Tebra · Authentication Profile

Tebra Authentication

Authentication

Tebra secures its APIs with apiKey and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and clientCredentials flow(s).

HealthcarePractice ManagementEHRMedical BillingPatient EngagementKareoPatientPop
Methods: apiKey, oauth2 Schemes: 3 OAuth flows: authorizationCode, clientCredentials API key in: header

Security Schemes

apiKeyAuth apiKey
· in: header (X-Api-Key)
smartOnFhirAuthCode oauth2
· flows: authorizationCode
smartOnFhirClientCredentials oauth2
· flows: clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-08-14'
method: searched
source: openapi/tebra-clinical-api-openapi.yml, openapi/tebra-documents-api-openapi.yml, openapi/tebra-fhir-api-openapi.yml,
  openapi/tebra-patient-api-openapi.yml
docs:
- https://www.tebra.com/wp-content/uploads/2025/05/Tebra-FHIR-API-User-Guide.pdf
- https://www.tebra.com/wp-content/uploads/2023/10/General_API_Documentation-Tebra.pdf
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
  - clientCredentials
schemes:
- name: apiKeyAuth
  type: apiKey
  in: header
  parameter: X-Api-Key
  description: Patient-generated API Key from the Tebra Patient Portal (My Account > API Access
    Key). A missing, revoked, or invalid key returns 401 Unauthorized.
  sources:
  - openapi/tebra-clinical-api-openapi.yml
  - openapi/tebra-documents-api-openapi.yml
  - openapi/tebra-patient-api-openapi.yml
- name: smartOnFhirAuthCode
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://fhir.prd.cloud.tebra.com/smartauth/oauth/authorize
    tokenUrl: https://fhir.prd.cloud.tebra.com/smartauth/oauth/token
    scopes: 24
  description: SMART on FHIR 3-legged OAuth 2.0 authorization-code flow for user-facing (patient/provider)
    applications. Authorization/token URLs are confirmed verbatim from the Tebra FHIR API User
    Guide. The scope list below is DERIVED, not verbatim - Tebra's guide instructs developers
    to "enter the SMART scopes required" without publishing an enumerated list, so these are
    the standard SMART v1 `patient/<Resour
  sources:
  - openapi/tebra-fhir-api-openapi.yml
- name: smartOnFhirClientCredentials
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://fhir.prd.cloud.tebra.com/smartauth/oauth/token
    scopes: 3
  description: SMART on FHIR 2-legged OAuth 2.0 client-credentials flow for backend services
    applications (no end-user present). Token endpoint is confirmed verbatim from the Tebra
    FHIR API User Guide; Tebra currently supports only the Client Credentials workflow (not
    JWKS-based backend auth). Scope strings below are DERIVED (`system/<Resource>.read`, standard
    SMART v1 syntax), not verbatim - see note above.
  sources:
  - openapi/tebra-fhir-api-openapi.yml

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/tebra-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.