Developers
Everything the app can do, the API can do.
Records, scheduling, prescriptions, billing and consultations over a documented REST API with signed webhooks, typed SDKs and a FHIR R4 view of the same data.
Status
All systems operational
Partner access is open now. Public self-serve keys are rolling out through 2026.
01Reference
A sample of the surface.
Predictable pagination, cursor-based, with consistent error shapes. Full OpenAPI schema available to partners today.
- GET
/v1/patients/{id}Full patient record with consented history - POST
/v1/appointmentsBook against a clinic’s live chair schedule - GET
/v1/practitionersVerified clinicians with registration status - POST
/v1/prescriptionsIssue a signed digital prescription - GET
/v1/invoicesBilling, payments and outstanding dues - POST
/v1/consultationsCreate a video consultation room and tokens - GET
/v1/fhir/Patient/{id}FHIR R4 representation of the same record - POST
/v1/webhooksRegister a signed webhook endpoint
02Webhooks
Signed, retried, replayable.
Every event carries an HMAC signature and a delivery id. Failures back off for twenty-four hours and stay replayable for seven days.
Versioned, with notice
Breaking changes ship behind a new version. We give twelve months of deprecation notice, and we email every integrator on the old one.
Everything the app can do
There is no private API. Osdent and 1Dentist call the same endpoints you do, which means the surface is complete by construction.
Idempotent and replayable
Writes accept an idempotency key. Webhooks are signed, retried with backoff, and replayable from the dashboard for seven days.
Scoped by consent
Access tokens carry the clinic and patient scope they were granted. A revoked consent invalidates the read on the next request, not the next sync.
03Open source
The parts that should belong to everybody.
Standards work, messaging compliance and offline sync are not competitive advantages. They are tax on every Indian health developer, so we publish ours.
svamai/fhir-dental
Mapping between odontogram findings and FHIR R4 resources, with a validation suite.
svamai/dlt-templates
DLT-compliant SMS and WhatsApp template definitions for Indian clinical messaging.
svamai/offline-sync
Conflict-safe offline sync primitives for Flutter clients on unreliable networks.
04Reliability
What we commit to, and where you can check it.
Status, changelog and deprecation notices are published rather than emailed on request.
Uptime target
99.9%
Rolling 90-day availability
Deprecation notice
12 months
Before any breaking change
Webhook replay window
7 days
Self-serve from the dashboard
Get a key and start building.
Partner API access includes a sandbox with synthetic patient data, the full OpenAPI schema, typed SDKs and a direct channel to the engineers who maintain it.