Ignition APIConnect Ignition without building on its API
Ignition has a REST API. Tiered: the read-only Reporting API needs the Pro+ or Enterprise plan (admin users), the read/write Core API is closed beta for enrolled practices on any plan, the Partner API is for approved partners only, and MCP is on all plans. If you're reading the docs because you need Ignition to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Ignition and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0 authorization code
- AccessPlan-dependent
What the Ignition API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 authorization code (PKCE for the Core API; 'reporting' and 'partner' scopes)
- Who can get access
- Tiered: the read-only Reporting API needs the Pro+ or Enterprise plan (admin users), the read/write Core API is closed beta for enrolled practices on any plan, the Partner API is for approved partners only, and MCP is on all plans.
- What it covers
- Clients/contacts, proposals, services, invoices, payments/billing, deals, and financial reporting data (settlements, fees, disbursals, collections), plus lifecycle webhooks in the Core/Partner APIs.
- Limits
- Reporting API allows 1,000 requests per hour per practice, and MCP is capped at 2,000 requests/hour per practice and 1,000/hour per OAuth client.
- Worth knowing
- The Reporting API is read-only, and write access (Core API) is limited to practices enrolled in the closed beta.
Official docs: developers.ignitionapp.com. Checked September 2026. Vendors change access terms, so confirm with Ignition before you build.
Building on the Ignition API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Ignition credentials, and manage tokens and refreshes. | Connect your Ignition account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Ignition task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Ignition work off someone's desk, the build is the slow part.
What teams usually want the Ignition API for
Proposal to open engagement
Caddi turns an accepted Ignition proposal into the client, contacts, and engagement records in practice management.
Independence and conflict check
Caddi runs the independence and conflict check on every new engagement, attaches the result, and routes exceptions to a human.
Billing setup and books sync
Caddi writes the engagement's billing terms to the ledger so the first invoice matches the letter.
Ignition API questions
Does Ignition have an API?
Yes. Ignition has a REST API, authenticated with OAuth 2.0 authorization code (PKCE for the Core API; 'reporting' and 'partner' scopes). The official documentation is at https://developers.ignitionapp.com/docs.
How do I get access to the Ignition API?
Tiered: the read-only Reporting API needs the Pro+ or Enterprise plan (admin users), the read/write Core API is closed beta for enrolled practices on any plan, the Partner API is for approved partners only, and MCP is on all plans.
Does the Ignition API have rate limits?
Reporting API allows 1,000 requests per hour per practice, and MCP is capped at 2,000 requests/hour per practice and 1,000/hour per OAuth client.
Can I connect Ignition to my other tools without writing code against its API?
Yes. With Caddi you show the Ignition task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Ignition and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Ignition with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Ignition is reviewed before it runs in production, and every run is logged.
Connect Ignition without the build.
Drop your work email and pick a time. We'll show you Caddi running your Ignition workflow end to end.