Skip to main content
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.

​
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:bede5c316fe8988bd505df2af117f599319cd4f546697cb38b20403923175b01'

​
Secure an API key

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.
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.
Last modified on February 24, 2026