Changelog

API keys: personal keys for you, workspace keys for your integrations

An API key used to belong to whoever made it, which caused two problems. A key could see more than the person behind it. And when that person left, every integration built on their key stopped working. We've split keys into two kinds to fix both.

Personal keys, for you

A personal key acts as you. It can see and do exactly what you can, checked on every request, and every teammate can now manage their own.

You can now:

  • Create, rename, rotate and revoke your own keys from your account settings
  • Pick how long a key lasts: 30 days, 90 days (the default), 1 year or no expiry
  • Trust that a key never sees more than its creator, and stops working when they leave the team

Every key you already have is now a personal key. If one was made by a teammate who can only see their own or their team's conversations, it now sees only those too.

Workspace keys, for integrations

A workspace key belongs to the workspace, not to a person. It has its own role, so your integrations keep running when people come and go.

You can now:

  • Create a workspace key with exactly the role it needs
  • Keep it working when the person who made it leaves
  • Rely on a guardrail: you can only give a key a role whose permissions you hold, and only an admin can give one the Owner role

For admins

  • See every teammate's personal keys, with their scopes, expiry and last use
  • Revoke any key
  • Turn off new personal keys for the whole workspace

Where to find it: your own keys are in your account settings under API keys. Workspace keys and the full list of keys are in Settings > Developers.

Live on Quackback Cloud now, and in Quackback 0.15 for self-hosted teams.