Read fields off the live responses rather than assuming names — created resources
return the
id you’ll need for the next step. You’ll need an API key first — see API
setup or create one on the API keys
page.Create the competitor group
POST /v2/creators makes the group you’ll attach competitors to. Send an
Idempotency-Key so a retry doesn’t create a duplicate group, and read the new
creator’s id from the response.Track each competitor account
POST /v2/accounts takes a platform (instagram or tiktok) and a username. Call
it once per competitor handle, each with its own Idempotency-Key keyed to the handle,
and read each new account id from the response.Link the accounts to the group
PUT /v2/creators/{id}/accounts/{account_id} attaches an account to the group. Call it
once per account id you collected.A freshly tracked account starts with
last_scrape_time: null and no metrics until
its first refresh lands — so the timeseries will be sparse right after you set up the
group, then fill in over the following scrape cycles. See Data
freshness for the timing before you read too much into an empty
chart.Data freshness
Why a new competitor’s metrics lag, and when they appear.
Concepts
How creators, accounts, and metrics relate.
Creators dashboard
Manage the same groups in the app.