Red Hat Lightspeed Remediations API Change Log
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 new endpoints to view, update, and reset organization-wide configuration for remediation plan expiration settings. Only org admins can set custom values or reset a field to the system default but all users can view the config values. The configurable fields are plan_retention_days (days of inactivity before a plan is treated as expired) and plan_warning_days (days before expiration when a warning is shown). More fields may be added later.
| Endpoint | Change Description | Impact |
|---|---|---|
GET /config | Returns the current and default configuration values for the caller's organization. Each field has an override value (custom setting) and a default value (system default). | Minor |
PATCH /config | Updates organization-wide configurable items for the caller's organization (restricted to organization admins only). Sets custom values that override the system defaults. | Minor |
DELETE /config/{field} | Resets an organization-wide config field to its default value. Restricted to organization admins only. After reset, the field's override will be null in the GET /config response, indicating the system default is in use. | Minor |
Release Date: March 25, 2026
Summary: Added last_run_at field to remediation list response for improved visibility into execution history.
| Endpoint | Change Description | Impact |
|---|---|---|
GET /remediations | Response 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.
| Endpoint | Change Description | Impact |
|---|---|---|
GET /remediations/:id?format=summary | Response now includes issue_count_details field (counts by type). | Minor |
GET /remediations/:id/playbook | Now returns 204 No Content (was 404) when a plan has no systems. | Major |
GET /remediations/:id/playbookGET /remediations/downloadPOST /playbook | Now returns 400 UNKNOWN_ISSUE if an issue cannot be retrieved. Partial playbooks are no longer generated. | Major |
POST /playbook | Request now accepts optional precedence field to control execution order. | Minor |
GET /remediations/:id/issuesGET /remediations/:id/systemsGET /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.
| Endpoint | Change Description | Impact |
|---|---|---|
POST /remediationsPATCH /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.
| Endpoint | Change Description | Impact |
|---|---|---|
POST /remediationsPATCH /remediations/:idGET /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/issues | Now returns 404 Not Found when the specified system does not exist in the plan. | Major |