Pagination

List endpoints use cursor-based pagination via limit + next_cursor query parameters.

Request

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

Response

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

next_cursor is opaque — do not parse it. Pass it back verbatim to fetch the next page:

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

When next_cursor is absent or empty, you've reached the end.

Endpoints that paginate

• GET /identities
• GET /configuration-sets
• GET /templates
• GET /suppression
• GET /events
• GET /production-access

Endpoints that don't

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

Default ordering

Most list endpoints return newest-first. For deterministic ordering across pages, results are stable — re-fetching with the same cursor returns the same rows.