Back to Integrations
HealthcareLive · 4 actions

Tebra API

Integuru generates a production-ready HTTP API for Tebra, the practice management and EHR platform used by independent medical practices. The integration covers 4 actions for provider listing, location lookup, availability search, and appointment booking, enabling healthcare tech teams to automate patient scheduling workflows programmatically via direct HTTP requests.

npm install -g integuru
Backed byY Combinator100 API calls/month free

4

Verified actions live today

<3 sec

Response latency per call

99.9%+

Reliability rate on generated APIs

24/7

On-call maintenance on Production plans

Integration facts

Authentication
Login flows, including 2FA, handled by Integuru using your own Tebra credentials.
Approach
Direct HTTP requests, with no browser automation or RPA involved.

Endpoints

Available actions

Click an action to expand its parameters

Don't see the action you need?

The actions above cover the most common Tebra integration patterns, but they're not the full picture. Integuru can build additional workflows for any capability the platform exposes. Our Managed Service handles scoping, building, and maintaining custom actions on your behalf, so just let us know what you need.

Guide

Tebra integration guide

Last reviewed: August 2026

Overview

Integuru's Tebra integration provides production-ready HTTP API access to Tebra, the practice management and EHR platform used by independent medical practices, covering 4 actions: list_providers, list_locations, get_available_slots, and book_appointment. Integuru connects via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.

End-to-end appointment booking in four actions. Tebra's scheduling workflow requires knowing which providers and locations exist before querying availability. Integuru's integration follows that same dependency chain: list_providers and list_locations supply the IDs that get_available_slots needs, and get_available_slots returns the start_time that book_appointment requires, so a full scheduling sequence is four ordered API calls.

Tebra was formed through the merger of Kareo and PatientPop, and is widely used by independent practices for both clinical documentation and patient-facing scheduling. The 4 Integuru actions cover the complete appointment booking surface: provider and location discovery, real-time slot availability across a date range, and full appointment creation including new/returning patient status, visit reason, telehealth flag, and optional insurance details. See the Wellsky integration for another Healthcare EHR platform, or browse the full integrations catalogue.


Does Tebra have a public API?

Tebra (formerly Kareo) runs a developer program, but it is partner enrollment rather than self-serve, and the partner tier covers a narrower set of workflows than the Tebra web application shows an authenticated user. Integuru's four Tebra actions authenticate against Tebra's patient scheduling flow with the practice's own credentials and cover provider and location lookup, slot availability and appointment booking.

Looking for the Kareo API? Kareo and PatientPop merged to form Tebra on 2 November 2021, and kareo.com has redirected to tebra.com since 4 December 2023. The Kareo practice management and EHR product is now Tebra, so a Kareo integration request lands on this page; the former Integuru Kareo guide is retired and redirects here.

What is not live. Patient records, clinical notes, claims, insurance policies and document upload are not in the verified catalog. They sit behind the practice's Tebra login, so the Managed Service scopes and builds them for a practice account you control, and they appear on this page once verified against live traffic.


Use Cases

Integuru's Tebra integration covers the provider discovery and appointment booking workflows that independent practice tech teams need to automate.

  • Provider listing: Call list_providers with no parameters to retrieve all providers at the practice, including the provider_id values needed for availability and booking calls.
  • Location listing: Call list_locations with no parameters to retrieve all practice locations, including the location_id values needed for availability and booking calls.
  • Availability search: Call get_available_slots with start_date, end_date (both YYYY-MM-DD), location_id, and provider_id to retrieve open appointment slots across the specified date range. The optional timezone parameter (defaults to America/Los_Angeles) controls the timezone of returned slots. Use page_size (defaults to 100) to control pagination.
  • Appointment booking: Call book_appointment with the required patient fields (first_name, last_name, email, phone, date_of_birth in YYYY-MM-DD, is_new_patient boolean), scheduling fields (start_time in ISO 8601 UTC, location_id, provider_id, reason), and optional fields including is_telehealth, duration, agree_sms_terms, and insurance details (insurance_provider_id, insurance_id_number, insurance_group_number).

Setup Notes

Integuru's Tebra integration authenticates against the Tebra scheduling endpoint. Configure credentials once during Integuru setup; Integuru manages authentication and session handling automatically.

The standard scheduling sequence runs in order: call list_locations and list_providers to retrieve valid IDs, call get_available_slots with those IDs and your target date range to find open slots, then call book_appointment with the start_time from the availability response. The duration in book_appointment should match the duration returned by get_available_slots; it defaults to 30 minutes if omitted.

For book_appointment, is_new_patient is always required. Insurance fields (insurance_provider_id, insurance_id_number, insurance_group_number) are optional; use insurance_provider_id: '121' for self-pay patients. The patient's date_of_birth must correspond to a patient who is at least 13 years old. Full parameter documentation is available for actions marked with the docs badge in the table above.


Get started

Install the CLI and connect your Tebra login:

npm install -g integuru

Or sign in at app.integuru.com, add Tebra, and call the same 4 actions from the dashboard. For patient records, clinical notes, claims or insurance policies, the Managed Service scopes and builds them against a practice account you control.

Guides in Healthcare

Platform API guides in this vertical

Platforms available to request, not yet live

Good to know

Before you start

Can I use it today?
Yes. Every action listed above has been verified against live Tebra traffic. Install the CLI or sign in at app.integuru.com, connect your Tebra account, and start calling the endpoints.
What if Tebra changes or breaks?
On Production plans the Integuru team is on call around the clock, with auth auto-healing included, so target-platform changes get fixed by Integuru rather than by your engineers.
What does it cost?
Start on the Free plan at $0/month with 100 API calls/month. Production starts at $499/month with 24/7 on-call maintenance and auth auto-healing.

FAQ

Frequently asked questions