> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ionage.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Pagination

> Paging through FLO Partner API collection endpoints

Collection endpoints accept `limit` and `offset` query parameters.

```
GET /public/fleets/v1/drivers?limit=50&offset=0
```

## Response shape

Paginated responses wrap results in `data` and paging state in `metadata`:

```json theme={null}
{
  "data": [],
  "metadata": {
    "total_count": 125,
    "next": "/public/fleets/v1/drivers?limit=50&offset=50",
    "prev": null
  }
}
```

| Field | Meaning |
| - | - |
| `total_count` | Total matching records across all pages |
| `next` | Path to the next page, or `null` on the last page |
| `prev` | Path to the previous page, or `null` on the first page |

`next` and `prev` are **paths, not absolute URLs** — join them to the API host before
requesting them.

> [!TIP]
>
> Follow `metadata.next` until it is `null` rather than computing offsets from
> `total_count`. A collection changing underneath you can otherwise cause a page to be
> skipped or repeated.

## Filtering

Most collection endpoints also accept filters, which combine with paging. `search` is
a case-insensitive match over customer-facing fields; other filters are exact. See the
individual endpoints under **FLO API** for the filters each one supports.

> [!NOTE]
>
> This envelope differs from the Nexus API, which returns a `links` object and an
> `X-Total-Count` header. Code written against one will not read the other.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.