API keys
Generate API keys so Zapier, lead vendors or your own systems can send leads into Bigly, and delete keys you no longer use.
Opening API Keys from Tenant Details, generating and copying a key, what the Scope column means, replacing a legacy key, and deleting a key safely.
An API key lets another system work with your Bigly account without a username and password. Typical uses are connecting Zapier and letting a lead vendor or your website send leads in as soon as they come in.
To connect Claude, ChatGPT or another AI assistant, don't use this page. Use Connect your AI agent instead.
Before you start
- Open the page from Tenant Details: click your initials, then Tenant Details, then API Keys in the left menu.
- You need permission to change account settings to generate or delete keys. See Team members.
- Each key belongs to the person who created it. You only see and manage your own keys.
Generate a key
- Click + Generate.
- Enter a name in Name of API key (e.g. leads-prod). Use a name that says where the key will be used.
- Click Generate key.
- Click the copy icon next to the key and paste it into the other system.
The key is shown only once: Copy this key now — it won't be shown again. If you lose it, delete it and generate a new one.
Click View the Public API docs → for the technical details your developer or vendor needs.
The API keys page with the name field filled in, the newly generated key in a green box with the copy icon, and the warning that it won't be shown again.
Your keys
The table lists your keys with their Name, Scope, Owner, Created date and Last used date.
| Scope | What it means |
|---|---|
| Locked to this tenant · Public API endpoints only | The key works only for this company account, and only for the public lead and Zapier endpoints. All new keys work this way. |
| Locked to this tenant | The key works only for this company account. |
| Legacy | An older key that isn't locked to one account. It works on every company account its owner can reach. |
Keys don't expire. Delete keys you no longer use.
The API keys table with columns Name, Scope, Owner, Created, Last used and Action, one row showing a Legacy badge and the yellow warning about keys not locked to this tenant.
Replace a legacy key
If you have legacy keys, a warning shows how many aren't locked to this account.
- Generate a new key.
- Update the integration to use the new key.
- Check the integration still works.
- Delete the legacy key.
Delete a key
- Click Delete on the key's row.
- Confirm with Yes, delete it! For a legacy key, type the key's name to confirm.
Any integration using the key stops working straight away. This can't be undone.
Troubleshooting
| Error your integration gets | Cause |
|---|---|
| Access denied! token can only be used for zapier. | The key was used for something other than the public lead and Zapier endpoints. |
| Access denied! token can only be used for associated tenant. please regenerate your API token | The key belongs to a different company account. Generate a key in the right account. |
| The integration stopped working after a teammate left | Keys belong to the person who made them. Have someone generate a new key and update the integration. |