---
title: "Maximum page size for list endpoints in Receivables API"
canonical: https://documentation.maventa.com/changelogs/developer-changelog/2026-11-12-maximum-page-size-for-list-endpoints-in-receivables-api/
---

The list endpoints of the Reskontravahti API now return at most 1000 items per page:

- GET /v1/assignments
- GET /v1/assignments/{assignment_id}/events
- GET /v1/assignments/{assignment_id}/messages
- GET /v1/events
- GET /v1/message_threads
- GET /v1/message_threads/{thread_id}/messages

The default page size stays 10. A `per_page` above 1000 is not rejected but treated as 1000, and the `X-Per-Page` response header shows the page size that was actually used. To fetch all items, request `page=1`, `page=2`, and so on until `X-Page` is greater than or equal to `X-Total-Pages`.

A `per_page` or `page` below 1 is now treated as 1 instead of causing an error or an invalid response.

On `GET /v1/message_threads` with the `unseen` parameter, `X-Total` and `X-Total-Pages` now count only the threads that match the filter. Before, they counted all threads.

On all list endpoints, items with the same value in the sort field, for example the same `due_date` or `paid`, now always come in the same order. Before, their order could differ between page requests, so paging through a list could return an item twice and skip another.

Check out [Swagger API documentation](https://swagger.maventa.com/?urls.primaryName=STAGE+-+AutoInvoice+Receivables+API#/assignments) for details.