The Developers page (under Practice in the sidebar) is for teams that integrate their own systems with Taiga — submitting encounters programmatically, pulling claim status into internal tools, or wiring up an EHR export. If your practice only uses the dashboard, you can safely ignore this page.
The partner API specification
The OpenAPI specification for Taiga's partner API is published at:
https://api.taigabilling.com/openapi.json
Use Copy, Download, or Open spec to grab it. The spec is the source of truth for every endpoint — most API tooling can generate a typed client from it directly.
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
Developer documentation for the partner API — authentication, endpoints, and guides — lives at docs.taigabilling.com. For access questions or integration help, email [email protected].