Population change feed
GET /v1/cards/{gemrate_id}/population.
Cursoring
The feed is keyset-paginated by an opaque cursor. A typical loop:
- First call: pass
since(an ISO date) for an initial backfill. With neithersincenorcursor, the feed defaults to today (UTC) — you get only the current day’s changes, not a full-history scan. - Read every page until
has_moreisfalse, passing the returnednext_cursorback ascursoreach time. - Store the final
next_cursor. Next time you poll, start from it — you’ll only see ids that changed since.
Every response echoes since, the inclusive lower-bound date it covers (today, in UTC, when you passed neither since nor cursor), so a naive poll can see the baseline it defaulted to.
When you’re caught up, the call returns an empty gemrate_ids with the same position echoed back in next_cursor, so you can keep polling with the same token. cursor takes precedence over since if both are sent.
Authorizations
Query Parameters
ISO date (YYYY-MM-DD), inclusive — return cards changed on or after this day. Interpreted in UTC; must be on or before today (UTC) and within the last 30 days. Ignored when cursor is also sent.
"2026-06-01"
Opaque pagination token from a prior response's next_cursor. Wins over since. Omit both to default to today (UTC).
Page size, 1–10000.
1 <= x <= 10000