CureMD API integration guide: FHIR registration and what's read-only

The short answer

CureMD has no self-serve developer portal. You register a FHIR app by sending CureMD a registration packet, and CureMD issues credentials. The published FHIR R4 API is largely read-only, including Appointment. Clinician-facing and backend apps need a business agreement with the practice first.

How access works

1. Email the registration packet described in CureMD's FHIR documentation: app name, URLs, redirect and launch URLs, patient or provider type, SMART scopes, platforms and attestation.
2. CureMD support issues credentials.
3. Patient-facing apps reading USCDI v1 are free, per CureMD's disclosures. Clinician and backend apps need an agreement with the practice and may carry one-time and recurring costs (amounts not published).
4. Commercial partnerships go through CureMD's partner contact.

What the APIs cover

Our take

Treat CureMD as a read integration unless the vendor confirms more in writing. For scheduling or write-back, plan a partner conversation with CureMD or a practice-authorized alternative, and price the data refresh cadence into your product.

FAQ

Does CureMD have a public API?

It publishes a FHIR R4 API with registration by email. There's no public self-serve developer portal or sandbox described in its documentation.

Can you book appointments in CureMD through the API?

Not through the published FHIR API, where Appointment is search and read only.

What are CureMD's API rate limits?

CureMD's FHIR documentation states 20 requests per minute per client.

Sources

Public pages, accessed 11 Oct 2026: CureMD FHIR API documentation (PDF) · CureMD mandatory disclosures (PDF) · CureMD partners