Skip to main content
The CreatorDB API follows RESTful API conventions, which allow you to request and receive information from specific links (also known as URIs or endpoints). This article explains how these URIs are structured and how to use them. For details on the requirements for each URI, see the API reference.

​
HTTP Methods

The CreatorDB API accepts the standard HTTP methods: GET and POST.
  • GET: The GET request retrieves data from the server without modifying the data.
  • POST: The POST request sends data to the server. For example, when you make a POST request to add filters to a social media platform’s advanced search, the specified filters are in JSON format in the request body.

​
Request body parameters

You must include a JSON request body in POST requests. For details, see the API reference about the available request parameters for each endpoint and the required fields.

​
Pagination

CreatorDB API uses optional parameters in the request body to paginate advanced search results. You can paginate your API requests using the offset parameter in the request body. Note that you must paginate results and make multiple API calls when more than 2,500 results are returned in an API request. The CreatorDB API can only get 2,500 results per API call. To get records from 2,501 and above, use the offset parameter in the request body to paginate your results. For example, if you get 10,000 records in an API call, you must make four API calls to get all the data. After retrieving 2,500 results in the first API call, you must set the offset parameter to 2,501, 5,001, and 7,501 to get the remaining data. Otherwise, by default, you can only get the first 2,500 results in every call. 
{
  "maxResults": 100,
  "sortBy": "subscribers",
  "offset": 2501,
  "desc": true,
  "filters": [
    {
      "filterKey": "subscribers",
      "op": ">",
      "value": 10000
    }
  ]
}
In the above request body example, the advanced filter will sort by the creator’s number of subscribers and return 100 results after the 2,501 record.

​
Response body parameters

All API call responses include headers and an optional JSON-formatted body. The API Reference contains the details for each specific API call.

​
Path parameters

Group 5.png Resource names and request parameters in an API URL provide instructions on structuring your API call. Resource names cannot be modified, but the parameters must be replaced with real values from a social media account or your CreatorDB account. You will need to replace the apiId parameter with your API key. For example, you need the creator’s YouTube channel ID and your CreatorDB account API key to get a YouTube creator’s basic data. The parameter values that need to be replaced are in curly brackets (""): https://dev.creatordb.app/v2/youtubeBasic/?youtubeId={YouTube_channel_ID}&apiId={CreatorDB_API_key} For detailed instructions, see Quickstart. Your final URL will resemble the following: https://dev.creatordb.app/v2/youtubeBasic/?youtubeId=UCm-X6o81nRsXQTmqpyArkBQ&apiId=LE6DPZQkR3TQShxofXoD2j8qCBu1-f0jti665m1t50dwDD12W
Last modified on February 9, 2026