API reference
DialDozer’s public API is JSON over HTTPS. API v1 routes through https://app.dialdozer.com/hooks/api_v1.php using the r query parameter. Lead intake is a dedicated endpoint optimized for external lead sources.
Endpoints
Section titled “Endpoints”| Method | Route | Scope | Purpose |
|---|---|---|---|
GET | ?r=leads/{lead_id} | leads:read | Retrieve a lead |
GET | ?r=conversations/{lead_id} | conversations:read | Retrieve a merged thread |
POST | ?r=messages | messages:write | Send SMS, email, or note |
POST | ?r=cti/dial | cti | Queue an agent-bound dial |
GET | ?r=cti/lookup&phone=… | cti | Resolve a number to a lead |
POST | /hooks/lead_intake.php | leads:write | Validate and create a lead |
Request conventions
Section titled “Request conventions”- Send JSON with
Content-Type: application/jsonfor writes. - Send authentication through
X-Api-Key. - Use numeric lead IDs.
- Supply an
operation_idwhen sending messages so retries are idempotent. - Phone input is normalized to digits by intake and CTI endpoints.
Response envelope
Section titled “Response envelope”Successful responses include "ok": true. Failures include "ok": false and a stable machine-readable error or reason.
{ "ok": false, "error": "wrong_scope" }Download the maintained OpenAPI 3.1 specification for schema details and client generation.