VICIdial API vs DialerSeat for Developers
VICIdial's APIs are two HTTP scripts on your own VICIdial server: the Agent API acts on a logged-in agent's session (dial, hang up, set a disposition, pause), and the Non-Agent API manages leads, lists, users, campaigns, do-not-call and reports. Credentials go in the URL and answers are plain text. DialerSeat for Developers is a hosted JSON API with an embeddable dialer and signed webhooks, and POST /v1/seats/{id}/commands does what the Agent API does to a user's open dialer.
VICIdial's column is from its own pages, checked 2026-11-15. Sources are linked below.
| VICIdial | DialerSeat for Developers | |
|---|---|---|
| What it is | Open-source contact-center software, AGPLv2, that you run on Asterisk with MySQL or MariaDB, Apache and PHP, and your own SIP or telco lines. | An outbound dialer you embed in your own product: the dialing engine, with your campaigns, users and dispositions. |
| The APIs | The Agent API at /agc/api.php and the Non-Agent API at /vicidial/non_agent_api.php, called as URLs with user, pass and source in the query string. HTTPS if your web server is set up for it. | A REST API at api.dialerseat.com/v1 with JSON bodies, Bearer keys and an OpenAPI spec. |
| Responses | Plain text: SUCCESS or ERROR with an explanation, for example "SUCCESS: external_status function set". | JSON, with error codes and the field at fault, documented in Errors and limits. |
| The agent screen | VICIdial's own agent interface. The Agent API acts on a session an agent opened there (agent_user). | One script tag, an HTML tag, a React component, an iframe, a hosted link, or headless from your own buttons. |
| Acting on an agent's session | The Agent API: external_dial, external_hangup, external_status (the disposition), external_pause, external_add_lead and more, each for one agent_user. | POST /v1/seats/{id}/commands: dial, hangup, skip, disposition, pause, resume, start, stop, add_leads, update_lead, show_card, hide_card, set_campaign, set_mode. The open dialer does it as if the agent pressed the button, with campaign access, do-not-call and calling hours still checked on the server. 202 when sent, 409 seat_offline when no dialer is open. |
| Who is logged in, and call lookup | The Non-Agent API: logged_in_agents, phone_number_log and lead_search. | GET /v1/seats?online=true lists every open dialer, with paused for an agent who is not available. GET /v1/calls takes ?phone=, ?seat= and ?lead=. |
| Dial modes from the API | update_campaign sets dial_method (MANUAL, RATIO, INBOUND_MAN and the ADAPT_ methods) and auto_dial_level. | Preview, progressive, power and predictive, set for the platform, a campaign or a seat. |
| Results back to you | A Dispo Call URL per campaign, which VICIdial requests when a call is dispositioned. Signing is not described in its API documents. | Signed with HMAC-SHA256, managed by API, retried at 1m, 5m, 30m, 2h, 6h, 12h and 24h, then daily for 72 hours. |
| Running it | Yours: servers, Asterisk, carriers, upgrades and capacity. | DialerSeat runs the engine, carrier, numbers and capacity. |
When VICIdial is the better choice
- You want to own and modify the dialer's source code, and run it on your own servers.
- You need inbound ACD, closers, remote agents on plain phones and the other contact-center features VICIdial includes.
- You have a team that already runs Asterisk and wants to tune its pacing settings directly.
When DialerSeat for Developers fits
- You build a CRM or platform and want your users dialing from your own pages, with no second account.
- You want power or predictive dialing, answering-machine detection and calling hours handled, not built.
- Your campaigns, dispositions and user ids should stay yours, with every result back by signed webhook.
- You want to build and test the whole integration in a free sandbox before you pay for a call.
Related: answering machine detection for developers, the webhook signature checker, a call disposition codes list and the dialer API FAQ.
Sources
- VICIdial Agent API document (vicidial.org)
- VICIdial Non-Agent API document (vicidial.org)
- VICIdial Contact Center Suite (vicidial.org)
- DialerSeat: the docs and API reference
Other comparisons
CloudTalk API · Aircall Everywhere · JustCall Dialer SDK · Dialpad API · WAVV API · RingCentral Embeddable · Kixie API · Five9 API · Convoso API · Twilio power dialer · Zoom Phone Smart Embed · Twilio Flex dialer · Amazon Connect Streams · Genesys Cloud Embeddable Framework · HubSpot Calling Extensions SDK · Service Cloud Voice · PhoneBurner API · Aloware API · Plivo dialer · Vonage Voice API dialer · GOautodial