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
There are no upcoming API updates at this time.
Release Date: June 23, 2026
Summary: GET /remediations and GET /remediations/{id} responses now include an expires_at timestamp indicating when a plan is treated as expired. The expires_at value is the period of time since the plan was last updated or executed, plus the retention period in effect for the organization (custom value or system default). GET /remediations supports sorting and filtering by this value as well.
| Endpoint | Change Description | Impact |
|---|---|---|
GET /remediations | Each list item now includes required expires_at (ISO 8601 date-time). Sort: expires_at, -expires_at. Filter: filter[expires_within]=N (integer, 1–366) returns plans that expire within the next N days, including plans that have already expired. Invalid values (e.g. 0, non-numeric, or > 366) return 400. | Minor |
GET /remediations/{id} | Response now includes required expires_at (ISO 8601 date-time), including ?format=summary. Same calculation as the list endpoint. | Minor |
Release Date: June 11, 2026
Summary: Added new endpoints to view and manage organization-wide configuration for remediation plan expiration settings. All authenticated users can read configuration values. Only organization admins can set or clear custom overrides via PUT /config/overrides. 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 effective value for each organization-wide configuration field for the caller's organization. Each field uses the custom override when one exists, otherwise the system default. All fields are always present. | Minor |
GET /config/defaults | Returns the system default value for each configuration field. All fields are always present. Does not reflect organization-specific overrides. | Minor |
GET /config/overrides | Returns only fields that have a custom override for the caller's organization. Fields using the system default are omitted. Returns {} when no overrides are set. | Minor |
PUT /config/overrides | Replaces organization-wide override values (organization admins only). Fields omitted from the request body or set to null are cleared (override removed; system default applies). To change one override while keeping another, include the current override value for the field that should stay customized. To clear all overrides, send {}. Response includes only fields with a non-null override (same shape as GET /config/overrides). Validates plan_warning_days < plan_retention_days using effective values (request value or system default when omitted/null). Valid range for each field: 1–366 days. | 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 |