Insights Remediations API Change Log

Updated

This article tracks updates to the Remediations API including new features, performance and scalability improvements, and changes that may affect your integrations or automations. The most recent updates are listed first.

Upcoming API Updates

Summary: Added last_run_at field to remediation list response for improved visibility into execution history.

EndpointChange DescriptionImpact
GET /remediationsResponse now includes last_run_at field (timestamp of most recent playbook run for the remediation). Returns null if no runs exist.Minor

Release Date: February 4, 2026

Summary: This release introduces more granular issue reporting and improves error handling consistency for playbook generation.

EndpointChange DescriptionImpact
GET /remediations/:id?format=summaryResponse now includes issue_count_details field (counts by type).Minor
GET /remediations/:id/playbookNow returns 204 No Content (was 404) when a plan has no systems.Major
GET /remediations/:id/playbook
GET /remediations/download
POST /playbook		Now returns 400 UNKNOWN_ISSUE if an issue cannot be retrieved. Partial playbooks are no longer generated.Major
POST /playbookRequest now accepts optional precedence field to control execution order.Minor
GET /remediations/:id/issues
GET /remediations/:id/systems
GET /remediations/:id/systems/:system/issues		Pagination limit increased from 50 to 100.Patch

Release Date: January 14, 2026

Summary: Implemented request payload limits to ensure service stability.

EndpointChange DescriptionImpact
POST /remediations
PATCH /remediations/:id		Request now limited to 50 issues and 50 unique systems.Major

Note: It is still possible to build arbitrarily large remediation plans, with hundreds of systems and issues. These limits apply only on a per-request basis.

Release Date: January 4, 2026

Summary: Added issue precedence field for controlling play execution order and improved error handling for absent systems.

EndpointChange DescriptionImpact
POST /remediations
PATCH /remediations/:id
GET /remediations/:id		Request now accepts precedence field on issues. Response includes precedence in GET. Controls play execution order in generated playbooks (lower numbers execute first).Minor
GET /remediations/:id/systems/:system/issuesNow returns 404 Not Found when the specified system does not exist in the plan.Major
SBR
Product(s)
Article Type