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 recipes by. Defaults to severity. Ties break by title (case-insensitive, ascending), then by id (ascending), whatever the sortOrder.

Sort direction for sortBy. Defaults to desc.

Restricts the recipes returned. One string of key:value clauses: , separates alternative values for one key (OR) and | separates keys (AND). For example, severity:critical,high|provider:aws,gcp returns recipes whose severity is critical or high and whose provider is Amazon Web Services or Google Cloud Platform. Because , and | are separators, a value itself can't contain them. Only equality matching is supported. Omit filter to list every recipe that has results in your recently scanned accounts, including dismissed recipes.

Keys:

• provider: one or more of aws, azure, azure_ad, gcp, general, google_cloud_source, google_workspace, k8s, oci, vmware.
• severity: one or more of critical, high, medium, low.
• pillar: one or more of cost, operations, performance, security, compliance. Matches recipes tagged with that pillar; compliance matches recipes tagged with at least one compliance standard (such as SOC2 or HIPAA).
• has_active_results: exactly one of true or false.
• allocation: up to 10 distinct allocation IDs (duplicates are ignored); get allocation IDs from GET /analytics/v1/allocations. Matches recipes with results on resources in any of those allocations, as resolved by Cloud Analytics; counts, savings and rowCount then cover only those resources. 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 value outside the allowed list, a non-boolean has_active_results, more than one has_active_results 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