API Cursor Pagination

The /events and /blog-posts REST endpoints now accept a cursor parameter in addition to the existing page / limit approach. Cursor pagination is more stable when records are being added or removed between requests, which is common in high-volume event calendars.

Using cursors

Each paginated response now includes a nextCursor field. Pass it as ?cursor=<value> to fetch the next page.

GET /api/v1/events?cursor=eyJpZCI6IjEyMzQ1In0=&limit=25

Backwards compatibility

The existing page / limit parameters continue to work without changes. There is no migration required. Cursor pagination is opt-in.

GraphQL

Cursor pagination is already available in the GraphQL API via the Connection pattern. This update brings the REST API to parity.