Your own control layer
Manage calls, campaigns and agents programmatically from your own application.
Products
Voice API & Integrations for Connected Calling Systems
Connect calling operations to your applications and business data through the interfaces and integrations supported by Dialog.
- Unlimited users
- Open API & integrations
- Browser-based, nothing to install
Integration patterns
What you can build with voice APIs
These are patterns, not a promise of every function. Each one is checked against the API documentation and your requirements before work starts.
Event-driven workflows
Receive webhooks for call events and act on them.
Data pipelines
Send call data to your warehouse and BI tools.
CRM connections
Keep customer records in step with call outcomes.
Calling and call-control capabilities
The REST API is designed for developers who need control. Endpoints, authentication and limits are documented in the voice API documentation, which is the source of truth for what is supported.
| Capability | What it lets you do | Where to confirm |
|---|---|---|
| Calls | Manage calls programmatically. | API documentation. |
| Campaigns | Manage campaigns programmatically. | API documentation and demo. |
| Agents | Manage agents programmatically. | API documentation. |
| Authentication and limits | Understand access scopes and rate limits. | API documentation and your credentials. |
We describe only functions that are documented.
Events
Events, webhooks and call data
Webhooks fire for every call event, so a call that ends can update a CRM, alert a Slack channel or start a workflow. Delivery details, payloads and retries are in the documentation. Call detail records are available for your own systems, as described in reporting and analytics.
Event delivery
Receive call events as they happen.
Payloads
Understand the data sent with each event.
Signatures and retries
Confirm how events are verified and re-sent, where supported.
CDR access
Granular call detail records, including SIP codes and MOS scores.
CRM and business system integration
There are several ways to connect a system. We distinguish them plainly. Dialog connects through its API and webhooks and scopes each connection with you. Related automation is described in AI & Automation.
| Approach | What it is | Suited when |
|---|---|---|
| API-led connection | Your developers call the API. | You need full control over the integration. |
| Webhook-led automation | Call events trigger actions elsewhere. | You want updates the moment a call ends. |
| Native integration | A packaged connector. | Only where one is confirmed for your system. |
We do not assume native connectors that are not confirmed.
Developer checklist
Authentication, security and reliability
Request credentials for the environment and scopes your integration needs, then validate representative traffic before going live. Current detail is in the documentation, and our approach is described in the security overview.
Scopes and access
Give an integration only the access it needs.
Rate limits
Design for the limits in the documentation.
Testing
Test against representative traffic first.
Logs
Keep logs that help you investigate problems.
Security controls
Review how access is protected.
Five-stage guide
Typical implementation workflow
Integrations go better in stages. Campaign data and rules are set up in campaign management, and routing in call routing and management.
-
1
Scope requirements
List the events, data and systems involved.
-
2
Build in a test environment
Develop against test credentials first.
-
3
Validate data
Check records and field mapping with real examples.
-
4
Roll out
Move to production in steps.
-
5
Monitor
Watch events and errors after launch.
Resources
Developer resources and support
Use what is available to your account. Sandbox access and consultation are offered only where available, and we confirm them during scoping.
API documentation
Start with the developer documentation.
Integration consultation
Talk through your design with the team.
Sandbox access
Test safely, where available.
Support
Get help from the support team. Visit support.
Product demonstration
See the voice API in a product demonstration
A demonstration shows how the API, webhooks and data options work for your use case, and what is in scope. Consider the compliance controls that apply to your data, then review the wider flow in how it works.
- API and webhook walkthrough
- Data destinations and exports
- Authentication and testing
- Support and consultation options
Voice API & Integrations: frequently asked questions
What is a voice API?
A voice API is a programming interface that lets software place, control and monitor phone calls and receive information about them. Developers use it to connect calling to their own applications, instead of relying only on a dashboard. Dialog offers a REST API for managing calls, campaigns and agents programmatically, documented for developers.
What can a telephony API do?
A telephony API lets your systems start and manage calls, react to call events and read call data. Typical uses include syncing outcomes to a CRM, alerting a team when something happens and sending records to a warehouse. The exact functions available depend on the product, so check the documentation for what is supported.
Does Dialog support webhooks?
Yes. Webhooks fire for call events, so you can update a CRM, send a Slack notification or trigger a custom workflow when something happens. Event types, payloads and delivery behaviour are described in the API documentation, and we recommend testing with representative traffic and a failure case before relying on them in production.
Can we integrate Dialog with our CRM?
Yes, through the API and webhooks. Your developers, or ours during scoping, connect call events and outcomes to your CRM records. These integrations are built with the API rather than supplied as packaged connectors, so we agree the scope, field mapping and testing with you first. See AI & Automation for related options.
Is API documentation available?
Yes. The voice API documentation is the place to confirm endpoints, authentication and limits. It is the source of truth for what the interface supports, so use it alongside your demonstration. If something you need is not documented, ask during scoping rather than assuming it is available, and keep a note of the answer for your developers.
How is API access secured?
Access is controlled through credentials issued for the environment and scopes your integration needs, and we recommend requesting only what is required. Validate the integration with representative traffic before going live and keep logs for investigation. Current security detail is in the documentation and in the security overview, and your own security team should review it against their requirements.
See how Voice API & Integrations would fit your operation
Discuss your use case, existing systems, calling volumes and integration requirements with the Dialog team.
Tailored demo · Unlimited users