Tebra API integration guide: SOAP, FHIR and the partner program

The short answer

Tebra has two APIs that do opposite jobs. The SOAP Web Services API (inherited from Kareo) is where you create, update and cancel appointments and work with practice-management data. The FHIR API is read-only clinical data. Most real integrations need the SOAP API, a practice-issued customer key, and Tebra's API partner terms.

The flavors to tell apart

• Tebra EHR (the clinical side) and Tebra Practice Management (the former Kareo PM and billing). The SOAP API and much of its documentation still live on Kareo-era hosts.
• Patient engagement and marketing, the former PatientPop.
• Billing-company accounts, which have their own partner path.

Confirm which modules a practice actually runs before you scope. A practice on Tebra PM only has nothing for a clinical read to find.

How access works

1. SOAP API. Each practice's system administrator generates a customer key and grants your API user the permissions you need. Commercial use as an integrator runs under Tebra's API Partner terms.
2. FHIR API. Self-service developer account and sandbox on Tebra's FHIR portal, app review by Tebra's FHIR team, then the practice asks Tebra Customer Care to activate FHIR for production.
3. Partner program. You apply, get approved, and get a partner portal login. Tebra's published API terms grant a revocable, non-transferable licence and don't allow reselling API access.

What the APIs cover

The SOAP guide publishes rate limits per call (appointment create, update and delete at roughly one call every half second), so build queues, not bursts.

What it costs

Tebra publishes API partner fees: a $3,000 per year developer platform fee, then per-call usage tiers (free under 10,000 calls a month, rising to $0.01 per call above a million), with a 10 GB data-usage limit. Patient-facing FHIR read of USCDI v1 is free; clinician-facing and bulk FHIR apps need an agreement with the practice and may carry extra fees. Figures are as published on Tebra's partner terms page, accessed 11 Oct 2026, and can change.

Our take

Tebra is one of the more workable mid-market EMRs because scheduling write is actually documented. The work goes into the SOAP envelope details, per-practice keys and permissions, and polling instead of webhooks. Budget the partner fee into your unit economics before you price per practice.

FAQ

Does Tebra have an API?

Yes, two. A SOAP Web Services API for practice-management data and appointment create, update and delete, and a read-only FHIR R4 API for clinical data.

Can you book appointments in Tebra through the API?

Yes. Tebra's SOAP API technical guide documents create, update and delete appointment calls, with per-call rate limits.

How much does the Tebra API cost?

Tebra's published partner terms list a $3,000 yearly developer platform fee plus per-call usage tiers above 10,000 calls a month. Check the current terms before you commit.

Is Kareo's API the same as Tebra's?

Largely. Tebra's SOAP API descends from Kareo's, and older Kareo documentation links now redirect to Tebra's help center.

Sources

Public pages, accessed 11 Oct 2026: Tebra partners · Tebra partner terms · Tebra API terms of use · Tebra FHIR API user guide (PDF) · Tebra API/integration help