---
title: "Pagination"
description: "See how Inttegro paginates large datasets using the /page endpoints, page numbers, and configurable page sizes."
canonical: "https://studio.inttegro.com/api/pagination"
format: inttegro-machine-docs/v1
language: "cURL"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/curl/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 503
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "machine-only-decisions"
recommended_mcp_tools: ["list_orders"]
estimated_tokens: 1373
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** See how Inttegro paginates large datasets using the /page endpoints, page numbers, and configurable page sizes. This cURL representation preserves HTTP paths and JSON wire names.

### Five questions

#### Q1. Is Pagination the right source for this task?

Use this reference for see how inttegro paginates large datasets using the /page endpoints, page numbers, and configurable page sizes. Keep the four decision rules below with its exact operations and fields; do not infer a broader workflow from endpoint order.

#### Q2. What is the first decision rule for traverse page endpoints deterministically?

Begin at page 1 and keep the requested page size stable for the traversal.
Increment the page number until the returned resource collection contains
fewer items than requested.

#### Q3. What is the second decision rule for traverse page endpoints deterministically?

Read the endpoint-specific response envelope: the collection property differs
by resource even when the request uses the same pagination concepts.

#### Q4. What is the third decision rule for traverse page endpoints deterministically?

Persist or deduplicate by resource ID when reconciliation spans multiple
runs. Page 1 is newest-first, so newly created records can change which items
appear in later numbered pages during a long traversal.

#### Q5. What is the fourth decision rule for traverse page endpoints deterministically?

Use lookup for one known resource ID. Use page endpoints for discovery,
reconciliation, exports, and back-office review rather than repeatedly
scanning pages to answer a single-object question.

### Recommended MCP assistance

Use these through an authenticated Inttegro MCP connection. This document remains the contract source.

- [`list_orders`](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#list_orders) — read; no mutation confirmation. Lists a bounded page of recent orders with totals and status, excluding customer contact and address data.

## Document content

# Pagination

Inttegro exposes paginated list endpoints for every high-volume resource (orders, balance transactions, payouts, and more). Each resource ships a `/page` endpoint that accepts a `page_number` and `page_size`, then returns a `page` object containing the records for that slice and metadata you can use to request additional pages.

Pagination is 1-based—requesting `page_number: 1` gives you the newest data, and subsequent page numbers step backwards in time. You can request up to 256 items per page, though smaller window sizes (25–100) often make it easier to re-request failed pages and keep dashboards responsive. Every response echoes the parameters you sent so you always know which window you are looking at.

## Traverse page endpoints deterministically

The four decision rules are in the machine preamble above.

## Request parameters

- `page_number` — `integer`

  1-based index for the page you want. Always start with `1` and increment
  until the response contains fewer records than `page_size`, which indicates
  you've reached the end.

- `page_size` — `integer`

  Number of objects to include per page (1–256). The default is 25. Choose a
  value that balances payload size with the number of requests your
  integration can comfortably make.

## Example request

In this example we request the first page of recent orders. The response returns two orders along with `number` and `size` so we can continue paging through historic activity. Subsequent requests should increment the request's `page_number` by one until the response includes fewer objects than requested.

**Fetch orders page — POST /orders/page**

```bash
curl https://api.inttegro.com/orders/page \
  -H "Authorization: Bearer $INTTEGRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "page_number": 1,
    "page_size": 2
  }'
```

```json
{
  "page": {
    "number": 1,
    "size": 2,
    "orders": [
      {
        "id": "or_kAVwBsk6EhQVv2YBUhYAqMf0lktEoQ0S7ZR8y2xi",
        "status": "requires_payment",
        "initiated_at": "2025-04-09T00:11:47.74569+01:00",
        "customer": {
          "id": "cu_N4IX542ZKixJJhIbc4bQBntdPrRb0DQ7KqEYSyqc",
          "guest": false,
          "name": "Gloria Kesewaa"
        }
      },
      {
        "id": "or_48ZW7BGvYUBWc1i6WBkL2jr0iPQP5jUy76mmmHpt",
        "status": "completed",
        "initiated_at": "2025-09-14T16:24:41.137708909Z",
        "completed_at": "2025-09-14T16:29:45Z",
        "customer": {
          "id": "cu_ewoa27qe7aO4GZouasUSmVXILsmxjR0Hc6lCMBkn",
          "guest": false,
          "name": "Anita Segnom"
        }
      }
    ]
  }
}
```