> For the complete documentation index, see [llms.txt](https://docs.themochi.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.themochi.app/troubleshooting-and-safety/pagination.md).

# Load every page

Some lists are too large to return at once. Mochi returns one **page** of results and a **cursor** for the next page. A cursor is an opaque continuation value: use it exactly as returned and do not try to read meaning from it.

## Follow the pages

1. Make the first request without a cursor.
2. Process the returned `data`.
3. If `next_cursor` contains a value, send that exact value as the next request's `cursor`.
4. Stop when `next_cursor` is `null`.

## Parameters

| Parameter   | Description                                                                            |
| ----------- | -------------------------------------------------------------------------------------- |
| `page_size` | Number of records requested. Default: `50`; maximum: `100`.                            |
| `cursor`    | Continuation value returned in the previous response. Leave it out for the first page. |

Example first page:

```http
GET /v1/leads/?page_size=50
```

Example response:

```json
{
  "data": [],
  "next_cursor": "opaque-value"
}
```

Request the next page by passing the value unchanged:

```http
GET /v1/leads/?page_size=50&cursor=opaque-value
```

Do not parse, modify, generate, or store business meaning in a cursor. Mochi may reject a changed or old cursor. Treat that as an error. Do not silently restart at page one, because that can duplicate a full export.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.themochi.app/troubleshooting-and-safety/pagination.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.