BE VOICE
For developers
Connect your software to BE Voice
These guides are for developers at your business, or your IT provider. There are two ways to connect: your app starts calls through BE Voice, or BE Voice's AI agent uses your system during a call. Many businesses use both.
1. Make calls from your app: the API and MCP
Your app (a CRM, a booking system, a script) tells BE Voice who to call and what the call is for. BE Voice rings the number and its AI holds the conversation until the goal is met. Your app can give it new instructions while the call is on, and gets the outcome, the answers, a summary and the transcript when it ends.
The same thing is available to AI assistants through MCP: add BE Voice as a remote MCP server and the assistant can place calls, follow them and read the results itself.
curl https://voice.binaryelements.com/v1/calls \
-H "Authorization: Bearer $BE_VOICE_KEY" \
-d '{"to": "+61400000000",
"task": {"goal": "Confirm Sam can take delivery of order A1002 on Friday morning"}}'- API keys and basics: your key, the base address, errors, IDs and limits.
- Place an AI call: every field of the call's brief, with a full example.
- Follow, steer and get results: status, live instructions, hanging up and the final result.
- Webhooks: results and events pushed to your system, and checking their signature.
- MCP: calls from an AI assistant: the MCP server, its tools and how to connect.
2. Integrations for agents: your AI agent calls your API
Here BE Voice calls you. While your AI agent is on a call (answering your phones, or working through a campaign), it can look things up in your system and record things there: an order's status, an invoice balance, a booking, a promise to pay. A campaign can also take its list of people to call from your system and send each result back.
- Integrations for agents: agent-ready APIs: what your API should look like so the agent uses it well.
- Integrations for agents: connect your API: adding the connection and its tools in the console, and testing them.
- Integrations for agents: campaigns from your system: your system supplies the call list and receives the results.
Which do I need?
| You want to… | Use |
|---|---|
| Have the AI ring one person from your app, with a goal you set for that call | Place an AI call |
| Ask an AI assistant to make a call for you ("call Sam and confirm Friday") | MCP |
| Change course while a call is on, or wait for its answers | Follow, steer and get results |
| Get results, messages and call events into your system as they happen | Webhooks |
| Let your receptionist agent check an order or a booking while a customer is on the line | Integrations for agents |
| Call a list of people every week (reminders, overdue accounts) with the list kept in your system | Integrations for agents: campaigns from your system |
| Call a list of people from a spreadsheet, with no code at all | Campaigns in the console |
Before you start
- An API key. Anyone who can sign in to your console can make one under Settings → Integrations → API keys. See API keys and basics.
- Calls through the API and MCP must be part of your account to place calls from your app or an AI assistant. If it isn't, the API answers
403 module_off: contact us to add it. - A number calls can come from. Calls show one of your business's numbers, such as 03 7000 0000. See Your numbers.