Tebra
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.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Tebra the way a machine reads it — 39 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Tebra scores 65.4/100 (strong), with a separate agent-readiness read of 33/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Tebra's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tebra/"
title="Tebra on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tebra.svg"
alt="Tebra Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/tebra/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tebra/"
title="Tebra on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tebra/card.svg"
alt="Tebra Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Tebra
Each block below is one kind of artifact we hold for Tebra. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 27
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Tebra Patients API
SOAP operations for patient records - GetPatient, GetPatients, GetAllPatients, CreatePatient, UpdatePatient, UpdatePatientsExternalID, and UpdatePrimaryPatientCase. Part of the ...
Tebra Appointments API
SOAP operations for scheduling - GetAppointment, GetAppointments, CreateAppointment, UpdateAppointment, UpdateAppointmentStatus, DeleteAppointment, plus GetAppointmentReasons an...
Tebra Providers and Practices API
SOAP reference-data operations - GetProviders, GetPractices, GetServiceLocations, and GetProcedureCodes - used to resolve the providers, practices, locations, and procedure code...
Tebra Billing and Claims API
SOAP revenue-cycle operations covering charges, encounters, payments, and transactions - GetCharges, GetEncounterDetails, CreateEncounter, UpdateEncounterStatus, GetPayments, Cr...
Tebra Documents API
SOAP operations for attaching and removing documents on practice records - CreateDocument and DeleteDocument - along with external-vendor utilities GetExternalVendors, RegisterE...
Tebra Clinical API
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...
Tebra Documents API
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...
Tebra Patient API
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...
Tebra Allergy Intolerance API
The AllergyIntolerance API from Tebra — 1 operation(s) for allergyintolerance.
Tebra Care Plan API
The CarePlan API from Tebra — 1 operation(s) for careplan.
Tebra Care Team API
The CareTeam API from Tebra — 1 operation(s) for careteam.
Tebra Condition API
The Condition API from Tebra — 1 operation(s) for condition.
Tebra Device API
The Device API from Tebra — 1 operation(s) for device.
Tebra Diagnostic Report API
The DiagnosticReport API from Tebra — 1 operation(s) for diagnosticreport.
Tebra Document Reference API
The DocumentReference API from Tebra — 1 operation(s) for documentreference.
Tebra Encounter API
The Encounter API from Tebra — 1 operation(s) for encounter.
Tebra Goal API
The Goal API from Tebra — 1 operation(s) for goal.
Tebra Immunization API
The Immunization API from Tebra — 1 operation(s) for immunization.
Tebra Location API
The Location API from Tebra — 1 operation(s) for location.
Tebra Medication API
The Medication API from Tebra — 1 operation(s) for medication.
Tebra Medication Request API
The MedicationRequest API from Tebra — 1 operation(s) for medicationrequest.
Tebra Observation API
The Observation API from Tebra — 1 operation(s) for observation.
Tebra Organization API
The Organization API from Tebra — 1 operation(s) for organization.
Tebra Practitioner API
The Practitioner API from Tebra — 1 operation(s) for practitioner.
Tebra Practitioner Role API
The PractitionerRole API from Tebra — 1 operation(s) for practitionerrole.
Tebra Procedure API
The Procedure API from Tebra — 1 operation(s) for procedure.
Tebra Provenance API
The Provenance API from Tebra — 1 operation(s) for provenance.
Scroll within the panel for all 27 ·
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONTebra Data Clinical API
OPEN COLLECTIONTebra Data Clinical Documents API
OPEN COLLECTIONTebra Data Clinical Patient API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Tebra Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Tebra Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Tebra Finops
FINOPSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Tebra — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tebra · machine-readable index on apis.io
This is an independent, third-party profile of Tebra, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.