Skip to content
Splashify Pro
Email docsEmail

Pagination

List endpoints use cursor-based pagination: limit sets the size of a page, and each page gives you a next_cursor for the next one. A list always comes one page at a time: leave limit out and you get the first 100 rows.

Request

bash
curl 'https://api.splashifypro.com/api/v1/partner/email/identities?limit=50' \
  -H "Authorization: Bearer $SPLASHIFY_API_KEY"

The parameter can also be sent under the name next_cursor. It means the same as cursor.

Response

json
{
  "success": true,
  "identities": [...],
  "count": 50,
  "next_cursor": "eyJpZCI6IjEyMzQ1IiwiX3QiOjE3..."
}

count is the number of rows on this page. next_cursor is opaque: do not parse it. Pass it back verbatim as cursor to fetch the next page:

bash
curl 'https://api.splashifypro.com/api/v1/partner/email/identities?limit=50&cursor=eyJ...' \
  -H "Authorization: Bearer $SPLASHIFY_API_KEY"

When next_cursor is absent or empty, you've reached the end. A page can hold fewer rows than limit, or none, while next_cursor is still there, so stop on a missing next_cursor and never on a short page.

Invalid cursors

A cursor works only for the account and the list that gave it. Anything else is a 400 INVALID_CURSOR with the message invalid cursor, and no rows:

  • a value that is not a cursor, or was changed
  • a cursor from another list, or from GET /configuration-sets with another customer_id
  • a cursor from GET /events with another day_bucket

GET /events reads one day. A cursor stays on the day its walk began, so you can leave day_bucket out of the next calls even if midnight passes.

Endpoints that paginate

  • GET /identities
  • GET /configuration-sets
  • GET /templates
  • GET /suppression
  • GET /events
  • GET /production-access
  • GET /audiences/:id/contacts, with rules of its own: it takes cursor, has no limit and always reads 50 contacts at a time. See List contacts.

Endpoints that don't

  • GET /quotas, /stats, /reputation — fixed-size responses
  • GET /emails/:message_id — single-row reads

Default ordering

GET /templates, /production-access and /events return newest first, /suppression in email address order and /identities by type, then value. Results are stable across pages: re-fetching with the same cursor returns the same rows, unless rows were added or removed in between.