Tebra is a healthcare technology company providing an all-in-one operating system for independent medical practices - EHR, practice management, medical billing, patient engagement, and practice growth. Tebra was formed from the 2021 merger of Kareo (practice management and billing) and PatientPop (practice growth), and its developer surface reflects that lineage. Three documented API surfaces exist. The Tebra SOAP Practice Management API - the former Kareo Integration API, still served at webservice.kareo.com - covers patients, appointments, providers, practices, charges, encounters, payments, and transactions, and is partner / administrator gated. The Tebra Clinical Data API is a REST patient-access API documented under tebra.com/macra (ONC / 21st Century Cures Act) with an API Key the patient generates from the Tebra Patient Portal; its documented host (api.tebra.com) no longer resolves in DNS as of this review. Tebra has since published a SMART on FHIR API (R4, US Core STU3 3.1.1, USCDI v1) at fhir.prd.cloud.tebra.com, built on the SmileCDR platform, offering no-charge patient read (GET) access to USCDI clinical resources over 2-legged or 3-legged OAuth 2.0.
Tebra publishes 27 API contracts indexed on the APIs.io network, including Clinical API, Documents API, Patient API, and 24 more. Tagged areas include Healthcare, Practice Management, Electronic Health Records, Medical Billing, and Patient Engagement.
The Tebra catalog on APIs.io includes 1 Spectral governance ruleset.
Tebra’s developer surface includes authentication, documentation, support, engineering blog, pricing, and 30 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Health regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics does not apply to this provider. The published contracts declare
no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's
denominator entirely — not scored zero. A reference or data API is not deficient for being unable to
upsert.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/tebra/"><img src="https://apis.io/badge/tebra/card.svg" alt="Tebra on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Typed Event Surface+6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →
Protected Resource Metadata+5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified) Ask about this →
4 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
SOAP operations for patient records - GetPatient, GetPatients, GetAllPatients, CreatePatient, UpdatePatient, UpdatePatientsExternalID, and UpdatePrimaryPatientCase. Part of the ...
SOAP reference-data operations - GetProviders, GetPractices, GetServiceLocations, and GetProcedureCodes - used to resolve the providers, practices, locations, and procedure code...
SOAP operations for attaching and removing documents on practice records - CreateDocument and DeleteDocument - along with external-vendor utilities GetExternalVendors, RegisterE...
USCDI-aligned clinical data classes for the authenticated patient. Base host (api.tebra.com) is the host documented in Tebra's own "General API Documentation" (Oct 2023) PDF and...
Binary clinical summary documents (e.g. C-CDA). Base host (api.tebra.com) matches the Oct 2023 "General API Documentation" PDF and this spec's servers[], but as of 2026-08-14 it...
Core patient demographic record. Base host (api.tebra.com) matches the Oct 2023 "General API Documentation" PDF and this spec's servers[], but as of 2026-08-14 it returns NXDOMA...
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
aid: tebra
url: https://raw.githubusercontent.com/api-evangelist/tebra/refs/heads/main/apis.yml
x-enrichment:
date: '2026-08-14'
status: enriched
artifacts_added: 20
pass: local-v1
name: Tebra
kind: company
description: Tebra is a healthcare technology company providing an all-in-one operating system for independent medical practices
- EHR, practice management, medical billing, patient engagement, and practice growth. Tebra was formed from the 2021 merger
of Kareo (practice management and billing) and PatientPop (practice growth), and its developer surface reflects that lineage.
Three documented API surfaces exist. The Tebra SOAP Practice Management API - the former Kareo Integration API, still served
at webservice.kareo.com - covers patients, appointments, providers, practices, charges, encounters, payments, and transactions,
and is partner / administrator gated. The Tebra Clinical Data API is a REST patient-access API documented under tebra.com/macra
(ONC / 21st Century Cures Act) with an API Key the patient generates from the Tebra Patient Portal; its documented host
(api.tebra.com) no longer resolves in DNS as of this review. Tebra has since published a SMART on FHIR API (R4, US Core
STU3 3.1.1, USCDI v1) at fhir.prd.cloud.tebra.com, built on the SmileCDR platform, offering no-charge patient read (GET)
access to USCDI clinical resources over 2-legged or 3-legged OAuth 2.0.
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: paid
onboarding: unknown
trial: false
try_now: false
public: false
label: Paid
confidence: high
source:
- plans
- authentication
- security
- sandbox
generated: '2026-11-13'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/tebra.png
tags:
- Healthcare
- Practice Management
- Electronic Health Records
- Medical Billing
- Patient Engagement
- Kareo
- PatientPop
tags_raw:
- Healthcare
- Practice Management
- EHR
- Medical Billing
- Patient Engagement
- Kareo
- PatientPop
created: '2026-07-10'
modified: '2026-08-14'
specificationVersion: '0.23'
apis:
- aid: tebra:tebra-patients-api
name: Tebra Patients API
tags:
- Patients
- Demographics
- SOAP
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://webservice.kareo.com/services/soap/2.1
properties:
- url: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
type: Documentation
- url: https://webservice.kareo.com/services/soap/2.1/KareoServices.svc?wsdl
type: WSDL
description: SOAP operations for patient records - GetPatient, GetPatients, GetAllPatients, CreatePatient, UpdatePatient,
UpdatePatientsExternalID, and UpdatePrimaryPatientCase. Part of the former Kareo Integration API. Access is administrator
gated - a practice System Administrator generates a customer key and grants permissions. Operation names confirmed from
the live WSDL.
- aid: tebra:tebra-appointments-api
name: Tebra Appointments API
tags:
- Appointments
- Scheduling
- SOAP
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://webservice.kareo.com/services/soap/2.1
properties:
- url: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
type: Documentation
- url: https://webservice.kareo.com/services/soap/2.1/KareoServices.svc?wsdl
type: WSDL
description: SOAP operations for scheduling - GetAppointment, GetAppointments, CreateAppointment, UpdateAppointment, UpdateAppointmentStatus,
DeleteAppointment, plus GetAppointmentReasons and CreateAppointmentReason. Tebra does not push updates, so integrators
poll (recommended every 5-15 minutes). Operation names confirmed from the live WSDL.
- aid: tebra:tebra-providers-practices-api
name: Tebra Providers and Practices API
tags:
- Providers
- Practices
- Location
- SOAP
tags_raw:
- Providers
- Practices
- Locations
- SOAP
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://webservice.kareo.com/services/soap/2.1
properties:
- url: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
type: Documentation
- url: https://webservice.kareo.com/services/soap/2.1/KareoServices.svc?wsdl
type: WSDL
description: SOAP reference-data operations - GetProviders, GetPractices, GetServiceLocations, and GetProcedureCodes - used
to resolve the providers, practices, locations, and procedure codes referenced by patients, appointments, and charges.
Operation names confirmed from the live WSDL.
- aid: tebra:tebra-billing-claims-api
name: Tebra Billing and Claims API
tags:
- Billing
- Claims
- Charges
- Payments
- SOAP
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://webservice.kareo.com/services/soap/2.1
properties:
- url: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
type: Documentation
- url: https://webservice.kareo.com/services/soap/2.1/KareoServices.svc?wsdl
type: WSDL
description: SOAP revenue-cycle operations covering charges, encounters, payments, and transactions - GetCharges, GetEncounterDetails,
CreateEncounter, UpdateEncounterStatus, GetPayments, CreatePayment, and GetTransactions. This is the billing and claims
surface of the former Kareo Integration API. Operation names confirmed from the live WSDL.
- aid: tebra:tebra-documents-soap-api
name: Tebra Documents SOAP API
tags:
- Documents
- Attachments
- SOAP
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://webservice.kareo.com/services/soap/2.1
properties:
- url: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
type: Documentation
- url: https://webservice.kareo.com/services/soap/2.1/KareoServices.svc?wsdl
type: WSDL
description: SOAP operations for attaching and removing documents on practice records - CreateDocument and DeleteDocument
- along with external-vendor utilities GetExternalVendors, RegisterExternalVendor, GetCustomerIdFromKey, and GetThrottles.
Operation names confirmed from the live WSDL.
- aid: tebra:tebra-clinical-api
name: Tebra Clinical API
description: USCDI-aligned clinical data classes for the authenticated patient. Base host (api.tebra.com) is the host documented
in Tebra's own "General API Documentation" (Oct 2023) PDF and matches this spec's servers[], but as of 2026-08-14 it returns
NXDOMAIN on public DNS resolvers (8.8.8.8, 1.1.1.1, system resolver) - the documented host no longer resolves. See lifecycle/
for detail; Tebra's newer FHIR API (tebra:tebra-fhir-api) covers most of the same USCDI resource set and is live.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://api.tebra.com/clinical/v1/api
tags:
- Clinical
properties:
- type: OpenAPI
url: openapi/tebra-clinical-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2023/10/General_API_Documentation-Tebra.pdf
- type: PostmanCollection
url: collections/tebra-clinical.postman_collection.json
- type: Overlay
url: overlays/tebra-clinical-api-overlay.yaml
- aid: tebra:tebra-documents-api
name: Tebra Documents API
description: Binary clinical summary documents (e.g. C-CDA). Base host (api.tebra.com) matches the Oct 2023 "General API
Documentation" PDF and this spec's servers[], but as of 2026-08-14 it returns NXDOMAIN on public DNS resolvers - the documented
host no longer resolves. See lifecycle/ for detail.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://api.tebra.com/clinical/v1/api
tags:
- Documents
properties:
- type: OpenAPI
url: openapi/tebra-documents-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2023/10/General_API_Documentation-Tebra.pdf
- type: PostmanCollection
url: collections/tebra-clinical.postman_collection.json
- type: Overlay
url: overlays/tebra-documents-api-overlay.yaml
- aid: tebra:tebra-patient-api
name: Tebra Patient API
description: Core patient demographic record. Base host (api.tebra.com) matches the Oct 2023 "General API Documentation"
PDF and this spec's servers[], but as of 2026-08-14 it returns NXDOMAIN on public DNS resolvers - the documented host
no longer resolves. See lifecycle/ for detail.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://api.tebra.com/clinical/v1/api
tags:
- Patients
tags_raw:
- Patient
properties:
- type: OpenAPI
url: openapi/tebra-patient-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2023/10/General_API_Documentation-Tebra.pdf
- type: PostmanCollection
url: collections/tebra-clinical.postman_collection.json
- type: Overlay
url: overlays/tebra-patient-api-overlay.yaml
- aid: tebra:tebra-careteam-api
name: Tebra Care Team API
description: The CareTeam API from Tebra — 1 operation(s) for careteam.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- CareTeam
properties:
- type: OpenAPI
url: openapi/tebra-careteam-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-condition-api
name: Tebra Condition API
description: The Condition API from Tebra — 1 operation(s) for condition.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Condition
properties:
- type: OpenAPI
url: openapi/tebra-condition-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-device-api
name: Tebra Device API
description: The Device API from Tebra — 1 operation(s) for device.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Device
properties:
- type: OpenAPI
url: openapi/tebra-device-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-diagnosticreport-api
name: Tebra Diagnostic Report API
description: The DiagnosticReport API from Tebra — 1 operation(s) for diagnosticreport.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- DiagnosticReport
properties:
- type: OpenAPI
url: openapi/tebra-diagnosticreport-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-encounter-api
name: Tebra Encounter API
description: The Encounter API from Tebra — 1 operation(s) for encounter.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Encounter
properties:
- type: OpenAPI
url: openapi/tebra-encounter-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-goal-api
name: Tebra Goal API
description: The Goal API from Tebra — 1 operation(s) for goal.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Goal
properties:
- type: OpenAPI
url: openapi/tebra-goal-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-immunization-api
name: Tebra Immunization API
description: The Immunization API from Tebra — 1 operation(s) for immunization.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Immunization
properties:
- type: OpenAPI
url: openapi/tebra-immunization-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-location-api
name: Tebra Location API
description: The Location API from Tebra — 1 operation(s) for location.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Location
properties:
- type: OpenAPI
url: openapi/tebra-location-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-medication-api
name: Tebra Medication API
description: The Medication API from Tebra — 1 operation(s) for medication.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Medication
properties:
- type: OpenAPI
url: openapi/tebra-medication-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-observation-api
name: Tebra Observation API
description: The Observation API from Tebra — 1 operation(s) for observation.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Observation
properties:
- type: OpenAPI
url: openapi/tebra-observation-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-organization-api
name: Tebra Organization API
description: The Organization API from Tebra — 1 operation(s) for organization.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Organization
properties:
- type: OpenAPI
url: openapi/tebra-organization-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-practitioner-api
name: Tebra Practitioner API
description: The Practitioner API from Tebra — 1 operation(s) for practitioner.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Practitioner
properties:
- type: OpenAPI
url: openapi/tebra-practitioner-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-procedure-api
name: Tebra Procedure API
description: The Procedure API from Tebra — 1 operation(s) for procedure.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Procedure
properties:
- type: OpenAPI
url: openapi/tebra-procedure-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-provenance-api
name: Tebra Provenance API
description: The Provenance API from Tebra — 1 operation(s) for provenance.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- Provenance
properties:
- type: OpenAPI
url: openapi/tebra-provenance-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-allergy-intolerance-api
name: Tebra Allergy Intolerance API
description: The Allergy Intolerance API from Tebra — 1 operation(s) for allergy intolerance.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- AllergyIntolerance
tags_raw:
- Allergy Intolerance
properties:
- type: OpenAPI
url: openapi/tebra-allergy-intolerance-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-care-plan-api
name: Tebra Care plan API
description: The Care plan API from Tebra — 1 operation(s) for care plan.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- CarePlan
tags_raw:
- Care plan
properties:
- type: OpenAPI
url: openapi/tebra-care-plan-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-document-reference-api
name: Tebra Document Reference API
description: The Document Reference API from Tebra — 1 operation(s) for document reference.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- DocumentReference
tags_raw:
- Document Reference
properties:
- type: OpenAPI
url: openapi/tebra-document-reference-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-medication-request-api
name: Tebra Medication Request API
description: The Medication Request API from Tebra — 1 operation(s) for medication request.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- MedicationRequest
tags_raw:
- Medication Request
properties:
- type: OpenAPI
url: openapi/tebra-medication-request-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
- aid: tebra:tebra-practitioner-role-api
name: Tebra Practitioner Role API
description: The Practitioner Role API from Tebra — 1 operation(s) for practitioner role.
humanURL: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
baseURL: https://fhir.prd.cloud.tebra.com/fhir-request
tags:
- PractitionerRole
tags_raw:
- Practitioner Role
properties:
- type: OpenAPI
url: openapi/tebra-practitioner-role-api-openapi.yml
- type: Documentation
url: https://www.tebra.com/macra
- type: APIReference
url: https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- type: DeveloperPortal
url: https://fhir.prd.cloud.tebra.com/appsphere/portal/#/login
- type: Sandbox
url: sandbox/tebra-sandbox.yml
common:
- type: CapabilityMap
url: capabilities/tebra-capability-edges.yml
name: Tebra Business Capability Map
- type: Overlay
url: overlays/tebra-fhir-api-overlay.yaml
- type: X-MCPServerCandidate
url: mcp/tebra-mcp.yml
note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
url: skills/tebra-read-patient-clinical-data.md
- type: OAuthScopes
url: scopes/tebra-scopes.yml
- type: AgenticAccess
url: agentic-access/tebra-agentic-access.yml
- type: TrustCenter
url: security/tebra-trust-center.yml
- type: Compliance
url: security/tebra-trust-center.yml
- type: DomainSecurity
url: security/tebra-domain-security.yml
- type: Authentication
url: authentication/tebra-authentication.yml
- type: LinkedIn
url: https://www.linkedin.com/company/tebra
- type: Website
url: https://www.tebra.com
- type: Documentation
url: https://helpme.tebra.com/Tebra_PM/12_API_and_Integration
- type: Support
url: https://helpme.tebra.com
- type: Blog
url: https://www.tebra.com/theintake
- type: Pricing
url: https://www.tebra.com/pricing
- type: TermsOfService
url: https://www.tebra.com/tebra-terms-of-service
- type: PrivacyPolicy
url: https://www.tebra.com/privacy-policy
- type: StatusPage
url: https://status.tebra.com
- type: Plans
url: plans/tebra-plans-pricing.yml
- type: RateLimits
url: rate-limits/tebra-rate-limits.yml
- type: FinOps
url: finops/tebra-finops.yml
- type: Conformance
url: conformance/tebra-conformance.yml
- type: Lifecycle
url: lifecycle/tebra-lifecycle.yml
- type: ErrorCatalog
url: errors/tebra-problem-types.yml
- type: Conventions
url: conventions/tebra-conventions.yml
- type: DataModel
url: data-model/tebra-data-model.yml
- type: LLMsTxt
url: llms/tebra-llms.txt
- type: Packages
url: packages/tebra-packages.yml
- type: UsageTerms
url: terms/tebra-terms-of-service.yml
- type: DataProcessing
url: privacy/tebra-privacy-policy.yml
- type: Attestations
url: compliance/tebra-compliance.yml
- type: Eligibility
url: eligibility/tebra-eligibility.yml
- type: AIPreferences
url: ai-preferences/tebra-ai-preferences.yml
- type: DataLicense
url: data-license/tebra-data-license.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
Tebra API — frequently asked questions
Does Tebra have an API?
Yes. APIs.io lists 27 APIs from Tebra, including Tebra Patients API, Tebra Appointments API and Tebra Providers and Practices API, and 24 more.
Is there an OpenAPI specification for the Tebra API?
Yes. APIs.io indexes 22 OpenAPI specifications for Tebra, each linked for download from this page.
How do I authenticate with the Tebra API?
Tebra documents its authentication (apiKey/oauth2 · 3 schemes). The details are profiled on APIs.io as Tebra Authentication.
How much does the Tebra API cost?
Tebra publishes its prices; its All in One plan is Custom solution to meet the unique needs of your practice. as of 2026-10-28. APIs.io lists 7 pricing plans for Tebra, with each plan's price, limits and inclusions under Pricing on this page.
Is the Tebra API ready for AI agents?
Tebra has a Kin Score of 59.3 out of 100 (strong) and an Agent Readiness score of 30.2 (agent-ready), scored by API Evangelist on 2026-11-13.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.