Developer overview

Integrate through the existing scoped REST API

This read-only overview links to the existing endpoint documentation and explicit request playground. Viewing it does not collect an API key, send a request or execute a business action.

Create a key in your own workspace

Manage API keys after signing in. Grant only the scopes required by your integration, keep the secret private and revoke it when access is no longer needed. REST API access also depends on the current plan.

Open API-key settings
Use the documented endpoints

The public v1 API exposes owned resources such as profile, contacts, agents, campaigns, calls and appointments. For example, GET /api/v1/profile requires profile:read. Authentication uses your API key through X-API-Key or the supported Bearer format.

Open endpoint documentation and playground
Check outcomes and operation receipts

Follow the endpoint schema and returned errors. Provider-facing operations can be pending or uncertain; a lost response is not permission to repeat a call, message or external write. Inspect the existing receipt and use the supported review path.

Keep execution deliberate

The linked playground runs only after you choose to send a request. A write can affect your account and may trigger funded or provider activity, so review the method, scope and destination first. This overview has no execution controls.

AUTONOMOUS VOICE AI

Ready to Never Miss a Customer Call Again?

Hear how an AiTeleMate AI voice agent platform handles calls like yours. Start your free trial. Our team is ready to walk you through the features, customized to your business.

No credit card required