SIP inbound
List SIP inbound trunks
Lists every inbound SIP trunk configured for the project that owns your API key. Inbound trunks let incoming SIP/phone calls reach a Nabrah agent: when a call arrives on one of the trunk's numbers, it is answered and routed to the bound agent. The response includes each trunk's id (use it as the path parameter for the GET/DELETE single-trunk endpoints), its display name, associated phone numbers, allowed source addresses, and the SIP digest credentials stored for the project. Authenticate with the X-API-Key header; the project is inferred from the key, so no project_id is required.
curl --request GET \
--url 'https://api.nabrah.ai/api/ext/sip-inbound' \
--header 'X-API-Key: <your-api-key>'{
"items": [
{
"name": "string",
"numbers": "string",
"id": "00000000-0000-4000-8000-000000000000",
"project_id": "00000000-0000-4000-8000-000000000000",
"created_by_email": "string",
"allowed_addresses": [
"string"
],
"auth_username": "string",
"auth_password": "string"
}
]
}What inbound trunks do
Inbound trunks terminate calls into your project.
DirectionInbound means Nabrah receives calls. A telephony/SIP provider delivers a call to a Nabrah number and the configured agent answers it. This is distinct from outbound trunks, which let an agent place calls out through your own provider.
The auth_username and auth_password returned here are the digest credentials your SIP provider uses to authenticate when delivering calls to Nabrah. They are stored and scoped to the project tied to your API key.
Listing returns full records
Each item in items is a complete SipInboundResponse.
To retrieve one trunk on its own, call GET /api/ext/sip-inbound/{sip_id} with an id value taken from this list.
Authorization
X-API-KeystringheaderrequiredYour workspace API key. Create one in the dashboard under API keys.
Response
Successful Response
application/json