Skip to main content
​
Dialer
Dialer authentication corrected

​
The Dialer partner API uses your standard API keys

The Dialer endpoints (https://api.cloudtalk.io/v1/dialer/*) authenticate with the same HTTP Basic credentials as the rest of the API — your API Access Key ID as the username and API Access Key Secret as the password.These pages previously documented a separate per-company x-api-key header, provisioned on request. That scheme was never deployed: requests carrying an x-api-key header are rejected with 401. If you could not authenticate against the Dialer endpoints before, use your standard key pair.Rate limiting on the Dialer surface is also per company, not per API key — a dedicated 60 requests-per-minute budget, separate from the core API’s quota.Note the Dialer is a newly released product surface: depending on your account’s rollout stage, campaigns managed through this API may not yet be visible in your CloudTalk Dashboard.
​
Documentation
New developer documentation

​
A new home for the CloudTalk API docs

These docs run on a new platform. The API reference is generated from our OpenAPI specification, so what you read here is what the API serves.What you can do now:
  • Send requests from the page. Every endpoint has a playground. Fill in your own API keys and see the real response.
  • Point your AI tools at the docs. There is an MCP server at https://developers.cloudtalk.io/mcp that lets an assistant search these pages directly. Every page also has a Copy page menu that hands the content to ChatGPT, Claude, Cursor, VS Code or Perplexity.
  • Search across every page, and a dark mode that respects your system setting.
This changelog starts here. From now on, changes to the API land as entries on this page, tagged by the part of the API they affect. Subscribe at /changelog/rss.xml.