Tebra

Last reviewed: July 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.

---

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.