How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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 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.

Tebra Clinical API is one of 27 APIs that Tebra publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Clinical. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 12 operations across 12 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.tebra.com/clinical/v1/api.

12 operations 12 paths 2 schemas 12 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.tebra.com/clinical/v1/api
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

Tebra Clinical API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Api-Key (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — Patient-generated API Key from the Tebra Patient Portal (My Account API Access Key). A missing, revoked, or invalid key returns 401 Unauthorized.

Paths & Operations 12

Across 12 paths, the API surfaces 12 operations — 12 GET. Each is listed below with its method, path, parameters, and response codes.

Clinical 12

USCDI-aligned clinical data classes for the authenticated patient.

GET
/patient/allergyIntolerance/medication
Get medication allergies and intolerances
getAllergyIntolerance → 200401
GET
/patient/carePlan
Get care plan
getCarePlan → 200401
GET
/patient/condition/problemList
Get problem list conditions
getProblemList → 200401
GET
/patient/device
Get implantable devices
getDevice → 200401
GET
/patient/diagnosticReport
Get diagnostic reports
getDiagnosticReport → 200401
GET
/patient/encounter
Get encounters
getEncounter → 200401
GET
/patient/goal
Get goals
getGoal → 200401
GET
/patient/immunization
Get immunizations
getImmunization → 200401
GET
/patient/medicationStatement
Get medications
getMedicationStatement → 200401
GET
/patient/observation/vitalSigns
Get vital signs
getVitalSigns → 200401
GET
/patient/procedure
Get procedures
getProcedure → 200401
GET
/patient/smokingStatus
Get smoking status
getSmokingStatus → 200401

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Error (2 properties), ResourceList (2 properties). Each schema is shown below with its type and property counts.

ResourceList
object
Generic container for a list of USCDI-aligned clinical resources (modeled). Actual payloads follow Tebra's clinical data format.
2 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tebra-clinical-api-openapi.yml Raw ↑

Other APIs Tebra publishes across the network.

Tebra Patients API
Tebra Appointments API
Tebra Providers and Practices API
Tebra Billing and Claims API
Tebra Documents SOAP API
Tebra Documents API
Tebra Patient API
Tebra Care Team API
Tebra Condition API
Tebra Device API
Tebra Diagnostic Report API
Tebra Encounter API
Where this information came from

This is an independent, third-party profile of Tebra Clinical API, 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.