What we do
Tools
Industries
Department
How we workLet's talk →
Home/Tebra
Tebra, formerly Kareo

The Tebra API: What a SOAP Integration Can Read, Write and Miss

If you opened Tebra's developer material expecting JSON and webhooks, the first surprise is the WSDL. The Tebra API, the same service Kareo published before the rename, is a SOAP web service. It reads most of the practice management record, writes a short list of things, and only tells you about a change when you ask for it.

Where Tebra stops

It runs the schedule and billing, but insurance eligibility, referral tracking and cross-system reporting still fall on staff.

Stuck on Tebra? Let's solve it →

Your first Tebra SOAP request, in order

Based on Tebra's own API and integration help pages.

  1. 1

    Have a System Administrator generate the customer key

    The key is created inside the Tebra application by a System Administrator. Every call carries it alongside a user's login, so it identifies which customer account you're working in.

  2. 2

    Set up the user the integration signs in as

    The same administrator sets the security permissions that user needs. Give it a login of its own, so the integration's activity isn't mixed up with a staff member's.

    Watch for: permissions set too narrowly. Calls fail for records the user isn't allowed to see, and it looks like an API problem when it's a settings one.

  3. 3

    Read the technical guide and the terms

    Tebra publishes an API Integration Technical Guide and API terms of use. The guide has the request and response shapes for each call.

  4. 4

    Start with reference data

    Call a Get for practices, providers or service locations first. They're small, they change rarely, and they prove the key and login work before you touch patient records.

  5. 5

    Poll for changes with the last-modified filter

    Tebra's guidance is to poll every 5 to 15 minutes and narrow each request with the last-modified parameter, so you fetch what changed instead of everything.

Which Tebra records the API reads, creates or changes

Record Calls Tebra offers What that means for a build
Patients Get (one or in bulk), create, update The only record type you can update. Anything that edits demographics goes through here.
Appointments Get (one or in bulk), create, delete There's no update call. Agree with the front desk what a reschedule from another system should become before you build it.
Encounters Get details, create Created from outside, then worked in Tebra as normal.
Payments Get, create Readable for an accounting sync, and creatable when payments are taken somewhere else.
Charges, transactions Get only Fine for reporting and month-end totals. Changes stay in Tebra.
Practices, providers, service locations, procedure codes Get only Reference data to map once and refresh now and then.

How a Tebra sync slowly falls out of step

Waiting for a push that never comes

How you'll know: The other system only updates when someone remembers to run an export.

Fix: The SOAP service answers requests. It doesn't announce changes. Schedule the poll, and log when each run starts and what it fetched.

Pulling everything on every run

How you'll know: Each poll takes longer as the practice grows, and runs start overlapping.

Fix: Filter on last-modified and store the time of the last good run, so each request only asks for the gap.

A second copy of a patient after a rerun

How you'll know: A migration or intake sync was run twice, and the front desk now merges duplicates.

Fix: Tebra documents external IDs for this. Store your own system's ID on the record and match on it before creating anything.

Expecting HL7 from it

How you'll know: A lab or device vendor asks for an HL7 feed from the Tebra API.

Fix: Tebra states the API doesn't support HL7 messaging. That vendor needs a different route, so settle it before the project is planned around one.

Opening a support case without the XML

How you'll know: A call starts failing, and the ticket to Tebra goes nowhere.

Fix: Tebra supports its API, not your code, and asks for the request and response XML. Log both for every failed call so you have them ready.

Tebra questions, from the product to the API

What is Tebra?

Practice management, EHR and billing software for independent medical practices, run in the cloud. Scheduling, charting, claims and patient communication sit in one platform.

Is Tebra the same as Kareo?

It's the same platform under a newer name. Kareo merged with PatientPop in 2021, and the combined company became Tebra in 2022. The Kareo API is now the Tebra API, and Tebra's help pages still link some Kareo-era guides. Our Kareo page covers the rename for practices.

Does the Tebra API send webhooks when something changes?

Tebra's API pages don't describe any. The documented pattern is polling every 5 to 15 minutes, filtered on last-modified, so a change in Tebra shows up downstream within one polling interval.

How much does Tebra cost?

Tebra doesn't publish flat pricing. The price depends on practice size and which parts you take, such as billing, EHR or patient experience tools, so you need a quote from Tebra.

Where do I log into Tebra?

At tebra.com, using the provider login or the patient portal depending on who you are. An old Kareo bookmark is worth replacing, since the platform now runs under the Tebra name. The patient side is covered on our Tebra patient portal page.

Who writes and maintains a Tebra API integration for a practice?

A developer who's comfortable with SOAP, because Tebra supports the service and not the code built on it. n-frames builds these for practices: the polling job, the external-ID matching, the accounting sync, and logging every failed call with its XML.

Jobs worth putting on the Tebra API

Month-end totals without the rebuild. Payments, charges and transactions are all readable, so n-frames builds the sync that posts totals to your accounting tool and flags anything that doesn't match, instead of a bookkeeper rebuilding the same figures every month.

Referral sources that reach a report. Where a referring provider is captured on the patient or appointment, the data can be pulled on a schedule and rolled up into a monthly view inside the practice.

Records arriving from somewhere else. Patients and appointments from another system can be created through the API, matched on external IDs so a rerun doesn't duplicate them. Tebra's help pages cover migrating patient data in this way, and it's also how a one-time move from an older system can be scripted and checked.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.