Whether this workspace may create SIP trunks
Ask BEFORE offering the create form. enabled is the staff-set entitlement; organizationVerified is the compliance prerequisite the customer can act on themselves. Both must be true for POST /v1/sip-trunks to succeed.
Requires the read scope. A key with less gets 403 insufficient_scope.
Authorization: Bearer tone_live_… or tone_test_…. The prefix IS the environment: a test key reaches only the sandbox, and no request field bridges the two.
In: header
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/sip-trunks/entitlement"{ "data": { "enabled": false, "organizationVerified": true, "request": { "id": "c0a8012e-1f2b-4c3d-9e4f-5a6b7c8d9e0f", "rejectionReason": "Carrier is outside India — see the cross-border note in the docs.", "requestedAt": "2026-09-15T09:30:00.000Z", "reviewedAt": null, "status": "pending" } }}Connect your own carrier over SIP — credentials are shown once
Creates a trunk in pending_verification: you can configure and test it, and our team approves it before it carries calls. Requires completed business verification AND SIP trunking enabled on your organization (403 sip_trunking_not_enabled otherwise — contact support). 🔴 The digest password in connection.password appears in this response only. Send an Idempotency-Key to make a retried create return the same trunk and the same password.
One SIP trunk
The trunk as it stands, including the last connectivity test.