#2694-Support multiple named API keys per account

Hi BotSailor Team,

I'd like to request support for creating multiple API keys per account, each with its own name. Right now there is a single API key for the whole account, which makes it hard to run safely once an account is integrated with more than one system.

What I'm asking for

1. Allow a user to generate more than one API key from the API settings page.
2. When creating a key, let the user give it a name or label, such as "Shopify Store", "Zapier", or "Internal CRM".
3. Show all keys in a list with their name, creation date, last-used date, and status.
4. Let the user revoke, disable, or regenerate each key independently, without affecting the others.
5. Show the full key value only once, at creation, as is standard practice.

Why this matters: use cases

1. Different integrations, different keys. One account may connect to Shopify, Zapier, n8n, and a custom backend. With a separate key for each, I can see which system is making calls.
2. Revoke one integration without breaking the rest. If a key leaks, or I stop using a tool, I can revoke only that key. Today I'd have to rotate the single key and update every integration, which causes downtime.
3. Separate environments. I can keep different keys for production, staging, and development, so test traffic never runs on the production key.
4. Agencies and multiple clients. An agency managing several clients can give each client or project its own key. When a client leaves, only their key is revoked.
5. Team and contractor access. I can give a freelancer or developer a dedicated key and remove it when the engagement ends, without exposing the main key.
6. Debugging and auditing. With named keys and a "last used" timestamp, I can quickly tell which integration is sending unexpected requests or hitting rate limits.
7. Safe key rotation. I can create a new key, move one integration over to it, confirm it works, and then delete the old one. There is no hard cutover.

Nice-to-have (optional, for later)

• Per-key permissions or scopes, for example read-only or messaging-only.
• Optional expiry dates for keys.
• Per-key usage and request logs.

Even the basic version, multiple keys with names and individual revocation, would be a big improvement for security and manageability.

Thanks for considering this. Happy to share more details or test it when it's ready.

Done — multi named API keys are live.

You can manage this from Developer Console (/api/developer/console).

• Multiple API keys per account , each with its own name
• Create / edit / enable / disable / delete
• Optional expiry (never, 30/90/365 days, or custom date)
• Permissions:Full access (*) — all current and future endpoints, or
• Per-endpoint access — pick endpoints from a checklist
• Secret is shown only once at creation (copy and store it safely)
• Existing keys are migrated to Default with full access (*) — existing integrations keep working
• API usage log shows which key was used (Default vs named key)

Thank you soo much for quick implementation