Get the workspace's SIP trunk
A workspace has at most one SIP trunk. Returns sip_trunk.not_found if none has been connected.
Authorization
bearerAuth Long-lived ES256 JWT minted from the dashboard (https://app.sautikit.com/developers/api-keys). Signed by the
platform keyring. Carries workspace_id and scopes claims;
revoked via the platform deny-list.
In: header
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/sip-trunk"{ "auth_mode": "registration", "label": "string", "realm": "string", "proxy": "string", "transport": "udp", "username": "string", "auth_username": "string", "has_password": true, "signaling_ips": [ "string" ], "media_ips": [ "string" ], "country_code": "string", "outbound_number_format": "string", "outbound_codec_prefs": "string", "outbound_media_security": "string", "status": "pending", "last_error": "string"}{ "error": { "code": "validation.bad_request", "message": "string", "request_id": "string", "details": [ "string" ] }}{ "error": { "code": "validation.bad_request", "message": "string", "request_id": "string", "details": [ "string" ] }}Revoke a SIP credential DELETE
Deletes the credential row. The associated SIP user-agent can no longer register with this username. Caller must have writer access to the workspace.
Connect or update the workspace's SIP trunk PUT
Upserts the workspace's single trunk — there is no trunk ID in the path because a workspace has only ever had, at most, one. Refused with `workspace.locked_to_platform_numbers` on a workspace that already buys numbers from Sautikit. For a `registration` trunk, the password is pushed to Sautikit's box and a REGISTER is attempted synchronously, inside this same request (up to ~20s). The response's `status` reflects the outcome immediately: `active` on success, `failed` (with `last_error`) if the provider rejected the credentials or was unreachable — the workspace stays unlocked either way until it actually succeeds. Omit `password` on a later `PUT` to keep the password already on file (e.g. when only changing a label); a password rotation re-signals every active BYO number on the trunk automatically. For an `ip_allowlist` (signaling) trunk, this only submits the trunk for review — it lands at `pending_approval` and does not go live, or lock the workspace, until a person on Sautikit's operations team approves it and installs both the signalling and media IPs on the box.