Overview
DialDozer exposes a small, composable developer surface for moving leads into the platform, reading lead and conversation state, sending messages, and requesting agent-bound CTI dials.
Pick an interface
Section titled “Pick an interface”| Interface | Best for | Authentication |
|---|---|---|
| HTTP API | Product integrations, webhooks, automation | X-Api-Key |
| MCP server | AI agents and coding assistants | API key passed to the local server |
| CLI | Operators, scripts, CI jobs | Environment variable or local profile |
Core resources
Section titled “Core resources”- Leads are contacts assigned to a list and campaign.
- Conversations merge a lead header with chronological communication entries.
- Messages create SMS, email, or internal-note entries using idempotent operation IDs.
- CTI lets an API key bound to an agent request a dial or resolve a phone number.
- Lead intake validates, deduplicates, creates, and optionally enqueues a lead.
All endpoints return JSON. Tenant-scoped keys only address leads belonging to campaigns in their organization. Platform-global keys are reserved for trusted administration.
Base URLs
Section titled “Base URLs”API v1: https://app.dialdozer.com/hooks/api_v1.phpLead intake: https://app.dialdozer.com/hooks/lead_intake.phpUse HTTPS only. The API route is selected with the r query parameter, for example ?r=leads/42.
Next step
Section titled “Next step”Follow the quickstart to make a real authenticated request, then use the OpenAPI document to generate clients or tools.