Overview
Enrich your influencer marketing data with our collected and AI model inferred information. CreatorDB has a creator database of over 30 million creators across YouTube, Instagram and TikTok that is updated almost daily. We have leveraged data and insights gained from our influencer marketing agency team to develop data solutions that can fit a wide variety of use cases, and includes a broad set of proprietary data including:
Audience demographics (Age range, countries and gender breakdown)
- Sponsored content for YouTube and Instagram
- Sponsorship cost estimates
- Topics and niches
- Creator emails
- and much more
Version 3 of our API is currently in development and is accepting applications from our enterprise users for a closed beta program for active testing, feedback, and iterative improvements.
The number of API calls you can make every second or per day depends on the amount of API credits you have. The more API credits you have, the more API calls you can make.
Authentication
If you are interested in participating in the beta program, please contact our sales team (sales@creatordb.app) for discussion.
Key Terms
The following terms are listed to help you better understand frequently used terminologies while working with CreatorDB.
General terms
-
Brands: A company or organization that sponsors a creator.
-
Creator: An individual who creates and uploads content on social media platforms, such as YouTube, Instagram, or TikTok.
-
Developer: An individual who builds apps or utilities with data fetched from CreatorDB’s database.
-
App: A mobile or web application.
-
Data: Public information aggregated by CreatorDB from social media platforms.
API technical terms
-
API key: The unique credential required to connect to CreatorDB’s APIs. For example,
LE6DPZQkR3TQShxofXoD2j8qCBu1-f0jti665m1t50dwDD12W
-
Authentication: The process of verifying an entity is who they claim to be.
-
Authorization: The process of verifying an authenticated entity has permission to access data or perform requested tasks.
-
Dev server: The live production environment in CreatorDB, which should only be used to connect your app to our database. This environment connects to CreatorDB’s database and contains real data. If you use this environment to make changes or for tests, it might cause issues in data quality and result in additional costs.
CreatorDB does not provide a mock server or sandbox environment for testing our API. All API calls are made to the production environment and use API credits.
API versions
The CreatorDB API is currently on version 3.0.
To view the API documentation for version 2.0, see CreatorDB API 2.0 documentation.
API structure
The API Uniform Resource Locator (URL) is a unique address directed towards the API resource. The URL is required for making HTTP requests and interacting with the API to obtain or send data. The API URL components and descriptions are as follows:
| Components | Description |
|---|
| Protocol | Indicates the required protocol the browser must follow to obtain the URL resource. |
| Host | Also known as the domain name, directs to the server being requested. Instead of a domain name, this can also be an IP address. |
| Version | Indicates the current API version. |
| Resource | The path to the API resource on the server. |
| Parameter | The information the web server requires in an API request to access the resource. |
- Resources are nouns like
api/v3/usage or youtube/profile.
- Subresources are a classification or item of another resource.
- Actions are represented by HTTP request methods.
- Responses follow the generic JSON content type.
CreatorDB follows industry best practices OpenAPI Specification to describe each endpoint.
The root URL of the CreatorDB API is https://apiv3.creatordb.app/.
Methods and Parameters
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.
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 100 results are returned in an API request. The CreatorDB API can only get 100 results per API call. To get records from 101 and above, use the offset parameter in the request body to paginate your results.
For example, if you get 1,000 records in an API call, you must make 10 API calls to get all the data. After retrieving 100 results in the first API call, you must set the offset parameter to 101, 201, 301, 401, 501, 601, 701, 801, and 901 to get the remaining data. Otherwise, by default, you can only get the first 100 results in every call.
{
"maxResults": 100,
"sortBy": "subscribers",
"offset": 101,
"desc": true,
"filters": [
{
"filterKey": "subscribers",
"op": ">",
"value": 10000
}
]
}
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.
