> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-api-and-mcp/api/pagination.md).

# Pagination

`GET /v1/company` is the one operation that returns more than one record, and so the one that paginates. It offers two ways through a result set, and a request uses one or the other — sending both `page` and `cursor` is **422 `validation_error`**.

* **Random access**: `page` (1-based) with `page_size` (up to 100) — a direct jump to a known page.
* **Walking every match**: leave `cursor` out of the first call, then repeat *the same search parameters* with `cursor=<the previous response's next_cursor>` until `next_cursor` comes back `null`. `page_size` may change between calls — a cursor is a position in the result set, not a page number, and a cursor page reports `page: null`.

The walk is the exhaustive form: a cursor resumes immediately after the last record it returned, so companies added to or removed from the datalake mid-walk neither skip nor repeat a record, which offsets cannot promise. A cursor belongs to the query that issued it: replaying one against a different search is **422 `validation_error`**, and the first page is the way back. Cursors are opaque — a cursor is meaningful only to the API that issued it, and one that has been parsed, edited or constructed is not a valid cursor.

`has_more` and `next_cursor` are authoritative; `total` is best-effort (a floor when `total_is_lower_bound` is true), so stop on `next_cursor`, never on a count. Every page is one call and is billed as one.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.delpha.io/delpha-api-and-mcp/api/pagination.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.