Hands a messaging entry point to a different member agent of this Application.
The answering agent IS the doorway's owner, so this re-owns the doorway row in place: the entry point, the provider/address identity and — for binding-shaped providers — the already-registered inbound webhook URL all survive, and only NEW inbound follows the new agent (conversations already bound stay with the old one). The target agent must already hold a live membership here (400 otherwise). For endpoint-owned providers a target that already fronts another bot for the provider is 409 unless `replaceExistingEndpoint` asks to deactivate it.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The Network that owns the entry point.
uuidThe Network entry-point id to re-own.
uuidThe tenant identifier
The member agent that should answer this channel.
The member agent that should answer this channel. It must have a live membership in the Application that owns the entry point.
Endpoint-owned providers only (Telegram): when the target agent already fronts a different config's bot for this provider (one active bot per agent per provider), deactivate that bot and hand this one over in its place. Without it such a reassign is rejected 409, so a bot swap is always an explicit choice. The displaced bot keeps its endpoint record (reactivatable later); its doorway rows are removed.
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/entryPoints/497f6eca-6276-4993-bfeb-53cbbbba6f08:reassign" \ -H "Content-Type: application/json" \ -d '{}'{
"id": "00000000-0000-0000-0000-000000000000",
"networkId": "00000000-0000-0000-0000-000000000000",
"networkIntegrationBindingId": "00000000-0000-0000-0000-000000000000",
"kind": "MESSAGING",
"provider": "string",
"externalAddress": "string",
"displayName": "string",
"integrationConfigId": "00000000-0000-0000-0000-000000000000",
"integrationConfigName": "string",
"agentId": "string",
"agentMembershipId": "00000000-0000-0000-0000-000000000000",
"unknownSenderAdmission": "REQUEST_ACCESS",
"knownUnenrolledAdmission": "REQUEST_ACCESS",
"routingPolicyKey": "string",
"sourceKind": "CHANNEL_BINDING",
"sourceId": "00000000-0000-0000-0000-000000000000",
"operationalStatus": "ACTIVE",
"createdAt": 0,
"modifiedAt": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Updates the routing policy key and/or live emergency status of an entry point.
Provider, external address, backing binding, provenance, and owning Network cannot be changed. Neither can the route's agent: the answering agent is the backing doorway's owner, and the entry point's `agentMembershipId` is a projection of it maintained by attach/detach. Point a channel at a different agent by connecting the connection to that agent, not by patching this resource.
Returns the Network's escalation pool (an empty pool when none is set).
Returns the live operator ladder the escalation tool uses for members of this Network. The pool and per-customer overrides are the only resolution source. No pool yet returns an empty ladder so clients can render the editor. Changes take effect without publishing a new Network revision.