PayintoDocs

Pagination

Page through long lists.

Pagination differs by endpoint.

EndpointsPagination
GET /accounts/main/transactions, GET /accounts/{id}/transactionsOffset or cursor
GET /bulk-transfers, GET /scheduled-bulk-transfers, GET /scheduled-bulk-transfers/{id}/executionsPage numbers, 30 per page
All other listsNone. The full list is returned.

Account transactions

ParameterDefaultDescription
pagination_typeoffsetoffset or cursor
per_page100Up to 1000
page1Offset pagination only
cursorCursor pagination only
typecredit or debit
statuspending, successful, failed, or reversed
from_date, to_dateDates in YYYY-MM-DD format

Use a cursor for syncing long histories, because new transactions can shift the results between offset pages.

curl "https://api.payinto.co/api/v1/business/accounts/main/transactions?pagination_type=cursor&per_page=200" \
  --header "Authorization: Bearer $PAYINTO_SECRET_KEY"

The response adds a pagination object next to data:

{
  "status": "success",
  "message": "Main account transactions retrieved.",
  "timestamp": 1793404800000,
  "data": [],
  "pagination": {
    "type": "cursor",
    "meta": {
      "next_cursor": "eyJpZCI6IjAxOTY0MzE2In0",
      "prev_cursor": null,
      "next_page_url": "https://api.payinto.co/api/v1/business/accounts/main/transactions?cursor=eyJpZCI6IjAxOTY0MzE2In0",
      "prev_page_url": null
    }
  }
}

Stop when next_cursor is null. With offset pagination, stop when meta.has_more_pages is false.

Bulk transfers and schedules

These endpoints nest the page inside data, so the records are at data.data. Use data.next_page_url to fetch the next page, and stop when it is null.

On this page