Response fields vary by endpoint, so fetch the live shape and read from it rather than
assuming field names. The API reference covers the
shared conventions, and you’ll need a key from the API keys
page.
Confirm your key
GET /v2/whoami verifies the key and returns the organization it belongs to. If this
fails, fix auth before going further — see API setup.Pull the top creators for a period
GET /v2/creators/top ranks your creators over a period of 7d, 30d, or 90d.
This is your candidate set for the leaderboard.Enrich each creator with analytics
For every creator in the candidate set, call
GET /v2/creators/{id}/analytics to get
its metrics. Read the fields you need from the live response — views, likes, comments,
shares, followers — and compute engagement rate as
(likes + comments + shares) / views when you want to rank by engagement.A creator added recently may have
last_scrape_time: null and little or no history
until its first refresh lands, so it can sort low through no fault of its own. See
Data freshness for the timing.Widen coverage beyond 25
GET /v2/creators/top is bounded at 25 results. To leaderboard your whole roster, page
through GET /v2/creators (cursor pagination, limit up to 200) to collect every creator
id, then run the same enrich-and-sort loop over the full list. Read
pagination.has_next and pass the previous pagination.next_cursor back as cursor until
has_next is false.
Pagination
The cursor contract for walking
/v2/creators past the first page.Python client
A typed client with a ready-made pagination helper.
Creators dashboard
The same rankings, rendered in the app.