Attaches an inbound doorway to this Network so its real inbound routes here.
Materializes (or adopts off another Network) the doorway's messaging entry point on this Application, so a live inbound resolves this Application's deployment instead of the Default Network. Provide exactly one of `channelBindingId` (a per-participant channel binding) or `messagingEndpointId` (a per-agent provider endpoint — its Telegram bot, WhatsApp number, …). The doorway's agent must already be a member of this Network. Rejects (409) if the endpoint is already routed by a different source.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The target Network id.
uuidThe tenant identifier
The inbound doorway to attach (a channel binding or a messaging endpoint).
The inbound AgentChannelBinding to route into this Network. Mutually exclusive with AttachChannelToNetworkRequest.MessagingEndpointId.
uuidThe AgentMessagingEndpoint (per-agent provider doorway) to route into this Network. Mutually exclusive with AttachChannelToNetworkRequest.ChannelBindingId.
uuidResponse Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/entryPoints/attach" \ -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
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Lists the stable external doorways materialized for a Network.
Returns messaging, trigger, and schedule entry points owned by this Network. Provider/address identity is stable and never inferred or transferred through this surface.
Connects a NEW channel to this Application in one step — mints the doorway and claims its address.
Creates a channel inside this Application; a channel is never created unbound. Mints the inbound doorway (a MANUAL inbound channel binding, or the agent's messaging endpoint for endpoint-owned providers such as Telegram, whose config is both credential and address) and creates its messaging entry point here. The agent must already be a member of this Application. Returns 409 when the address is already used by another Application; move a claimed address with `:move` instead. Returns the one-time webhook URL when a new channel binding was created. An Email (Gmail) channel is checked and set up further: a connection without the `gmail.modify` scope is refused before anything is created (400, code `EMAIL_CHANNEL_SCOPES_MISSING`). Its admission follows the Application's policy for new senders, which connect does not change; the response's `email.unknownSenders` says what that policy does to someone who writes in, and `warnings` lists what did not stop the connect, such as `AGENT_SENDS_GMAIL`.