Pagination

List endpoints in the public API share one pagination shape. It’s designed to fit no-code tools like Make (limit + offset + has-more).

Query parameters

limit

integer

default:"50"

Page size. Range 1–100.

offset

integer

default:"0"

Number of records to skip.

The profiles and campaigns list endpoints also accept page (1-based) for convenience, but the response is always the limit/offset shape below.

Response shape

Paginated list responses (inside the data envelope) look like:

{
  "success": true,
  "data": {
    "items": [ ],
    "limit": 50,
    "offset": 0,
    "total": 128,
    "has_more": true,
    "next_cursor": "50"
  }
}

items

array

The page of records.

limit

integer

The page size that was applied.

offset

integer

The offset that was applied.

total

integer

Total matching records.

has_more

boolean

true when offset + items.length < total.

next_cursor

string | null

The next offset as a string (e.g. "50") when has_more, else null.

Paging through results

let offset = 0;
const limit = 100;
const all = [];

for (;;) {
  const res = await fetch(
    `https://api.senderz.app/api/v1/public/profiles?limit=${limit}&offset=${offset}`,
    { headers }
  );
  const { data } = await res.json();
  all.push(...data.items);
  if (!data.has_more) break;
  offset = Number(data.next_cursor);
}

next_cursor is a stringified numeric offset, not an opaque token. Feed it back as offset, not page.

Non-paginated lists

GET /public/webhooks returns a raw array of endpoints, not a paginated envelope — there are few enough of them that paging isn’t needed.

Errors & rate limits Event ingest

⌘I

Introduction

Ingest & transactional

Public API

Query parameters

Response shape

Paging through results

Non-paginated lists

​Query parameters

​Response shape

​Paging through results

​Non-paginated lists

Query parameters

Response shape

Paging through results

Non-paginated lists