Organization administrators can now create multiple named API keys instead of relying on one shared credential for every integration.

Each key has its own name, identifying prefix, creation time, and active or revoked status.

Active keys can be revealed or copied individually. Creating a new key does not replace existing keys, and revoking one key does not disable the organization’s other active keys.

Existing API keys remain available as the organization’s legacy key. All keys retain the same organization-wide API access and share the organization’s existing rate limit; this release does not add per-key permissions.

Open Admin → My Account → Profile as an organization administrator and find the API Keys section.

Create a key, enter a descriptive name for the integration or system that will use it, then copy the credential into that integration.

For rotation without downtime, create and install the replacement key first, confirm it is working, and then revoke the old key.

Use Reveal or Copy on an active key when needed. Revoked keys remain listed for history but cannot authenticate, be revealed, or be copied.

Teams can separate credentials by integration and revoke or rotate one credential without interrupting unrelated API consumers.

Keys remain organization-owned rather than user-owned, so creating additional keys does not change endpoint access or multiply the organization’s rate-limit allowance.