Creators vs Profiles
The API separates the person from their social accounts. Understanding this split helps you pick the right endpoint and avoid redundant lookups.- A creator is the person or brand.
- A profile is one social account on one platform.
Which Endpoint to Use
Typical Workflow
If you start from a known username:- Call
GET /v1/profiles/{platform}/{username}orPOST /v1/profiles/lookup. - Read the returned
creator_id. - Call
GET /v1/creators/{id}?include=profilesto see the creator and all their linked accounts together.
- Call
POST /v1/search. - Pick a creator from the response.
- Call
GET /v1/creators/{id}?include=profilesto get the full picture.
Why the Split Exists
Creators and profiles answer different questions.
Keeping them separate means you can look up a single social account without pulling in everything about the creator, and you can fetch a creator without needing to know which platform they’re on.
Common Patterns
Search and then expand
UsePOST /v1/search to find relevant creators, then open one by ID when you want more detail. This keeps the search response lightweight while still giving you a path to full creator data.
Verify a single account
UseGET /v1/profiles/{platform}/{username} when you already know the platform and username. This is the fastest way to check whether an account exists in the system and grab its creator_id.
Batch known accounts
UsePOST /v1/profiles/lookup when you have a list of accounts to resolve. This saves you from making individual profile requests and returns all the creator_id mappings in one call.