Dolores Developer Docs
Build voice-AI integrations on top of the Dolores REST API and webhooks.
The Dolores API is a Twilio-style HTTPS interface for managing customers, scheduling appointments, and receiving signed webhook events on appointment changes — everything you need to wire Dolores's voice agent into your stack.
Get started
Quickstart
Make your first API call in five minutes. Auth, customer, webhook.
Authentication
API keys, livemode vs testmode, rotation, best practices.
Your first webhook
Register an endpoint, verify the HMAC signature, handle delivery.
SDKs
Languages we ship code samples for, and how to build your own client.
API reference
Customers
Full CRUD on customer records. Phone numbers canonicalized to E.164 at ingest.
Appointments
Book, reschedule, cancel. Every status transition fires a webhook.
Sessions
Read-only access to call metadata, transcripts, and recordings.
Events & webhooks
Audit log of delivered events; replay individual deliveries.
Conventions
Once you've made your first call, these short pages cover the conventions every endpoint follows:
- Errors — uniform envelope, type/code taxonomy, request-id correlation.
- Pagination — cursor-based traversal with
has_more/next_cursor. - Idempotency — safely retry POST/PATCH with
Idempotency-Key. - Rate limits — 100 req/sec + 5000 req/min per key, with backoff strategy.
- Versioning — how breaking changes ship.
Webhooks
Dolores delivers appointment-status events to URLs you register. Read Overview for the mental model, then Verifying signatures for the HMAC-SHA256 recipe in six languages.
Need help?
- Email support@meetdolores.ai — include the
Dolores-Request-Idheader from your failing call. - See Support for what to include in a bug report.
- See the Changelog for what shipped recently.