Vulnerability Management: Pagination Enforced for List Scans on January 19, 2027

On January 19, 2027, Tenable will enforce pagination on the List scans endpoint. Currently, the endpoint returns every scan in your container in a single response. After this change, requests will return a maximum of 200 scans by default, and you can request up to 5,000 scans per response. This change helps maintain consistent API performance across deployments of all sizes.

🛑

Caution

Integrations that expect a complete list of scans in a single response must be updated to paginate through the results using the limit and offset query parameters before January 19, 2027. Requests that do not use pagination will still succeed but return only one page of results, potentially causing integrations to silently miss scans.

If your container holds 200 or fewer scans, you do not need to update your integration to retrieve the complete list immediately. However, implementing pagination ensures your integration continues to work correctly as the number of scans grows.

What is changing

After this change:

• Requests without a limit query parameter return a maximum of 200 scans by default.
• You can request up to 5,000 scans per response.
• The endpoint supports the limit and offset query parameters for pagination.
• The endpoint supports a sort query parameter to order results by name or last modification date.
• The response includes a pagination object describing the current page and the total number of scans matching your request criteria.

How to prepare

1. Update your requests to use the limit and offset query parameters rather than relying on a single response to contain every scan.
2. Read pagination.total from the response to determine the total number of matching scans, then request additional pages until you have retrieved all results.
3. Update any logic that counts scans or assumes the first response contains the complete result set to account for pagination.

For example, to retrieve the second page of 100 scans, sorted by most recently modified, use the following cURL request:

curl --request GET \
     --url 'https://cloud.tenable.com/scans?limit=100&offset=100&sort=last_modification_date:desc' \
     --header 'X-ApiKeys: accessKey=<YOURACCESSKEY>;secretKey=<YOURSECRETKEY>' \
     --header 'accept: application/json'

The response includes a pagination object alongside the scan and folder data:

{
  "scans": [ ... ],
  "folders": [ ... ],
  "pagination": {
    "total": 428,
    "limit": 100,
    "offset": 100,
    "sort": "last_modification_date:desc"
  },
  "timestamp": 1671477512
}

Query parameters

After this change, the List scans endpoint supports the following query parameters:

Response properties

The response includes a pagination object with the following properties:

Use pagination.total to determine how many matching scans exist and whether additional pages need to be retrieved.

Affected endpoint

This change affects the following endpoint:

📘

Note

You can review the updated parameters and response ahead of the change in the List scans reference on the Tenable Early Access portal. The reference on the Tenable Developer Portal will be updated when the change is released.