# Pagination

Pagination splits results into pages. Results are in `data`; page details are
in `meta.paging`.

| Field     | Meaning                                                                                |
| --------- | -------------------------------------------------------------------------------------- |
| `offset`  | How many results to skip. `0` starts at the first result.                              |
| `start`   | Another name for the starting position, used by some endpoints. It also starts at `0`. |
| `hasMore` | `true` means more results are available. `false` means you can stop.                   |
| `cursor`  | A value you send to continue from the previous page. Copy it exactly.                  |

## Get the next page

Use the paging method listed in the endpoint's API reference:

| Method | First request       | Next request                                           |
| ------ | ------------------- | ------------------------------------------------------ |
| Offset | Send `offset=0`.    | Set `offset` to `meta.paging.nextOffset`.              |
| Start  | Send `start=0`.     | Set `start` to `meta.paging.nextStart`, when provided. |
| Cursor | Leave out `cursor`. | Set `cursor` to `meta.paging.nextCursor`.              |

Keep the same endpoint, profile or company, and filters. Continue while
`hasMore` is `true`, using the next value returned by the API. Stop when it is
`false`. A short or empty page can still have more results.

Some endpoints return `start` but use a cursor for the next page, such as
[Company Posts](https://docs.envoapi.com/api/operations/getcompanyposts.md). Follow the endpoint's API
reference for the fields it accepts.

The API sets the page size. Do not send `count`, `limit`, `maxPages`, or `fetchAll`.

[Documentation index](https://docs.envoapi.com/llms.txt) · [All endpoints](https://docs.envoapi.com/api/index.md)