• 228 destinations
  • No KYC, ever
  • Bitcoin, Monero, USDT and 4 more

API and integration

Cursor pagination

Cursor pagination returns a list in pages using an opaque token pointing at the last item seen, so that new messages arriving while you page do not shift or duplicate results, unlike page numbers.

Offset pagination asks for "items 201 to 300". It is simple, and it breaks on lists that change while you read them: a message created between two requests shifts every later item by one, so a page boundary repeats one item or skips another. Deep offsets are also slow, because the database has to count past everything it skips.

A cursor names a position instead of an offset. The server encodes where the last page ended, typically the sort key and id of its last item, into an opaque token; the client sends the token back to get the next page, and the server continues from exactly that point. New items arriving at the head of a newest-first list do not disturb a walk already in progress; a later walk picks them up. Responses typically carry the items, a cursor for the next page and a flag saying whether more pages exist.

The trade-offs are deliberate: no jumping to page 40, often no total count, and pages fetched one after another rather than in parallel.

Example

A hypothetical reconciliation job reads the last hour's messages, newest first, a hundred at a time, while traffic keeps arriving. With offsets, every new message would push the pages along under it, and some messages would be counted twice. With a cursor, each request resumes after the last message seen, and every message is counted once.

Common mistakes

  • Parsing or constructing cursors; they are opaque by design and their format can change.
  • Changing filters mid-walk while reusing the old cursor.
  • Stopping at the first short or empty page instead of checking the flag.
  • Paging through lists to follow status changes that a webhook would push.

At SMSMeteor: GET /v1/messages lists and filters messages with cursor pagination: limit is 1 to 200, default 50, and cursor is the opaque cursor from the previous page's next_cursor. Each response carries data, next_cursor and has_more; keep paging while has_more is true. Message records are kept for 90 days, and campaign summaries indefinitely. For a one-off pull, the report export in CSV or JSON may be simpler, and webhooks push sent, delivered and failed events as they happen. Details are in the API reference.

Go further

See the term in practice.An email address opens the account, the rate card is public, payment is crypto, the test key is free.
Start sending