For engineers
Drive the whole platform from code
Everything the dashboard does is available over HTTP. Drive the platform from your own code, or let a coding agent build the workflow for you.
What this is for
A dashboard is the right interface until the thing you want to do is repetitive, conditional, or supposed to happen at three in the morning. At that point you want the same capability behind an endpoint, and you want it to be the same capability rather than a reduced version of it.
What you can drive from code
- 01
Everything the dashboard does
The API is not a subset. Agents, flows, numbers, campaigns and call records are all reachable over HTTP.
- 02
Two SDKs
Client libraries so the common paths are a function call rather than a hand-rolled request.
- 03
An MCP server
Point a coding agent at it and let it build the workflow, which is a reasonable way to get a first version standing up.
- 04
The same records back
Calls made through the API keep the same recordings, transcripts and outcomes as calls made any other way.
Related
- Workflow BuilderDesign call flows on a drag-and-drop canvas
- IntegrationsRead and write your systems mid-call
- ReportsVolume, outcomes and minutes used
- AI voice agentLay the conversation out node by node, hear every branch in the browser, then point a phone number at it. The agent that answers is the one you tested.
Drive the whole platform from code: common questions
Is the API a subset of the dashboard?
No. Everything the dashboard does is available over HTTP, which is the design rather than a roadmap item.
Which SDKs are there?
Two client libraries, plus an MCP server for driving the platform from a coding agent.
Can I build an agent entirely from code?
Yes. You can also build it on the canvas and drive it from code afterwards. The two are the same objects.
Do API calls produce the same records?
The same recordings, transcripts and outcomes. How a call was initiated does not change what is kept.
Where are the API docs?
In the documentation alongside the rest of the platform, with the endpoints and the SDK usage together.
Still stuck? Talk to our team.