Developers
The same API our dashboard runs on.
A versioned REST API and signed webhooks for appointments, interviews, summaries, calls and tasks. The API is in design and will open to partners with the first release.
Conventions.
Predictable by default, so an integration can be written once and trusted.
- Style
- REST over HTTPS, JSON, version in the path.
- Authentication
- OAuth 2.0 client credentials, short-lived tokens, scopes per resource.
- Idempotency
- An Idempotency-Key header on every POST. Keys are kept for 24 hours.
- Pagination
- Cursor-based, up to 100 items per page.
- Errors
- Problem-details JSON with a stable code and a request ID.
- Rate limits
- Per client and per clinic. 429 with Retry-After.
- Tenancy
- A token is bound to one clinic, or to a partner with explicit clinic grants.
- Time
- ISO 8601 in UTC, with the clinic timezone given separately.
Endpoints.
- GET
/v1/availabilitySearch bookable slots by provider, type and windowappointments:read - POST
/v1/appointmentsBook a slotappointments:write - PATCH
/v1/appointments/{id}Reschedule or cancelappointments:write - POST
/v1/intakesCreate an interview for an appointment; returns the patient linkintakes:write - GET
/v1/intakes/{id}Status and progress of an interviewintakes:read - GET
/v1/summaries/{id}Structured summary, with versionssummaries:read - GET
/v1/summaries/{id}/documentRendered PDF or plain textsummaries:read - GET
/v1/callsCall log, summary and transcriptcalls:read - PATCH
/v1/tasks/{id}Assign and resolve queue itemstasks:write - POST
/v1/webhooksRegister an endpoint and the events it wantswebhooks:write
Webhooks.
Payloads carry identifiers and status, never clinical content. Your service fetches detail with its own token.
Calls
call.startedcall.completedcall.transferredcall.abandoned
Scheduling
appointment.bookedappointment.rescheduledappointment.cancelledappointment.no_show
Intake and summary
intake.startedintake.completedsummary.createdsummary.signed
Safety
flag.raisedescalation.startedescalation.acknowledged
Integration
emr.write.succeededemr.write.failed
Tasks
task.createdtask.resolved
POST https://partner.example/hooks/dcoyo
Dcoyo-Signature: t=1794400000,v1=5f2c...
Dcoyo-Event-Id: evt_01JC...
{
"id": "evt_01JC...",
"type": "intake.completed",
"created_at": "2026-11-11T14:05:38Z",
"clinic_id": "cl_8f2...",
"data": {
"intake_id": "in_3aa...",
"appointment_id": "ap_91c...",
"summary_id": "sum_01J...",
"completeness": { "required_filled": 7, "required_total": 8 },
"flags": ["urgent_same_day"]
}
}- Signature is HMAC-SHA256 of the timestamp and body with your endpoint secret. Reject anything older than 5 minutes.
- Delivery is at least once. De-duplicate on the event ID.
- Failed deliveries retry with exponential backoff for 24 hours.
Every visit, better prepared.
Tell us how your clinic runs. We'll show you Dcoyo answering your phone, booking into your calendar and preparing your clinicians.