Get a single alert or list of alerts with multiple events.
- Response is concatenated using AND condition (OR is not supported).
- Maximum result set size is 100.
- Offset is the zero-based number of alerts from the start of the result set.
Note: You can send a request to retrieve all or filtered results.
Required license: Cortex Xpanse Expander
authorization
String
required
api-key
api-key
{{api_key}}
x-xdr-auth-id
String
required
api-key-id
api-key-id
{{api_key_id}}
curl -X 'POST'
-H
'Accept: application/json'
-H
'Content-Type: application/json'
-H
'authorization: {{api_key}}'
-H
'x-xdr-auth-id: {{api_key_id}}'
'https://api-}/public_api/v2/alerts/get_alerts_multi_events/'
-d
'{
"request_data" : {
"search_from" : 0,
"next_page_token" : "next_page_token",
"filters" : [ {
"field" : "business_units_list",
"value" : "AlertFilter_value",
"operator" : "gte"
}, {
"field" : "business_units_list",
"value" : "AlertFilter_value",
"operator" : "gte"
} ],
"sort" : {
"field" : "creation_time",
"keyword" : "desc"
},
"search_to" : 0,
"use_page_token" : true
}
}'
import http.client
conn = http.client.HTTPSConnection("api-")
payload = "{\"request_data\":{\"filters\":[{\"field\":\"business_units_list\",\"operator\":\"gte\",\"value\":\"string\"}],\"search_from\":0,\"search_to\":100,\"sort\":{\"field\":\"creation_time\",\"keyword\":\"ASC\"},\"use_page_token\":true,\"next_page_token\":\"string\"}}"
headers = {
'authorization': "{{api_key}}",
'x-xdr-auth-id': "{{api_key_id}}",
'content-type': "application/json"
}
conn.request("POST", "%7B%7Bfqdn%7D%7D/public_api/v2/alerts/get_alerts_multi_events/", payload, headers)
res = conn.getresponse()
data = res.read()
print(data.decode("utf-8"))require 'uri'
require 'net/http'
require 'openssl'
url = URI("https://api-/%7B%7Bfqdn%7D%7D/public_api/v2/alerts/get_alerts_multi_events/")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
http.verify_mode = OpenSSL::SSL::VERIFY_NONE
request = Net::HTTP::Post.new(url)
request["authorization"] = '{{api_key}}'
request["x-xdr-auth-id"] = '{{api_key_id}}'
request["content-type"] = 'application/json'
request.body = "{\"request_data\":{\"filters\":[{\"field\":\"business_units_list\",\"operator\":\"gte\",\"value\":\"string\"}],\"search_from\":0,\"search_to\":100,\"sort\":{\"field\":\"creation_time\",\"keyword\":\"ASC\"},\"use_page_token\":true,\"next_page_token\":\"string\"}}"
response = http.request(request)
puts response.read_bodyconst data = JSON.stringify({
"request_data": {
"filters": [
{
"field": "business_units_list",
"operator": "gte",
"value": "string"
}
],
"search_from": 0,
"search_to": 100,
"sort": {
"field": "creation_time",
"keyword": "ASC"
},
"use_page_token": true,
"next_page_token": "string"
}
});
const xhr = new XMLHttpRequest();
xhr.withCredentials = true;
xhr.addEventListener("readystatechange", function () {
if (this.readyState === this.DONE) {
console.log(this.responseText);
}
});
xhr.open("POST", "https://api-/%7B%7Bfqdn%7D%7D/public_api/v2/alerts/get_alerts_multi_events/");
xhr.setRequestHeader("authorization", "{{api_key}}");
xhr.setRequestHeader("x-xdr-auth-id", "{{api_key_id}}");
xhr.setRequestHeader("content-type", "application/json");
xhr.send(data);HttpResponse<String> response = Unirest.post("https://api-/%7B%7Bfqdn%7D%7D/public_api/v2/alerts/get_alerts_multi_events/")
.header("authorization", "{{api_key}}")
.header("x-xdr-auth-id", "{{api_key_id}}")
.header("content-type", "application/json")
.body("{\"request_data\":{\"filters\":[{\"field\":\"business_units_list\",\"operator\":\"gte\",\"value\":\"string\"}],\"search_from\":0,\"search_to\":100,\"sort\":{\"field\":\"creation_time\",\"keyword\":\"ASC\"},\"use_page_token\":true,\"next_page_token\":\"string\"}}")
.asString();import Foundation
let headers = [
"authorization": "{{api_key}}",
"x-xdr-auth-id": "{{api_key_id}}",
"content-type": "application/json"
]
let parameters = ["request_data": [
"filters": [
[
"field": "business_units_list",
"operator": "gte",
"value": "string"
]
],
"search_from": 0,
"search_to": 100,
"sort": [
"field": "creation_time",
"keyword": "ASC"
],
"use_page_token": true,
"next_page_token": "string"
]] as [String : Any]
let postData = JSONSerialization.data(withJSONObject: parameters, options: [])
let request = NSMutableURLRequest(url: NSURL(string: "https://api-/%7B%7Bfqdn%7D%7D/public_api/v2/alerts/get_alerts_multi_events/")! as URL,
cachePolicy: .useProtocolCachePolicy,
timeoutInterval: 10.0)
request.httpMethod = "POST"
request.allHTTPHeaderFields = headers
request.httpBody = postData as Data
let session = URLSession.shared
let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
if (error != nil) {
print(error)
} else {
let httpResponse = response as? HTTPURLResponse
print(httpResponse)
}
})
dataTask.resume()<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api-/%7B%7Bfqdn%7D%7D/public_api/v2/alerts/get_alerts_multi_events/",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_POSTFIELDS => "{\"request_data\":{\"filters\":[{\"field\":\"business_units_list\",\"operator\":\"gte\",\"value\":\"string\"}],\"search_from\":0,\"search_to\":100,\"sort\":{\"field\":\"creation_time\",\"keyword\":\"ASC\"},\"use_page_token\":true,\"next_page_token\":\"string\"}}",
CURLOPT_HTTPHEADER => [
"authorization: {{api_key}}",
"content-type: application/json",
"x-xdr-auth-id: {{api_key_id}}"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}CURL *hnd = curl_easy_init();
curl_easy_setopt(hnd, CURLOPT_CUSTOMREQUEST, "POST");
curl_easy_setopt(hnd, CURLOPT_URL, "https://api-/%7B%7Bfqdn%7D%7D/public_api/v2/alerts/get_alerts_multi_events/");
struct curl_slist *headers = NULL;
headers = curl_slist_append(headers, "authorization: {{api_key}}");
headers = curl_slist_append(headers, "x-xdr-auth-id: {{api_key_id}}");
headers = curl_slist_append(headers, "content-type: application/json");
curl_easy_setopt(hnd, CURLOPT_HTTPHEADER, headers);
curl_easy_setopt(hnd, CURLOPT_POSTFIELDS, "{\"request_data\":{\"filters\":[{\"field\":\"business_units_list\",\"operator\":\"gte\",\"value\":\"string\"}],\"search_from\":0,\"search_to\":100,\"sort\":{\"field\":\"creation_time\",\"keyword\":\"ASC\"},\"use_page_token\":true,\"next_page_token\":\"string\"}}");
CURLcode ret = curl_easy_perform(hnd);var client = new RestClient("https://api-/%7B%7Bfqdn%7D%7D/public_api/v2/alerts/get_alerts_multi_events/");
var request = new RestRequest(Method.POST);
request.AddHeader("authorization", "{{api_key}}");
request.AddHeader("x-xdr-auth-id", "{{api_key_id}}");
request.AddHeader("content-type", "application/json");
request.AddParameter("application/json", "{\"request_data\":{\"filters\":[{\"field\":\"business_units_list\",\"operator\":\"gte\",\"value\":\"string\"}],\"search_from\":0,\"search_to\":100,\"sort\":{\"field\":\"creation_time\",\"keyword\":\"ASC\"},\"use_page_token\":true,\"next_page_token\":\"string\"}}", ParameterType.RequestBody);
IRestResponse response = client.Execute(request);request_dataobjectA dictionary containing the API request fields. An empty dictionary returns all results.
A dictionary containing the API request fields. An empty dictionary returns all results.
filtersarrayAn array of filter fields.
An array of filter fields.
fieldstring (Enum)Identifies the alert fields the filter is matching.
Identifies the alert fields the filter is matching.
operatorstring (Enum)String that identifies the comparison operator you want to use for this filter. Possible values:
- in— use with
alert_id_list, alert_source, asm_alert_categories, case_id_list, business_units_list, cloud_management_status, tags, xpanse_policy_id, severity, integration_source
- gte— Filters data from a specific timestamp onwards. Use with
creation_time, first_observed, last_observed.
- lte— Filters data up to a specific timestamp. Use with
creation_time, first_observed, last_observed.
- range— Filters data between two specific timestamps. Use with
first_observed, last_observed.
- relative_timestamp— Filters data relative to the current time (e.g., last 30 days). Use with
first_observed, last_observed.
String that identifies the comparison operator you want to use for this filter. Possible values:
- in— use with
alert_id_list,alert_source,asm_alert_categories,case_id_list,business_units_list,cloud_management_status,tags,xpanse_policy_id,severity,integration_source - gte— Filters data from a specific timestamp onwards. Use with
creation_time,first_observed,last_observed. - lte— Filters data up to a specific timestamp. Use with
creation_time,first_observed,last_observed. - range— Filters data between two specific timestamps. Use with
first_observed,last_observed. - relative_timestamp— Filters data relative to the current time (e.g., last 30 days). Use with
first_observed,last_observed.
valueobjectValue that this filter must match. The contents of this field will differ depending on the alert field that you specified for this filter:
- alert_id_list — List of integers. Each item in the list must be an alert ID.
- alert_source — List of strings.
- asm_alert_categories — List of strings. Example values: "Development Infrastructure", "Unpatched, Misconfigured, and end-of-life (EOL) systems".
- business_units_list — String or list of strings in the format "BU name" or "BU:BU name", for example “Acme & Co, Inc.” or “BU:Acme & Co, Inc.”
- case_id_list — List of integers. Each item in the list must be a case ID.
- cloud_management_status — String. Values are
Managed Cloud, Unmanaged Cloud, and Not Applicable.
- creation_time — Integer representing the number of seconds or milliseconds after the Unix epoch, UTC timezone. The value is returned in the response under the detection_timestamp field and represented in the console under the TIMESTAMP field.
- external_id_list— List of strings representing external IDs.
- first_observed — Values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format
"value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- integration_source — Valid values:
AWS, AZURE, GOOGLE, PRISMA_CLOUD
- last_observed — values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format, as follows
"value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- severity — Valid values:
low, medium, high, critical, informational
- status — Valid values:
new, reopened, resolved_no_risk, resolved_risk_accepted, resolved_no_longer_observed, resolved_contested_asset, resolved_remediated_automatically, resolved, under_investigation.
- tags — List of strings indicating the tags to filter on in the format
"tag-family:tag-name", for example "AR:registered to you".
- xpanse_policy_id — List of strings representing the xpanse policy IDs.
Value that this filter must match. The contents of this field will differ depending on the alert field that you specified for this filter:
- alert_id_list — List of integers. Each item in the list must be an alert ID.
- alert_source — List of strings.
- asm_alert_categories — List of strings. Example values: "Development Infrastructure", "Unpatched, Misconfigured, and end-of-life (EOL) systems".
- business_units_list — String or list of strings in the format "BU name" or "BU:BU name", for example “Acme & Co, Inc.” or “BU:Acme & Co, Inc.”
- case_id_list — List of integers. Each item in the list must be a case ID.
- cloud_management_status — String. Values are
Managed Cloud,Unmanaged Cloud, andNot Applicable. - creation_time — Integer representing the number of seconds or milliseconds after the Unix epoch, UTC timezone. The value is returned in the response under the detection_timestamp field and represented in the console under the TIMESTAMP field.
- external_id_list— List of strings representing external IDs.
- first_observed — Values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format "value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- integration_source — Valid values:
AWS,AZURE,GOOGLE,PRISMA_CLOUD - last_observed — values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format, as follows "value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- severity — Valid values:
low,medium,high,critical,informational - status — Valid values:
new,reopened,resolved_no_risk,resolved_risk_accepted,resolved_no_longer_observed,resolved_contested_asset,resolved_remediated_automatically,resolved,under_investigation. - tags — List of strings indicating the tags to filter on in the format
"tag-family:tag-name", for example"AR:registered to you". - xpanse_policy_id — List of strings representing the xpanse policy IDs.
stringValue that this filter must match. The contents of this field will differ depending on the alert field that you specified for this filter:
- alert_id_list — List of integers. Each item in the list must be an alert ID.
- alert_source — List of strings.
- asm_alert_categories — List of strings. Example values: "Development Infrastructure", "Unpatched, Misconfigured, and end-of-life (EOL) systems".
- business_units_list — String or list of strings in the format "BU name" or "BU:BU name", for example “Acme & Co, Inc.” or “BU:Acme & Co, Inc.”
- case_id_list — List of integers. Each item in the list must be a case ID.
- cloud_management_status — String. Values are
Managed Cloud, Unmanaged Cloud, and Not Applicable.
- creation_time — Integer representing the number of seconds or milliseconds after the Unix epoch, UTC timezone. The value is returned in the response under the detection_timestamp field and represented in the console under the TIMESTAMP field.
- external_id_list— List of strings representing external IDs.
- first_observed — Values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format
"value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- integration_source — Valid values:
AWS, AZURE, GOOGLE, PRISMA_CLOUD
- last_observed — values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format, as follows
"value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- severity — Valid values:
low, medium, high, critical, informational
- status — Valid values:
new, reopened, resolved_no_risk, resolved_risk_accepted, resolved_no_longer_observed, resolved_contested_asset, resolved_remediated_automatically, resolved, under_investigation.
- tags — List of strings indicating the tags to filter on in the format
"tag-family:tag-name", for example "AR:registered to you".
- xpanse_policy_id — List of strings representing the xpanse policy IDs.
Value that this filter must match. The contents of this field will differ depending on the alert field that you specified for this filter:
- alert_id_list — List of integers. Each item in the list must be an alert ID.
- alert_source — List of strings.
- asm_alert_categories — List of strings. Example values: "Development Infrastructure", "Unpatched, Misconfigured, and end-of-life (EOL) systems".
- business_units_list — String or list of strings in the format "BU name" or "BU:BU name", for example “Acme & Co, Inc.” or “BU:Acme & Co, Inc.”
- case_id_list — List of integers. Each item in the list must be a case ID.
- cloud_management_status — String. Values are
Managed Cloud,Unmanaged Cloud, andNot Applicable. - creation_time — Integer representing the number of seconds or milliseconds after the Unix epoch, UTC timezone. The value is returned in the response under the detection_timestamp field and represented in the console under the TIMESTAMP field.
- external_id_list— List of strings representing external IDs.
- first_observed — Values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format "value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- integration_source — Valid values:
AWS,AZURE,GOOGLE,PRISMA_CLOUD - last_observed — values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format, as follows "value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- severity — Valid values:
low,medium,high,critical,informational - status — Valid values:
new,reopened,resolved_no_risk,resolved_risk_accepted,resolved_no_longer_observed,resolved_contested_asset,resolved_remediated_automatically,resolved,under_investigation. - tags — List of strings indicating the tags to filter on in the format
"tag-family:tag-name", for example"AR:registered to you". - xpanse_policy_id — List of strings representing the xpanse policy IDs.
integerValue that this filter must match. The contents of this field will differ depending on the alert field that you specified for this filter:
- alert_id_list — List of integers. Each item in the list must be an alert ID.
- alert_source — List of strings.
- asm_alert_categories — List of strings. Example values: "Development Infrastructure", "Unpatched, Misconfigured, and end-of-life (EOL) systems".
- business_units_list — String or list of strings in the format "BU name" or "BU:BU name", for example “Acme & Co, Inc.” or “BU:Acme & Co, Inc.”
- case_id_list — List of integers. Each item in the list must be a case ID.
- cloud_management_status — String. Values are
Managed Cloud, Unmanaged Cloud, and Not Applicable.
- creation_time — Integer representing the number of seconds or milliseconds after the Unix epoch, UTC timezone. The value is returned in the response under the detection_timestamp field and represented in the console under the TIMESTAMP field.
- external_id_list— List of strings representing external IDs.
- first_observed — Values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format
"value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- integration_source — Valid values:
AWS, AZURE, GOOGLE, PRISMA_CLOUD
- last_observed — values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format, as follows
"value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- severity — Valid values:
low, medium, high, critical, informational
- status — Valid values:
new, reopened, resolved_no_risk, resolved_risk_accepted, resolved_no_longer_observed, resolved_contested_asset, resolved_remediated_automatically, resolved, under_investigation.
- tags — List of strings indicating the tags to filter on in the format
"tag-family:tag-name", for example "AR:registered to you".
- xpanse_policy_id — List of strings representing the xpanse policy IDs.
Value that this filter must match. The contents of this field will differ depending on the alert field that you specified for this filter:
- alert_id_list — List of integers. Each item in the list must be an alert ID.
- alert_source — List of strings.
- asm_alert_categories — List of strings. Example values: "Development Infrastructure", "Unpatched, Misconfigured, and end-of-life (EOL) systems".
- business_units_list — String or list of strings in the format "BU name" or "BU:BU name", for example “Acme & Co, Inc.” or “BU:Acme & Co, Inc.”
- case_id_list — List of integers. Each item in the list must be a case ID.
- cloud_management_status — String. Values are
Managed Cloud,Unmanaged Cloud, andNot Applicable. - creation_time — Integer representing the number of seconds or milliseconds after the Unix epoch, UTC timezone. The value is returned in the response under the detection_timestamp field and represented in the console under the TIMESTAMP field.
- external_id_list— List of strings representing external IDs.
- first_observed — Values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format "value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- integration_source — Valid values:
AWS,AZURE,GOOGLE,PRISMA_CLOUD - last_observed — values in milliseconds format
- with gte or lte operator, specify a specific date or time as a timestamp in milliseconds format
- with range operator, specify "to" and "from" values as timestamps in milliseconds format, as follows "value": { "from": "{{previous30Days}}","to": "{{previous7Days}}"
- with relative_timestamp operator, specify time interval to look back on (24H, 7D, 30D, etc.) as a value in milliseconds format
- severity — Valid values:
low,medium,high,critical,informational - status — Valid values:
new,reopened,resolved_no_risk,resolved_risk_accepted,resolved_no_longer_observed,resolved_contested_asset,resolved_remediated_automatically,resolved,under_investigation. - tags — List of strings indicating the tags to filter on in the format
"tag-family:tag-name", for example"AR:registered to you". - xpanse_policy_id — List of strings representing the xpanse policy IDs.
search_fromintegerAn integer representing the starting offset within the query result set from which you want alerts returned. Alerts are returned as a zero-based list. Any alert indexed less than this value is not returned in the final result set and defaults to zero.
An integer representing the starting offset within the query result set from which you want alerts returned. Alerts are returned as a zero-based list. Any alert indexed less than this value is not returned in the final result set and defaults to zero.
search_tointegerAn integer representing the end offset within the result set after which you do not want alerts returned. Alerts in the alerts list that are indexed higher than this value are not returned in the final results set. Defaults to 100, which returns all alerts to the end of the list. Use this field to specify the number of results on a page when using page token pagination.
Max value - 100
An integer representing the end offset within the result set after which you do not want alerts returned. Alerts in the alerts list that are indexed higher than this value are not returned in the final results set. Defaults to 100, which returns all alerts to the end of the list. Use this field to specify the number of results on a page when using page token pagination.
Max value - 100
100sortobjectIdentifies the sort order for the result set.
Identifies the sort order for the result set.
fieldstring (Enum)Can either be severity or creation_time.
Can either be severity or creation_time.
"creation_time"keywordstring (Enum)Can either be ASC (ascending order) or DESC (descending order). Case sensitive.
Can either be ASC (ascending order) or DESC (descending order). Case sensitive.
"desc"use_page_tokenbooleanUse "use_page_token":true in the initial request to paginate the response data.
Use "use_page_token":true in the initial request to paginate the response data.
next_page_tokenstringIf "use_page_token":true was included in the initial request, the response for that request will include a page token. Use "next_page_token":"string" to pass that page token into the next request to paginate the next set of data.
If "use_page_token":true was included in the initial request, the response for that request will include a page token. Use "next_page_token":"string" to pass that page token into the next request to paginate the next set of data.
{
"request_data": {
"filters": [
{
"field": "business_units_list",
"operator": "gte",
"value": "string"
}
],
"search_from": 0,
"search_to": 100,
"sort": {
"field": "creation_time",
"keyword": "desc"
},
"use_page_token": true,
"next_page_token": "string"
}
}{
"request_data": {
"filters": [
{
"field": "last_observed",
"value": {
"from": "{{previous30Days}}",
"to": "{{previous7Days}}"
},
"operator": "range"
}
]
}
}