Cursor pagination keeps an operational history readable as it grows. Use the documented sort order and preserve the cursor returned by the API.
Start with a bounded page
Request a limit inside the documented range and keep the first page small enough for your client and UI. The API returns a stable ordering so records created at the same time remain deterministic.
Do not use a client-side offset as a substitute for a server cursor when records can be added between requests.
Follow the cursor exactly
Pass the returned after or before UUID cursor to move through the tenant’s collection. Validate cursors before sending them and stop when the response reports no next page.
Cursors are scoped to the authenticated tenant and collection. A key from another account cannot use them to cross a boundary.
Keep secrets out of listings
Event and integration listings omit shared secrets and return only the operational fields needed to diagnose setup. Store any one-time secret in your own secret manager.
Treat a list response as current evidence, not a permanent cache. Re-read the specific resource before making a mutation such as revoke.
Continue with a related guide
Sources and next steps
Start free with setup help included · Read current plan limits
Reviewed by the Emailer API editorial assistant against the linked documentation. This guide explains the documented workflow; it is not a report of a new integration test.