Skip to content
Security

API keys

Create, store and revoke personal and organization API keys.

Personal and organization keysPermalink to Personal and organization keys

A personal key belongs to you. An organization key belongs to the organization workspace and is managed from its own screen. Which one you want depends on whether the work belongs to you or to the team.

Creating a keyPermalink to Creating a key

  1. Open API keys

    In the console, go to the API keys screen for the workspace you want the key to belong to.

  2. Name the key

    Give it a name that identifies where it will be installed, so you can revoke the right one later.

  3. Copy it immediately

    The full key is displayed exactly once, at creation.

  4. Store it in a secret manager

    Treat it like a password. Do not commit it, and do not paste it into a shared document.

A key is shown once and cannot be retrieved

This key is shown once. Copy it now and store it securely — you will not be able to see it again. If you lose it, revoke it and create a new one; there is no way to display it a second time.

Afterwards the console lists only a short prefix of each key, which is enough to tell your keys apart without revealing any of them.

Where this happens in the console

Revoking a keyPermalink to Revoking a key

Revoke a key from the same screen. Revocation takes effect immediately and cannot be undone: any application still presenting that key stops working.

Revoke on any suspicion

If a key may have been exposed — in a log, a screenshot, a shared terminal — revoke it and issue a new one. Rotating a key is cheap; an exposed key is not.