Pagination
List endpoints use cursor pagination: results come newest-first in pages, with an opaque cursor pointing at the next page.
curl \ -H "Authorization: Bearer YOUR_API_KEY" \ "https://api.reminix.com/v1/workspace/audit-events?limit=25"{ "items": [{ "id": "…", "action": "member.invited", "createdAt": "…" }], "nextCursor": "eyJ0IjoiMjAyNi0wOC0uLi4ifQ"}To fetch the next page, pass the cursor back unchanged:
curl \ -H "Authorization: Bearer YOUR_API_KEY" \ "https://api.reminix.com/v1/workspace/audit-events?limit=25&cursor=eyJ0IjoiMjAyNi0wOC0uLi4ifQ"Iterate until nextCursor is null — that is the last page.
Rules worth knowing:
limitaccepts 1–100 (default 25).- Cursors are opaque: never construct or modify one; a malformed
cursor returns
invalid_request. - Pages are stable under concurrent writes — new rows created while you paginate never cause skips or duplicates within your walk.
- Treat the response shape as additive: new fields may appear on items, existing ones will not be renamed.