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

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.
You cannot create an API key if your account has no credits. Please check your account’s credit balance and purchase additional credits if necessary.
You can get an API key through the CreatorDB app dashboard by following these steps:
  1. Log in to CreatorDB.
  2. Click API.
  3. Click + Create key.
    The Create API key window appears.
Go to the API dashboard
  1. Enter an API key name.
  2. Optional: Set credit usage limit.
    a. Click Add credit usage limit.
    b. Enter the maximum number of credits that can be used with this API key.
  3. Click Create.
    The Save your API key window appears.
Create an API key and set the credit usage limit
  1. Click Copy.
    The API key is now copied to your clipboard and can be used for API calls. Save the API key in a secure location, as it is required for all API requests.
  2. Click Done.
Copy the API key to your clipboard

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

​
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 September 18, 2026