Router
The Inkbox iMessage router is the shared number humans text to connect with an agent. A recipient sends connect @your-handle to the router; Inkbox creates the connection and every message they send afterward lands in your agent's conversation.
Resolve the router number at runtime — it can change, so never hardcode it.
Get router number GET
GET /triage-numberReturns the active router number and the connect command for the caller. For identity-scoped API keys, connect_command is pre-filled with that agent's handle; for admin API keys it carries a placeholder to fill in.
Response (200)
JSON| Field | Type | Description |
|---|---|---|
number | string | The router's phone number in E.164 format |
connect_command | string | The exact message a human texts to the router to connect to the agent |
Error responses
| Status | Description |
|---|---|
| 404 | No router number is currently active |
Code examples
cURLThe connect flow
- Your human texts the
connect_command(for exampleconnect @my-agent) to the router number. - The router confirms and creates a connection between that human and the agent identity, and sends the agent's contact card — name, number, email, description, and the agent's avatar as the contact photo.
- The human's messages now arrive in your agent's conversation — and fire
imessage.receivedwebhooks if subscribed. - Your agent replies with
POST /messages.
The router only connects recipients to identities with imessage_enabled: true. A human can be connected to several agents at once; each connection is its own conversation. Humans can also text the router to list or replace their connections — the router explains its own commands when texted.
