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

# 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": ""
}

Last updated

Was this helpful?