API reference
A REST API over JSON: predictable resources, bearer keys, idempotent writes and signed webhooks.
Base URL
https://api.daybookhealthcare.com/v1OpenAPI spec
The whole API as an OpenAPI 3.1 document, for code generators, API clients and agents: /docs/openapi.json. Every docs page is also plain Markdown at its own URL with .md on the end, such as /docs/quickstart.md.
Conventions
Authorization: Bearer sk_live_... on every request. sk_test_ keys reach the sandbox.IdempotencySend Idempotency-Key on every POST. A retry never places a call or submits a form twice.Async by defaultCalls, portal tasks, enrollments and batches return right away; the result arrives as a webhook.Money and datesInteger cents. YYYY-MM-DD dates. RFC 3339 timestamps in UTC.Metadata
Most objects take metadata: up to 20 keys of your own, such as your account, ticket or claim id. Metadata is echoed on the object and on every event about it, so your webhook handler never needs a lookup table. Keep it to ids: a patient's name, date of birth or member id belongs in the request's own fields, never in metadata, which is echoed everywhere and will land in your logs.
Pagination
List endpoints return data and has_more. Pass the last id as starting_after for the next page.