Read fields off the live delta response rather than assuming names. You’ll need an API
key first — see API setup or create one on the API keys
page — and see the API
reference for the shared conventions.
1
Set up a client with error parsing
Wrap requests so any non-2xx response surfaces the RFC 9457
code, detail, and the X-Request-ID — you’ll want both when a batch call fails.2
Page through your tracked videos
GET /v2/account-videos lists the videos discovered for your tracked accounts (use
GET /v2/videos if you track individual posts). Follow the cursor: read
pagination.has_next and pass the previous pagination.next_cursor back as cursor,
stopping when has_next is false. Collect each video id.3
Request engagement deltas in batches
POST /v2/videos/deltas takes up to 200 video_ids and optional windows —
look-back periods in days (1–365, default [1, 7, 14, 30]) to compute each delta over.
Send your ids in batches of 200, with a tight window like [7] for week-over-week
movement, and read the per-video deltas off the live response.4
Flag the breakouts
Sort the deltas by the change metric you care about — view growth for raw reach, or the
engagement change for quality — and flag the top movers. Read the delta fields from the
live response; here we sort on a
views change and treat the top slice as breakouts.Error handling
The RFC 9457 problem shape the client parses.
Rate limits
Back off on 429 when looping over large video libraries.
Python client
A fuller typed client to build these loops on.