Changelog

The Dolores API uses URL major versions (/v1/) plus dated minor revisions for non-breaking enhancements. Breaking changes always ship under a new major version (see Versioning).

2026-08-22 — plain-text replies for chat integrations

• POST /v1/conversations/{id}/messages and POST /v1/messages accept an optional markdown boolean (default true). Pass false to receive the agent's reply as plain text — markdown emphasis and HTML are stripped, links flatten to label: url. Use it when relaying replies to surfaces that render text literally, such as SMS or WhatsApp. The stored transcript keeps the original reply.

2026-08-03 — call a customer on demand

• New action endpoint: POST /v1/customers/{id}/call places a one-shot outbound call to the customer immediately. Unlike workflow-driven outbound dialing, a no-answer is not retried — the attempt simply ends.
• Session objects now carry a call_status field with the dial outcome of an outbound call: queued, dialing, completed, no_answer, failed, invalid_number, or call_later. Track a triggered call via GET /v1/sessions/{session_id} using the session_id returned by the call action.
• WhatsApp business numbers: when Meta call consent isn't on file yet, the call action returns 202 with status: consent_pending and the call dials automatically once the customer accepts.

2026-06-01 — v1 initial release

• Customers resource with full CRUD (/v1/customers).
• Appointments resource with full CRUD (/v1/appointments).
• Sessions read-only API including transcript and recording endpoints.
• Events audit log and manual replay.
• Webhook endpoints management with HMAC-SHA256 signing and rotatable secrets.
• Appointment-status webhook events: appointment.created, appointment.confirmed, appointment.rescheduled, appointment.cancelled, appointment.failed.
• API key auth, per-key livemode flag, cursor pagination, idempotency, rate limits (100/s + 5000/m per key).