Agent inbound links

Link an agent to an inbound trunk

Links an agent to a SIP inbound trunk so the agent answers calls arriving on that trunk. Both the agent and the trunk must already exist in the workspace behind your API key — create them with POST /api/ext/agent and POST /api/ext/sip-inbound. Save the returned link_id to de-link later via DELETE /api/ext/agent-inbound-link/{link_id}.

POST

https://api.nabrah.ai/api/ext/agent-inbound-link

curl --request POST \
  --url 'https://api.nabrah.ai/api/ext/agent-inbound-link' \
  --header 'X-API-Key: <your-api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "agent_id": "018f3a2b-9c4d-7e1a-bf52-0a1b2c3d4e5f",
  "inbound_id": "018f3a2b-9c4d-7e1a-bf52-0a1b2c3d5a60"
}'

{
  "link_id": "00000000-0000-4000-8000-000000000000",
  "agent": {
    "agent_id": "00000000-0000-4000-8000-000000000000",
    "name": "string"
  },
  "sip_inbound": {
    "id": "00000000-0000-4000-8000-000000000000",
    "numbers": "string"
  },
  "project_id": "00000000-0000-4000-8000-000000000000",
  "created_at": "2026-01-15T12:00:00.000Z"
}

Where the IDs come from

agent_id and inbound_id

agent_id comes from GET /api/ext/agent or the create response of POST /api/ext/agent. inbound_id comes from GET /api/ext/sip-inbound or the create response of POST /api/ext/sip-inbound.

agent_idinbound_id

When this returns 400

All three of these produce the same 400 response, so check them in order.

Agent or trunk not in this workspace

Both IDs are validated against the workspace behind your API key. An ID belonging to another workspace is rejected exactly like a non-existent one.

The link already exists

The same agent cannot be linked to the same trunk twice. Call GET /api/ext/agent-inbound-link first if you need to know whether a pair is already linked.

Many-to-many

Several agents on one trunk

A trunk may carry several agents and an agent may serve several trunks — call this endpoint once per pair. Which agent answers a given call is decided at call time by the voice runtime, not by this API.

Authorization

X-API-Keystringheaderrequired

Your workspace API key. Create one in the dashboard under API keys.

Body

application/json

Attach one agent to one SIP inbound trunk.

Example

{
  "agent_id": "018f3a2b-9c4d-7e1a-bf52-0a1b2c3d4e5f",
  "inbound_id": "018f3a2b-9c4d-7e1a-bf52-0a1b2c3d5a60"
}

Response

200

Successful Response

application/json

422

Validation Error

application/json