Pagination

All list endpoints in the send0 API use cursor-based pagination. This provides stable, consistent results even when new data is being created between page requests.

Response shape

Every list endpoint returns the same pagination structure.

{
  "data": [
    { "id": "em_abc1", "subject": "Welcome", "status": "delivered" },
    { "id": "em_abc2", "subject": "Invoice #42", "status": "sent" }
  ],
  "has_more": true,
  "cursor": "cur_xxxx"
}

Parameters

Using the SDK

let cursor: string | undefined;

do {
  const { data, has_more, cursor: nextCursor } = await send0.emails.list({
    limit: 20,
    cursor,
  });

  for (const email of data) {
    console.log(email.id, email.subject);
  }

  cursor = has_more ? nextCursor ?? undefined : undefined;
} while (cursor);

Using curl

Fetch the first page:

curl https://api.send0.dev/v1/emails?limit=20 \
  -H "Authorization: Bearer sk_live_..."

Fetch the next page using the cursor from the previous response:

curl https://api.send0.dev/v1/emails?limit=20&cursor=cur_xxxx \
  -H "Authorization: Bearer sk_live_..."

Continue fetching pages until has_more is false.

Why cursor-based?

Cursor-based pagination is more reliable than offset-based pagination for APIs where data changes frequently.

• Stable results. New records created between page requests don't cause duplicates or skipped items.
• Consistent performance. Cursors are backed by indexed lookups, so page 1,000 is as fast as page 1.
• No count overhead. Offset pagination requires counting rows, which gets slower as data grows.

Note: send0 never supports offset-based pagination. All list endpoints use cursors exclusively.