Findings APIs
Use the Findings API to query your findings inventory in real time. These synchronous REST endpoints let you list findings, get total counts, group findings by any supported field, and retrieve all findings detected on a specific asset, without waiting for an asynchronous report to complete.
All Findings API endpoints are read-only. Your account identity is derived automatically from your JWT token, so you do not need to pass a customer ID in any request.
Available Findings APIs
|
API Name |
Endpoint |
Description |
|---|---|---|
| List Findings API | POST/etm/api/rest/v1/findings/list | Use this API to get a paginated list of findings. |
| Get Findings by Asset API | POST/etm/api/rest/v1/findings/asset/{assetId} | Use this API to get findings associated with a specific asset. |
| Count Findings API | POST/etm/api/rest/v1/findings/count | Use this API to get the count of findings based on the specified query parameters. |
| Group Findings API | POST/etm/api/rest/v1/findings/group | Use this API to group findings by one or more fields and return the count for each group. |
| Get Findings by ID API | GET/etm/api/rest/v1/findings/{findingId} | Use this API to get finding details for a specific finding ID. |
Authentication
All Findings API endpoints require a valid Bearer JWT token in the request header:
Authorization: Bearer <your-jwt-token>Rate Limits
Assets API endpoints share the combined Inventory API rate limit of 300 requests per minute per customer. List operations return a maximum of 1,000 records per page; use pagination tokens to retrieve additional pages. Group operations return up to 1,000 buckets, sorted by count in descending order.
Count and group operations reflect full, accurate totals and are not subject to the 1,000-record page limit.
Requests that exceed the rate limit receive an HTTP 429 response; retry after the period indicated in the Retry-After response header.