SIP credentials: connect your own desk phone, and see the password again
SIP credentials are ready to register the moment the API responds. Passwords can be shown again, and there are five new MCP tools.
SIP credentials are ready to register the moment the API responds. Passwords can be shown again, and there are five new MCP tools.
You can point your own SIP equipment (a desk phone, an office PBX, Odoo, a softphone) at a Sautikit number. Four things changed in how credentials work.
Creating a SIP credential now finishes setting it up before the API responds, so a 201 means the device can register straight away. Before, there was a short delay during which a new password might not work yet.
If the credential cannot be set up, the request fails with numbers.sip_provisioning_failed and nothing is created.
{
"username": "…",
"password": "…",
"host": "sip.sautikit.com",
"port": 5080,
"transport": "udp",
"realm": "sip.sautikit.com"
}transport and realm are new. Read all the settings from the response.
const res = await fetch(
`https://api.sautikit.com/v1/numbers/${numberId}/sip-credentials/${credentialId}/reveal`,
{
method: "POST",
headers: { Authorization: `Bearer ${process.env.SAUTIKIT_API_KEY}` },
}
);
const { password } = await res.json();A mislaid password no longer means rotating a working credential. Revealing changes nothing, and a registered device keeps working.
Rotation is still there for when you want a new password. It disconnects the device using the old one.
A number can hold several credentials, one per device, each with its own password. The list response now reports active_count and limit, and creating past the limit returns numbers.credential_limit_reached. Revoking a credential frees a slot.
list_sip_credentials, create_sip_credential, reveal_sip_credential, rotate_sip_credential and revoke_sip_credential are available on the hosted MCP server, so an AI client can set up a desk phone for you. reveal_sip_credential needs a key with write access, because it returns a live password.