athenahealth API integration guide: athenaOne, Marketplace and FHIR
- Access model
- Marketplace partner + practice authorization
- Developer program
- athenahealth Developer Portal + Marketplace
- Certified FHIR access
- FHIR R4 (certified, US Core)
- Scheduling write
- Via the athenaOne proprietary API
The short answer
athenahealth runs two API layers on athenaOne: a certified FHIR R4 API and a large proprietary REST API where most operational work happens, including scheduling and documents. Serious products go through the athenahealth Marketplace partner program, and each practice authorizes your app.
The flavors to tell apart
| Flavor | What it means for an integration |
|---|---|
| athenaOne | Cloud, single-instance platform (clinicals, collector, communicator). One global API surface: proprietary REST plus FHIR R4. This is what most practices mean by "athena". |
| athenaOne for Hospitals & Health Systems | The hospital variant of the same network platform. |
| athenaPractice / athenaFlow | Centricity lineage, deployed on customer servers. Separate FHIR server and developer portal (mydata.athenahealth.com); each practice registers your app in its own install, on its own domain. |
If a prospect says "athena", ask whether it's athenaOne. The Centricity-lineage products are a different integration.
How access works
- Sign up on the developer portal for preview (sandbox) access.
- Choose your auth. OAuth 2.0 client credentials for backend apps; authorization code with PKCE for SMART apps.
- Production and the proprietary API route through the Marketplace partner program. athenahealth describes partners as vetted for security, HIPAA compliance and integration quality.
- Each practice authorizes your app for its practice ID.
What the APIs cover
| Job | Path on athenaOne |
|---|---|
| Certified clinical read | FHIR R4, US Core / USCDI, SMART on FHIR, at api.platform.athenahealth.com/fhir/r4 |
| Scheduling, documents, most write workflows | athenaOne proprietary REST API (athenahealth cites 800+ endpoints) |
| Event notifications | FHIR Subscriptions, in limited alpha per athenahealth's public GitHub |
Our take
athenaOne is one of the better EMRs to build on: a single cloud platform, a real write API, and a marketplace practices actually shop. Budget for the partner process, not just the code: security review, commercial terms and a practice-by-practice rollout. Design for the proprietary API from the start if you need to book or file anything; FHIR alone won't get you there.
FAQ
Does athenahealth have an open API?
It has a certified FHIR R4 API and a proprietary athenaOne API. Production access to the proprietary API goes through the athenahealth Marketplace partner program.
Can you schedule appointments in athenahealth by API?
Scheduling runs through the athenaOne proprietary API, not the certified FHIR API.
Is athenaPractice the same as athenaOne?
No. athenaPractice and athenaFlow come from the Centricity line, run on customer servers, and have their own FHIR server and developer portal.
Sources
Public pages, accessed 11 Oct 2026: athenahealth developer portal · athenaOne FHIR base URLs · athenaPractice / athenaFlow APIs · athenaOne FHIR Subscriptions (GitHub) · athenahealth Marketplace partners
Other EMR integration guides
eClinicalWorks
Self-registration + per-customer approvalEpic
Self-service FHIR + partner-gated proprietary APIModMed
Registration + per-customer tenant provisioningOracle Health (Cerner)
Tiered programs; distributor terms for vendorsNextGen Healthcare
Free open tier + paid integrator tiersVeradigm (Allscripts)
The audit is free. Another quarter of guessing is not.
Book the Free 48-Hour Audit