Feature · developer API
Outbound dialer API: safe retries and checks before the ring.
PyAI places outbound calls through one REST request, with compliance checks and an AI voice agent on every call.
What PyAI gives you for outbound dialing
- An outbound dialer API on PyAI runs its checks before the ring: it confirms the from number is active and voice-capable and that the agent sits in the same project.
- A failed consent, suppression, quiet hours or velocity check returns a compliance block (403), and nothing is dialed.
- A 3-minute delivery call on Omni costs $0.18 at $0.05/min plus $0.01 telephony, with no seat license or platform fee added.
- Call status can be read back from the API or arrives on signed webhooks, which retry 429 and 5xx answers with backoff.
What does the API return in common outbound cases?
Step through three request outcomes. The lines are an example script, not a recording, built from the documented outbound call flow.
Pick a moment, then press play
What happens between the API request and the first ring?
Most of the work happens before the phone rings, and any stage can stop the call. The replay check runs first, so a resent request returns the original result.
Authenticate and scope
The edge accepts only Live keys with calling permission. Test keys cannot originate real calls.
Replay check
The duplicate-safe key is looked up. A match with the same body replays the first result. A match with a new body returns 409.
Resource check
The from number must be active and voice-capable, and the agent must sit in the same project.
Compliance and route
Policy, consent, suppression, quiet hours and velocity pass, then routes are ranked by quality and health before origination.
Rules pass
The response carries a call id with status requested. The statuses ringing, answered, and completed or failed follow.
Rules block
A compliance block (403) comes back and nothing is dialed, so your code can log the reason and move on.
What do developers build on an outbound calling API?
Event-driven calls fit an API better than a campaign screen, because the trigger lives in your own system. Each example below starts from an event in someone's own database, not from a campaign list.
Delivery exceptions
A failed delivery scan triggers one call to the customer, who picks a new window with the agent. The order id doubles as the duplicate-safe key, so a replayed job never calls twice.
Pre-visit checks
A scheduling system calls patients who consented at booking, two days ahead, and the agent confirms or reschedules through a server tool.
Verification callbacks
A flagged transaction queues a call for the allowed calling hours. A dispute goes straight to a human analyst by live transfer.
Form to call
A CRM workflow fires the request when a high-intent form lands, and the call record links back to the lead.
Activation calls
A product analytics event, such as a trial account that never connected its data, triggers one call from an outbound dialer job. The agent offers a setup session and logs the answer to the account.
Technician running late
A dispatch system calls the next customer when the technician's ETA slips past the window, so nobody waits at home without news.
Promise to pay
A billing system calls customers who opted into balance reminders. The agent records a promised date, and Recap at $0.02 a minute writes it back to the account.
Outbound dialer API questions
Is an autodialer illegal?
Autodialers are legal in the US when used within the rules. Under 47 U.S.C. 227(b), an artificial or prerecorded voice call to a mobile needs the callee's prior express consent, and 47 CFR 64.1200 requires that consent in writing for telemarketing. PyAI checks stored consent before dialing. This is not legal advice.
How do you choose a dialer system for an outbound call center?
For a floor of human reps, the right system matches its dialing mode, CRM and reporting needs. For developers adding calls to their own product, an API such as PyAI fits better, because each call is one request with compliance checks and an Omni agent included. Check how each option handles retries.
Does an outbound dialer API need a campaign tool or seat license?
An outbound dialer API built on PyAI needs neither. Teams that already own the contact list, the trigger and the CRM send one request per call, and the rules run on the PyAI server whatever client sends it. Calls bill at $0.05/min plus $0.01 telephony, with no platform fee.
How do I build an outbound dialer with an API?
Store the contact list and trigger logic in your own system, then call PyAI once per contact with one API request, a Live key with calling permission, and a duplicate-safe key derived from your event. Read status from GET, or receive it through signed webhooks, before the next attempt.
Related features
PyAI is voice infrastructure. It hands you the audio and transcript, and does not replace your own models or review tools.