Skip to main content
List endpoints return a page of results plus the offset of the next page.

The envelope

array
required
The results for this page, newest first.
integer
required
Results per page. Fixed at 10 — it is not a request parameter.
integer
required
The offset this page was fetched at.
integer | null
The offset to request next. null means you have reached the end.

Paging through everything

Follow nextOffset until it is null. Do not compute offsets yourself.
Stop on nextOffset === null, not on an empty data array. Treat 0 as a valid offset — a falsy check on nextOffset will terminate on the first page.

Ordering and drift

Results come back newest first. New records are created at the front, so paging a busy account over a long period can shift items between pages.
A status filter narrows the set but does not freeze it: links complete or expire while you page, and results are ordered by creation date, not by when their status changed. If one-pass completeness matters, de-duplicate on id and re-run the pass rather than trusting a single walk.

Filtering

GET /v1/payment-link accepts a status filter of active, inactive or completed. Filtering server-side beats fetching everything and discarding most of it. Moove Payment Links →

Next

Moove Payment Links

The list endpoint.

Rate Limits

Page politely.

Errors

Handling failure mid-page.