Attach Numbers to Trunk
Trunks
Attach Numbers to Trunk
Map one or more numbers to a SIP trunk and get the origin endpoint
POST
Attach Numbers to Trunk
Map one or more numbers to this trunk - the Leg-A (BYO carrier) path. The bridge is
auto-resolved and hidden. The response returns the trunk-level origin endpoint: the
shared SBC ingress your carrier sends inbound calls to, the mapped DIDs, and the accepted
source IPs.
Prerequisites: API Token + Org-Handle. See Authentication.
Headers
| Name | Type | Required | Description |
|---|---|---|---|
| Authorization | string | Yes | Token <your-api-key> |
| Org-Handle | string | Yes | Organization domain handle |
| Product-Id | string | No | Product scope for the auto-resolved bridge (default unpod.dev) |
| Content-Type | string | Yes | application/json |
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
| id | integer | Yes | Trunk id |
Request body
| Field | Type | Required | Description |
|---|---|---|---|
| number_ids | integer[] | Yes | Numbers to map (deduped, order preserved) |
| bridge_slug | string | No | Explicit bridge; auto-resolved when omitted |
| region | string | No | Region hint (e.g. IN) |
Origin endpoint
| Field | Type | Description |
|---|---|---|
| ingress | string | SBC ingress URI your carrier dials in to |
| dids | string[] | The numbers successfully mapped |
| accepted_source_ips | string[] | The trunk’s source-IP allow-list |
| region | string | Resolved bridge region |
Partial success
201 if at least one number maps, else 400. Each data.numbers entry reports
ok/error independently.
cURL
Authorizations
Format: Token
Headers
Organization domain handle
Example:
"unpod.tv"
Product scope for the auto-resolved bridge (default unpod.dev)
Example:
"unpod.dev"
Path Parameters
Example:
21
Body
application/json
Response
Numbers mapped to trunk; origin endpoint returned