Developer documentation · API v1
Detected tracking changes
Query your observed follower or following changes by date.
Read recent changes
GET /open-api/v1/accounts/alice/changesThe default is followers over the last seven calendar days in UTC. Query list=following for following changes. This operation reads your accessible tracking history and spends no collection credits.
Select a date range
GET /open-api/v1/accounts/alice/changes?list=followers&from=2026-10-01&to=2026-10-07&timezone=UTC&limit=50from and to must be supplied together as YYYY-MM-DD dates. Both days are included in the chosen IANA timezone. UTC is the default. The range can span at most 366 calendar days; that does not promise 366 days of available history.
Read summary and members
data includes accountId, username, list, from, to, timezone, summary and items. summary covers your readable query range; items is one page.
- added and removed count detected additions and removals.
- netDiscovered is detected additions minus detected removals.
- countNetChange is the difference in observed profile totals where enough observations exist.
- Unknown summary values are null, not zero.
Member changes have id, kind, detectedAt and account (id and username). Kinds are new_follower, lost_follower, new_follow and unfollow. detectedAt records when Instoryview detected a change, not the exact Instagram action time. netDiscovered and countNetChange can differ.
Keep paging consistent
Use limit (1–100, default 50) and the returned nextCursor. Keep the same account and filters. The server fixes your query's observation context while you paginate. If it expires, cursor_expired asks you to start a new stored read.
Respect coverage and warnings. A gap or no detected event cannot prove that no action occurred. First snapshots establish a baseline; they do not establish past follow history.