Findings API — Recent Changes
Customer-relevant changes to Findings API endpoints and schemas from the past 6 months. Dates below are when each change was committed, not necessarily when it reached production — release to production may lag as it rolls through our int → uat → production pipeline.
| Date | Version | Type | Change |
|---|---|---|---|
| 2026-09-28 | 1.10.0 | Added | Added an optional include query parameter to GET /v2/findings. Setting include=response_actions embeds each finding's response actions directly in the list response, and extends the response_actions schema with additional fields (uuid, response_id, updated_by, updated_timestamp, error_details, action_taken). |
| 2026-09-15 | 1.9.0 | Added | Added an optional tenant_code query parameter to GET/POST /v2/findings and its sub-resource endpoints, letting an authorized partner organization act on behalf of a tenant it directly manages. Deprecated the existing, always-ignored customer_code query parameter in favor of tenant_code. |
| 2026-09-02 | 1.8.0 | Fixed | Corrected the published OAuth scope requirements for several endpoints, added the missing 503/504 error responses to GET /v2/findings, and fixed a typo in the support contact email address. |
| 2026-08-27 | 1.7.0 | Added | Added GET /v2/findings/{case_id}/comments and GET /v2/findings/{case_id}/emails to retrieve case comment and email history for escalated findings. |
| 2026-08-26 | 1.6.0 | Added | Added GET /v2/findings/{finding_id}/activity-logs, /related-alerts, and /events, and a fully typed finding-detail response for GET /v2/findings/{finding_id}, for parity with the finding detail page in the customer portal. |
| 2026-08-26 | 1.6.0 | Changed | GET /v2/findings and its sub-resource endpoints now consistently return lower_snake_case field names. |
| 2026-06-25 | 1.4.2 | Added | Added Suspicious to the finding category enum. |
| 2026-05-25 | 1.4.2 | Fixed | start_date/end_date query parameters now accept ISO 8601 date-time format in addition to plain dates. |