ModMed API integration guide: EMA, synapSYS and certified FHIR

The short answer

ModMed has two lanes. The certified FHIR API is self-service and read-only. The EMA Proprietary API reads and writes across EMA and ModMed Practice Management (patients, appointments, encounters, clinical data, charges, tasks) but you apply for it through ModMed's synapSYS partner program and pass a technical review.

The flavors to tell apart

How access works

Certified FHIR (self-service):

1. Find the practice's public FHIR endpoint (ModMed publishes them).
2. Register a client ID and request scopes.
3. The practice authorizes your app.

EMA Proprietary API (partners):

1. Apply through the synapSYS Marketplace.
2. Get a backend sandbox and agree resource access with synapSYS.
3. Pass a demo and technical review.
4. Receive production keys for each customer that connects.

What the APIs cover

Our take

ModMed is a good EMR to build serious products on, if you do the partner work. Certified FHIR gets you reading in days; anything that books, files or bills needs synapSYS, so start that application early and budget for the review cycle. Scope your build to the specialty line your customers run: EMA and gGastro aren't the same integration.

FAQ

Does ModMed have a public API?

Yes. A self-service certified FHIR API (read-only) and an EMA Proprietary API for approved synapSYS partners.

Can you write appointments into ModMed EMA?

Through the EMA Proprietary API, which supports creating and updating resources including appointments. You need synapSYS partner access.

What is synapSYS?

ModMed's partner and developer program for third-party apps that integrate with its proprietary API.

Sources

Public pages, accessed 11 Oct 2026: ModMed API portal · Getting started · EMA Proprietary API · ModMed synapSYS announcement