The Developers page (under Practice in the sidebar) holds two things: a one-click export of your practice's billing data, and the API keys and specification your team needs to integrate its own systems with Taiga. If your practice only uses the dashboard, the export is still worth knowing about — the rest of the page you can safely skip.
Exporting all of your data
Your data is yours, and you should never have to ask for it. The Your data card on the Developers page hands you the whole of your practice's billing records in one click — no request, no waiting, no export ticket.
Click Export all data and Taiga builds a ZIP file and downloads it to your computer. A large practice's export can take a minute or two to build, so leave the tab open while it works.
What's in the file
The ZIP holds a set of CSV files, one per kind of record, that open in Excel, Numbers, Google Sheets, or any accounting system:
Claims and encounters — every visit and its claim, with patient details, insurance and subscriber information, guarantor, each provider on the claim, diagnoses, status, and dates.
Service lines and charges — the procedures billed on each claim, with modifiers, units, and amounts.
Payments and adjustments — what each payer and patient paid, what was adjusted or denied and why, and every posted financial transaction.
Financial summaries — billed, allowed, paid, and outstanding balances per visit, along with expected amounts under your contracts.
Payer list — the payers referenced elsewhere in the export.
A README.txt in the ZIP lists every file, its row count, and the exact time the data was current. The files share ID columns, so you can join them back together in a spreadsheet or load them straight into another system.
What to know before you export
Who can do it. Anyone on your team with full dashboard access. Front desk accounts don't have the Developers page.
How current it is. The export refreshes nightly, so it reflects your practice as of the previous night rather than the last few minutes. The README states the exact time.
Remittance files. The original ERA files and EOB PDFs your payers sent aren't in this ZIP — the payment and adjustment details from them are. To download the source files themselves, use Download all ERAs or Download EOBs on the Remits page; see Remits and insurance payments.
What's not included. A few dashboard-only records live outside your billing data and aren't in the export: card payments taken at the front desk, patient balance outreach, prior authorization requests, and bank reconciliation. Patients who have never had a claim aren't included either. Ask us and we'll get you any of it.
Export as often as you like — for your accountant, for a year-end archive, for a migration, or simply to keep your own copy.
The Taiga API card
The card at the top of the page gathers everything an integrator needs before writing code:
Open docs opens the developer documentation at docs.taigabilling.com: authentication, guides, and a page for every endpoint.
Open spec and the download button fetch the OpenAPI specification, the source of truth for every endpoint. Most API tooling can generate a typed client from it directly.
Access password unlocks both the docs site and the spec. It is hidden until you click the eye icon, and the copy button copies it without revealing it.
The specification lives at:
https://api.taigabilling.com/openapi.json
When your browser asks for a username and password to open it, enter any username and the access password. Tools such as curl take it as -u taiga:<password>.
API keys
API keys are scoped to your organization: they can only see and act on your practice's data.
Creating a key
Click Add new key
Give it a name that says what it's for (for example "EHR export — production"), and optionally set an expiration
Copy the key and store it somewhere safe — a password manager or secrets vault. Treat it like a password: anyone holding it can read your practice's billing data
Managing keys
The key list shows each key's name, when it was created, its expiration, and when it was last used. Last used is the quickest way to spot keys that are dead weight — if a key hasn't been used in months, open the row's menu and choose Revoke key.
A few habits keep your integration safe:
Create one key per integration, so revoking one doesn't break another
Revoke keys immediately when a vendor or teammate no longer needs access
Never commit keys to code, paste them into tickets, or share them over email
Where to go next
The developer documentation at docs.taigabilling.com covers authentication, endpoints, and guides; use the access password from the Taiga API card to open it. For a filtered spreadsheet of claims rather than the full export, see Claims page: search, filters, columns, and exports. For access questions, help with an export, or integration help, email [email protected].