Filters and pagination

Filter identity

The list, summary and changes resources accept bounded risk, evidence, business segment and geography filters. Snapshot resources also accept inclusive UTC from and to timestamps.

Treat the complete non-date filter set as part of the local sync identity. Cursors are opaque. Keep that set unchanged when moving from a full snapshot to incremental changes because each cursor is bound to the resource, filter set, API version and public generation. A checkpoint created for one risk type or geography cannot continue another.

Date filters are intentionally rejected on /changes. When a user changes the filter set or date window, start a new full snapshot because membership is defined by each current public record's last_seen value.

Use taxonomy values returned by the API rather than hard-coding display labels. The taxonomy carries the current schema version and minimum partner group size.

Pagination rules

• Choose a page size within the documented bound.
• Follow next_cursor exactly; do not parse or modify it.
• Across the snapshot, keep that page size and filter set unchanged.
• Wait for the last page to report complete before committing its terminal checkpoint.
• A cursor, filter or generation conflict requires a restart.

Cursor opacity lets the server change its internal ordering without exposing database keys or event times.