API Reference

Everything you can do with SIP trunking in the dashboard is backed by an API, and programmatic access is available for building your own automation and monitoring. This page is a short orientation; the full endpoint-by-endpoint reference is being prepared.

What you can do

Trunks & numbers: create and manage trunks and configure number routing.
Live statistics: pull per-trunk call/traffic stats and registration status, the same data shown in the dashboard (see CDRs & Call Troubleshooting).
Fax: submit outbound faxes and track their status (see Faxing over SIP).

For push-based integration instead of polling, see Webhooks & Events.

Authentication

API access is tied to your Cloud Voice account, the same account you use to sign in at voice.izt.cloud. Requests are authorized against that account, and you can only see and manage the trunks and numbers that belong to it.

Credential setup steps coming soon.

Good practices

A few things that hold regardless of the endpoint details:

Treat the dashboard as the reference behavior. The API enforces the same rules the dashboard does, for example, a trunk can’t be deleted while numbers still route to it, and caller ID overrides must be numbers your account owns.
Phone numbers are E.164. Send and expect numbers in +1XXXXXXXXXX form.
Prefer webhooks over tight polling loops for registration, call, and fax status, see Webhooks & Events.
Keep credentials out of client-side code. API access carries the same authority as your dashboard sign-in.

Full reference

The complete endpoint reference, request/response schemas, error codes, and examples, is coming soon.