Scroll API Changes
Objective
This guide presents reference information on migration for API calls to query access logs that will require search_after parameter to be set to true.
Current Approach
Use ves.io.schema.log.CustomAPI.AccessLogQueryV2 API to download logs with scroll parameter set to true. See, API Reference.
The response contains a scroll ID.
Scroll ID is passed to the subsequent Access Log Scroll Query to return the next set of logs.
Changes
A stateless way to use the APIs with the search_after parameter. It improves the performance of the log queries.
search_after parameter for access log queries where you can pass a list of sort values.
Note: March 2026 changes initiated.
Enforcement Timeline
API calls to query access logs will require search_after parameter to be set to true.
Migrate to use search_after parameter for access logs.
Supported Until August 2026: scroll_id and search_after are supported for access log query.
Note: By August 2026, scroll_id parameter will be depreciated.
Search_after Operation
- In post method to query logs from Access Logs reference. See, Access Logs.
- Set “search_after”: true.
Note: Remove “scroll” parameter if you are using this in your API request.
"aggs": { },
"end_time": "string",
"limit": 0,
"namespace": "string",
"query": "string",
"search_after": true,
"sort": "DESCENDING",- Response returns maximum of 500 records with 2 additional fields last_doc_id and last_timestamp.
"aggs": { },
"last_sort_values": {
"last_doc_id": 17777788899,
"last_timestamp": 63506060602- Use above last_doc_id and last_timestamp in your next request to get additional set of records.
Note: last_doc_id parameter is a string.
{
"aggs": {},
"end_time": "string",
"limit": 0,
"namespace": "string",
"query": "string",
"search_after": true,
"sort": "DESCENDING",
- "sort_values": {
"last_doc_id": “17777788899”,
"last_timestamp": 63506060602
},
"start_time": "string"
}- Repeat last step until response returns “null” in “last_sort_values” parameter.