> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revbridge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# API Keys

> Create secret keys for your servers and the publishable key for your website, and revoke them when you no longer need them.

Open **Settings → API Keys**. Keys belong to the workspace selected at the top of the app; switch workspaces to manage another account's keys. The page has two tabs.

| Tab | Key | Use it in | What it can do |
| - | - | - | - |
| **Secret keys** | `rbak_…` | Your servers only | Whatever permissions you give it: send messages, read stats, manage webhooks and more |
| **Publishable key** | `rbpk_…` | Your website or app, through the [Web SDK](https://docs.revbridge.ai/developer/web-sdk.md) | Only send events. It can't read data or send messages, so it's safe to expose |

> [!WARNING]
>
> Never put a secret key in a website, mobile app or any code that runs on your customers' devices. Use the publishable key there.

## Create a secret key

**1. Click New API key**

On the **Secret keys** tab.

**2. Name it**

Use a name that says where the key will run, such as "Production backend".

**3. Choose the permissions**

Permissions are grouped by area, such as Email, SMS, WhatsApp, Webhooks and Stats. New keys start with **Read email**, **Send email**, **Read webhooks**, **Manage webhooks** and **Read stats**. Select only what this integration needs; **Reset to defaults** brings back the starting set.

**4. Copy the key**

Click **Create**. The full key is shown only once: copy it, store it somewhere safe, then click **I have saved it**.

The list shows each key's name, ID, status, when it was last used and when it was created.

## Disable or delete a key

* **Disable** stops a key from working without deleting it. **Enable** turns it back on.
* **Delete** removes it for good. Applications using it stop working immediately, and this can't be undone.

Keys marked **System** are **Managed by RevBridge** and can't be changed here.

## The publishable key

On the **Publishable key** tab, click **Generate publishable key**, then **Copy** it into your Web SDK snippet.

**Regenerate** creates a new key. The current one stops working once your sites and apps switch to the new one, so update your install snippet right after regenerating.

## Next steps

> **[Authentication](https://docs.revbridge.ai/developer/authentication.md)**
>
> How to send your key with each request.

> **[Web SDK](https://docs.revbridge.ai/developer/web-sdk.md)**
>
> Install the SDK on your site with the publishable key.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.