Skip to main content
POST
cURL
Legacy SIP trunks (deprecated). These /sip-trunks endpoints manage legacy SIP trunks. Existing legacy trunks keep working, but use the SIP trunks API for every new setup, and see Migrate to SIP trunks to move an existing trunk.

Next steps

After adding a phone number, patch your agent’s telephony provider to sip-trunk.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

trunk_id
string
required

The unique trunk ID

Body

application/json

Phone number to add

phone_number
string
required

The DID phone number to register

Example:

"919876543210"

name
string

Optional human-readable label for the number

Example:

"Mumbai Support Line"

e164_check_enabled
boolean
default:false

Whether to enforce E.164 format validation

Response

Phone number added

Phone number (DID) registered on a SIP trunk.

id
string

Unique phone number identifier.

phone_number
string

The DID phone number stored on the trunk.

name
string

Optional label for the phone number.

byot_trunk_id
string

The SIP trunk ID that this phone number belongs to.

telephony_provider
string

Always sip-trunk on this legacy endpoint. Numbers on SIP trunks are managed with the SIP trunks API and call through provider trunk.

Example:

"sip-trunk"

deleted
boolean

Whether the phone number is deleted.

created_at
string<date-time>

ISO timestamp when the phone number was created.

updated_at
string<date-time>

ISO timestamp when the phone number was last updated.