Taiga Partner API
The Taiga Partner API lets approved partner organizations work with billing data programmatically. The API uses Taiga-issued API keys and your organization’s configured billing-provider NPI scope.
Use the guides for the workflow around the API: authentication, request shape, tenant scoping, pagination, and errors. Use the API Reference for exact endpoint paths, request bodies, response schemas, and generated request examples.
Start here
OpenAPI spec
The full machine-readable spec for every endpoint, request body, and response schema is published at https://api.taigabilling.com/openapi.json.
Base URLs
How access works
Your organization must have developer access enabled in Taiga. Once enabled, users in your organization can create API keys from the developer portal.
Each API key belongs to one Taiga organization. Requests made with that key are scoped to that organization’s configured billing-provider NPIs. You do not pass an organization override in API requests.
Typical integration flow
Create the patient before the encounter
Register the patient with POST /patients/v1, create their insurance with POST /coverages/v1 using the patient field, then add the returned coverage id to the patient’s filing_order.coverages with a versioned PUT /patients/v1/{id}/{version}. Encounters reference the resulting patient record; the patients-first sequence walks through each call.
Create encounters from the patient
Call POST /api/encounters/v4/create-from-pre-encounter with the patient’s pre_encounter_patient_id; demographics and coverage are pulled from the patient record. Non-telehealth encounters must include a service facility, and each applicable service line must carry its prior-authorization number. Use BILLABLE only when the encounter is ready for immediate billing processing; validation blockers can still require action before submission.