# Pagination

Nullify’s API uses cursor-based pagination for endpoints that can return large result sets (findings, events, inventories). Each response includes a `nextToken` when more data is available.

## Parameters

* `limit` – Maximum number of items returned per request. Defaults to the service-specific page size.
* `nextToken` – Cursor from the previous response. Omit this parameter on the first request.

When `nextToken` is empty or absent from the response, you have reached the end of the collection.

## Example

```bash
# Request 1
curl -s \
  -H "Accept: application/json" \
  -H "Authorization: Bearer <TOKEN>" \
  'https://api.<TENANT>.nullify.ai/secrets/findings?githubOwnerId=1234&limit=1'

# Response 1 (trimmed)
{
  "findings": [
    {
      "id": "01J6EEXK3NKYKWW9XTPQYAF41N"
    }
  ],
  "numItems": 1,
  "nextToken": "eyJpZCI..."
}

# Request 2
curl -s \
  -H "Accept: application/json" \
  -H "Authorization: Bearer <TOKEN>" \
  'https://api.<TENANT>.nullify.ai/secrets/findings?githubOwnerId=1234&limit=1&nextToken=eyJpZCI...'

# Response 2 (trimmed)
{
  "findings": [
    {
      "id": "01J6EFVQN34BCEAHDJTE4F9Y22"
    }
  ],
  "numItems": 1,
  "nextToken": ""
}
```


---

# 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://docs.nullify.ai/api-reference/api-reference/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.