API2 min read
Several API keys, one for each integration
Create named keys for each system and revoke one without breaking the others.
Create my accountHow it was before
Each account had a single key and secret pair, used by every integration.
How it works now
You create as many keys as you need, each with a name, for example Zapier, n8n or your own system. Revoking one does not affect the others, and revoking asks for your password. The secret appears at creation and can be viewed again for a short window.
What you gain
- One key per integration, with a name
- Revoke one key without breaking the rest
- Password required to revoke
- A viewing window for the secret
Before
A single key and secret pair per account, shared by everything.
Now
- As many keys as you need, each with a name
- Revoking one key does not affect the others
- Revoking asks for your password
- The secret can be viewed again for a short window after creation
Good practice
Use one key per system. If one leaks, you replace only that one.