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

# Authentication

> Create an API key, send it with each request and revoke it.

Every request needs an API key. An API key starts with `cb_live_`.

## Create an API key

1. Sign in to the ClipStake web app.
2. Open **Settings**, then **API keys**.
3. Select **Create API key** and give the key a name.
4. Copy the key. ClipStake shows it only once.

You can have up to 10 active API keys.

## Send the API key

Send the API key in the `Authorization` header of each request.

```bash theme={null}
curl "https://app.clipstake.com/api/v1/brand/brands" \
  --header "Authorization: Bearer cb_live_..."
```

The API does not accept a key in the URL or in a cookie.

## What an API key can read

An API key belongs to your ClipStake account. It reads the brands that you are
a member of, and the campaigns and clips of those brands. It cannot change any
data.

When you are removed from a brand, your API keys stop reading that brand at
once. When your account is no longer active, your API keys stop working.

## Keep the API key secret

* Store the API key on your server.
* Do not put the API key in a browser, a mobile app or a public repository.
* Create one API key for each tool. Then you can revoke one tool without
  stopping the others.

## Revoke an API key

Open **Settings**, then **API keys**, and select **Revoke** on the key. The key
stops working at once. You cannot restore a revoked key.

Requests with a revoked, missing or unknown key return `401 unauthorized`.


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