# Pagination

Some methods return paginated results. The formatting of a paginated result is always:

```json
{
    "items": [
        ...
    ],
    "next": {
        "page": "..."
    },
    "previous": {
        "page": "..."
    }
}
```

The objects `previous` and `next` will be omitted if there are no previous or next items respectively.

The `next.page` and `previous.page` values can be added to the query parameters of the original query under the `page` key in order to get the next or previous page.

### Example

You make a GET request to a paginated endpoint `https://api.example.com/foo/bar`, and receive the following response:

```json
{
  "items": [],
  "next": {
    "page": "next-page-id"
  }
}
```

In order to get the next page of results, you would take the ID at position `.next.page` in the response body, and provide it as the value of the `page` key in a query to the same endpoint. The full URL including query parameters of your request to get the next page of the listing is:

```
https://api.example.com/foo/bar?page=next-page-id
```


---

# Agent Instructions: 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:

```
GET https://gitbook.com/docs/developers/gitbook-api/pagination.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.