Continuation token from the pageToken of the previous response. Omit it on the first request; a response without pageToken is the last page.

The token records the position, the sort and the allocation filter IDs. Changing sortBy, sortOrder or the allocation IDs while paginating returns 400 pagination_token_invalid. Keep the other filter keys and maxResults unchanged while paginating. Tokens expire 5 minutes after they are issued; an expired token returns 400 pagination_token_expired. In both cases, restart from the first page.

Field to sort results by. Defaults to detection_time. Ties break by id (ascending), whatever the sortOrder.

Sort direction for sortBy. Defaults to desc.

Restricts the results returned. One string of key:value clauses: , separates alternative values for one key (OR) and | separates keys (AND). For example, region:us-east-1,us-west-2|status:active returns active results in either region. Because , and | are separators, a value itself can't contain them. Matching is exact unless a key says otherwise. Omit filter to list the recipe's results from the most recent scan of each recently scanned account, in every status.

Keys:

• account_id: one or more cloud account IDs, matched exactly.
• region: one or more cloud regions, matched exactly.
• issued_resource_name: one or more names of the affected resource, matched exactly.
• related_resource_name: one or more names of resources related to the result (for example, an attached IAM policy). Each value is matched as a substring anywhere in the result's related-resource details, not only against names.
• status: exactly one of active (not resolved and not snoozed), snoozed, resolved or all. Omitting it is the same as all. Combine resolved with last_scan_only:false; with the default it usually returns nothing.
• last_scan_only: exactly one of true or false. Defaults to true, which returns only results reported by each recently scanned account's most recent scan. A resolved result keeps the ID of the last scan that reported it, so resolved results rarely appear by default. false returns results from every scan and account, including resolved ones.
• allocation: up to 10 distinct allocation IDs (duplicates are ignored); get allocation IDs from GET /analytics/v1/allocations. Matches results on resources in any of those allocations, as resolved by Cloud Analytics; rowCount then counts only those results. You must be able to view every listed allocation. Service-account API keys can use public allocations only. If allocation access can't be checked, the request returns 503 with Retry-After and never falls back to unfiltered data.

Errors:

• An unknown key returns 400 filter_key_not_supported when it's the only problem, otherwise 400 validation_failed.
• A status outside the allowed list, a non-boolean last_scan_only, more than one status or last_scan_only value, more than 10 distinct allocation IDs, an invalid allocation ID (blank, longer than 256 characters, or containing /, whitespace or control characters), a malformed expression or an unsupported operator returns 400 validation_failed.
• An allocation that doesn't exist or that you can't view returns 404 composer-api.allocation_not_found.

Generated from available response content types