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

# Authentication

> How to authenticate API requests to CreatorDB

Every API request to the CreatorDB API must be authenticated with an API key, a secure string like `LE6DPZQkR3TQShxofXoD2j8qCBu1-f0jti665m1t50dwDD12W`. The API key is the same as the `api-key` in the request header. Authentication requires the key in string format.

## Getting an API key

To obtain the CreatorDB API key, please contact the CreatorDB sales team at [sales@creatordb.app](mailto:sales@creatordb.app).

<Note>
  API usage is billed to the account that owns the key, not the person making
  the calls. If you're using a key issued by someone else, a teammate or a
  shared organization key, their account is charged for your usage.
</Note>

## Using an API key

Your API requests must include the API key in the authorization header. Below is an example of a `cURL` call to CreatorDB's API:

```
curl --request GET \
  --url 'https://apiv3.creatordb.app/youtube/profile?channelId=UC83AILrMkQSzeGbN0rJV7JA' \
  --header 'api-key:YOUR-API-KEY'
```

## Secure an API key

<Warning>
  Exposing your API key to the public can result in unauthorized usage and potential charges to your account. To prevent unauthorized access, keep your API key private and secure.
</Warning>

For optimal security, follow these guidelines when managing API keys:

* Restrict access to your API key.
* Applying restrictions helps limit unauthorized access and reduces the risk of misuse if the API keys are compromised.
* Regularly review and remove unused API keys to limit potential exposure.
* Rotate API keys periodically, remove outdated ones, and ensure all applications use the updated keys.