Skip to main content

Pagination

List endpoints use offset-based pagination with two query parameters: Every list response includes a meta object with the total count so you can page through results:
To fetch the next page, increase offset by your limit (for example, ?limit=100&offset=100).

Filtering

Some list endpoints accept filters. For example, GET /payments supports recipientId, batchId, and referenceId.

Status codes

The API uses standard HTTP status codes:

Errors

Non-success responses return a consistent error envelope:
Validation errors (400) include a human-readable message that names the offending field, making it easy to surface back to your users.