DEVELOPER DOCUMENTATION

Build with the
TAPI platform.

Reference material and integration concepts for applications using programmable telephony services.

API overview

The TAPI platform exposes versioned HTTP endpoints for telephony operations. Requests use JSON and responses include a request identifier for operational tracing.

GET /v1/health

Authentication

Production integrations use an application credential issued through the TAPI administration process. Credentials should be stored outside source control and rotated according to your organisation's security policy.

Authorization: Bearer <token>

Calls

Call operations return a request identifier and an initial lifecycle state. Long-running operations are reported through events.

POST /v1/calls

Events

Applications can consume event notifications to track changes in call state and operational status.

Errors

Errors are returned as structured JSON with a stable code and human-readable message. Request IDs can be supplied to support teams when troubleshooting.