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, move and reassign. Point a channel at a different agent by connecting the connection to that agent, not by patching this resource.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The owning Network id.
uuidThe Network entry-point id.
uuidThe tenant identifier
The partial routing-policy and/or emergency-status update.
Live emergency control. Only ACTIVE and DISABLED are accepted.
"UNSPECIFIED" | "ACTIVE" | "DISABLED"Doorway override of application unknown-sender admission. Null leaves the override unchanged. clearUnknownSenderAdmission restores inheritance. PROVISION requires the application's provisioning policy to be configured.
"UNSPECIFIED" | "REQUEST_ACCESS" | "REJECT" | "PROVISION"The same per-doorway override for known-but-unenrolled contacts.
"UNSPECIFIED" | "REQUEST_ACCESS" | "REJECT" | "PROVISION"The escalation desk this channel's conversations are handed to when its agent escalates. Null leaves it alone; use UpdateNetworkEntryPointRequest.ClearEscalationDesk for no handoff on this channel. The desk must belong to this Application, and a console desk only goes on a channel whose provider has a console.
uuidResponse Body
curl -X PATCH "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/entryPoints/497f6eca-6276-4993-bfeb-53cbbbba6f08" \ -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",
"escalationDeskId": "00000000-0000-0000-0000-000000000000",
"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
}Moves a messaging entry point to another Application.
The explicit re-home of a claimed channel address: NEW inbound routes to the target Application, while existing conversations stay with this Application (their conversation bindings pin them here). The doorway's agent must already be a member of the target Application (400 otherwise), where the route's membership is re-resolved. Provider/address identity is preserved — a move re-points the claim, it never forks a second one.
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.