SBC
SBC Manager — REST and SOAP API Integration
SBC Manager exposes a full REST API and a SOAP API for integration with external provisioning systems, carrier portals, and automation tools. Tokens are managed under Security → API Tokens.
REST API
All REST endpoints are under /api/v1/ and authenticate with a Bearer token:
Authorization: Bearer <token>
Key Resource Areas
| Area | Base Path | Description |
|---|---|---|
| Trunks | /api/v1/trunks |
Create, read, update SIP trunks |
| DIDs | /api/v1/dids |
Manage DID inventory and routing |
| Routes | /api/v1/routes |
Manage routing policies |
| HMR | /api/v1/hmr |
Manage header manipulation rule sets |
| Fraud | /api/v1/fraud-rules |
Manage destination fraud rules |
| Operations | /api/v1/ops/ |
Stage versions, queue apply/rollback, view history |
| Backups | /api/v1/backups |
Trigger and download backups |
| Endpoints | /api/v1/endpoints/provision |
Full NAP provisioning in one call |
| Route Simulation | /api/v1/route-simulate/batch |
Batch routing decision test (up to 200 calls) |
Full endpoint documentation is available in the SipLive SBC API Reference guide.
SOAP API
A SOAP interface is available at /soap/v1 for legacy provisioning systems, with equivalent coverage to the REST API. The WSDL is published at /soap/v1?wsdl.
Notes
- API changes follow the same staged model as the GUI: provisioning calls stage changes, and an apply (via
/api/v1/ops/) makes them live. - Scope tokens narrowly — a DID-management integration needs only the DIDs area.