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

# Pagination

> v2 list endpoints share one cursor-based pagination format and list object.

## Query parameters

<ParamField query="limit" type="number" default="20">
  Specifies the maximum number of items to return in a single response. The value must be between 1 and 100. If not specified, defaults to 20 items per page.
</ParamField>

<ParamField query="cursor" type="string">
  Specifies the starting point for the next page of results. The response will include items that come after (but not including) the object with this ID. To get the next page, use the ID of the last item from your previous request. The easiest way is to use the [list object's](#the-list-object) cursor field. If not provided, the API will return items from the beginning of the list.
</ParamField>

## The list object

Every list endpoint returns a standardized object:

<ResponseField name="results" type="array">
  The requested resource objects. Never more than `limit` items.
</ResponseField>

<ResponseField name="next" type="string | null">
  URL of the next page (carries the `cursor`), or `null` if there is no next page.
</ResponseField>

<ResponseField name="previous" type="string | null">
  URL of the previous page, or `null` on the first page.
</ResponseField>

```json theme={null}
{
  "results": [
    { "id": "cm9f6vwed0002iejc4vg2zu3t", "object": "content", "type": "flow", "..." : "..." },
    { "id": "cm9jaftye007yrjlx3ghggigi", "object": "content", "type": "checklist", "..." : "..." }
  ],
  "next": "/v2/projects/{projectId}/content?limit=2&cursor=cm9jaftye007yrjlx3ghggigi",
  "previous": null
}
```

To page, request the URL in `next` (or pass its `cursor` back as the `cursor`
query param).