Create a SIP trunk
Registers your own SIP provider for inbound and outbound calling. Supports DID or Extension (trunk_kind), calling-number format, transport, and advanced options (secure trunking, headers, codecs). Use this to bring your own numbers instead of buying from the marketplace. See BYO SIP trunk. Required scope: sip_trunks:write (keys without scope restrictions have full access).
Authorizations
API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access within the workspace's available capabilities.
Body
Provider termination host, e.g. sip.provider.com (no sip: prefix, no port).
Exactly one inbound match number is required. DID: E.164. Extension: E.164 or national digits without country code.
1 elementdid, extension twilio, custom Stored server-side; never returned by the API.
Stored server-side; never returned by the API.
shared, separate credentials, none auto, udp, tcp, tls e164_plus, e164_no_plus, national ISO-3166 alpha-2 for outbound region pinning, or empty for automatic.
TLS signaling + SRTP media.
allow, require, disable Custom outbound INVITE headers (max 10).
none, x, all PCMU, PCMA, G722, AMR-WB 1 <= x <= 36005 <= x <= 600May include inbound auth mode (inbound_auth, allowed_addresses) and region hints.
Response
The created SIP trunk (sanitized).
Customer-owned BYO/BYOC SIP trunk. Managed platform trunks, passwords, and internal trunk identifiers are never returned.