How to set up API access to Ignition
Ignition (the client engagement, proposals, and payments app at ignitionapp.com, formerly Practice Ignition) does not currently offer a self-serve public API where you generate your own API key from a settings page. There is no "create API key" screen in your account. Instead, the supported way to let another tool read your Ignition data programmatically is to authorise a connection through Zapier, which links Ignition to thousands of other apps. When you connect, you log in to Ignition and authorise the connection rather than copying out a secret key, and an administrator can see every connected user and revoke any connection at any time. If you genuinely need direct REST API access for a custom build, that is handled as a partner or approved-integration arrangement with Ignition rather than something you can switch on yourself. This guide explains how to authorise programmatic access the supported way, how to remove it, and how to keep any credential you are given safe.
Keep this credential safe
Treat any API token or secret Ignition issues you exactly like a password: anyone who has it can access whatever data it allows, so guard it carefully. Where the product lets you, scope access to read-only and to only the data that is actually needed. Never send a token in plaintext email or chat; share it through a secure method such as a password-manager share link. Prefer the authorised Zapier connection (where you log in rather than expose a key) over copying secrets around. Delete or rotate any token, and revoke any connection, the moment it is no longer needed.
Access to grant
Authorised Zapier connection (login and authorise, not a copy-paste key). Direct REST API access is partner or approval-gated.
Who you're granting access to
- The developer, consultant, or tool that will read your data through the connection, for example a Zapier automation or an approved integration partner.
Before you start
- You need to be an Administrator on your Ignition account to authorise or revoke a connection.
- A Zapier account (or another tool that connects to Ignition through Zapier) if you are using the no-code path.
- For direct REST API access: confirmation from Ignition that your use case is approved, as the API is not self-serve.
Step by step
- 1
Confirm there is no self-serve API key
Sign in to Ignition and check your account settings. Ignition does not expose a "create API key" or "developer" screen for customers, so you will not find a key to copy. Programmatic access is done by authorising a connection (below), not by generating a secret.
- 2
Connect Ignition through Zapier
Log in to Zapier (or the tool that uses Zapier under the hood) and add Ignition as a connected app. When prompted, you authorise the connection by signing in to your Ignition account and approving access, rather than pasting an API key. Only an Ignition Administrator should authorise the connection.
- 3
Build the workflow or hand the connection over
Once the connection is authorised, the tool can use Ignition triggers and actions to read your data and automate tasks. If a developer or consultant is doing this on your behalf, authorise it from your own account so you stay in control, or have them set it up while you watch, and never share your Ignition login password.
- 4
For direct REST API access, ask Ignition first
If a no-code connection is not enough and you need direct REST API access for a custom build, contact Ignition support to ask about partner or approved-integration access, because it is not something you can enable yourself. If Ignition issues you any API token or secret as part of that, treat it like a password from the moment you receive it.
Removing access afterwards
- Sign in to Ignition as an Administrator and open Apps.
- Click Zapier to see the list of users and tools that have connected to your account.
- Choose Revoke next to the connection you want to remove. Access ends immediately. Note that revoking will break any active Zaps built on that connection, so check it is no longer needed first.
- If Ignition issued you a direct API token under a partner arrangement, ask Ignition support to rotate or revoke it once the work is finished.
If that option is not available
Because Ignition has no self-serve API key, if you only need someone to review your setup, the simplest option is to add them as a user with the appropriate role, or to share your screen on a short call and walk them through Ignition live. For anything requiring direct REST API access, contact Ignition support to ask about partner or approved-integration access. You should never need to share your password.
Frequently Asked Questions
No. Ignition does not offer a self-serve API key that you create from a settings page. The supported way to give a tool programmatic access to your data is to authorise a connection through Zapier. Direct REST API access is handled as a partner or approved-integration arrangement, not something you switch on yourself.
Prefer the Zapier connection, where you log in and authorise rather than copy out a secret. If Ignition ever issues you a direct API token, treat it like a password: scope it to read-only where possible, share it only through a secure method such as a password-manager share link rather than plaintext email or chat, and delete or rotate it as soon as it is no longer needed.
Sign in to Ignition as an Administrator, open Apps, click Zapier, and choose Revoke next to the connection you want to remove. Access ends immediately. Revoking will break any active Zaps built on that connection, so confirm it is no longer needed first. For a direct partner token, ask Ignition support to rotate or revoke it.
You must be an Administrator on your Ignition account to authorise or revoke a connection. If a developer or consultant is helping, authorise the connection from your own account so you keep control, or have them set it up while you watch. Never hand over your Ignition login password.
Contact Ignition support to ask about partner or approved-integration access, because the API is not self-serve. If they grant access and issue a token or secret, secure it like a password straight away, scope it as tightly as the product allows, and rotate or revoke it when the project is done.
Related guides
Steps last checked against Ignition on 2026-06-09.
Based on official Ignition documentation: Ignition Help Centre: Ignition and Zapier, Ignition Help Centre: Apps & Integrations, Ignition: Zapier integration. Ignition is a trademark of its respective owner; this guide is independent and for instruction only.
Want this handled for you?
Clever Ops connects and automates the systems mid-market businesses already run. Book a free assessment and we will map your stack.