Get remediation agility for an organization
const url = 'https://api.adversarial.com/api/v1/risks/remediation?start_date=2026-01-01&end_date=2026-12-31';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.adversarial.com/api/v1/risks/remediation?start_date=2026-01-01&end_date=2026-12-31'Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”One side of a date range: an RFC 3339 timestamp in any UTC offset, used as given, or a bare YYYY-MM-DD naming a whole UTC day.
Inclusive start of the window. A bare YYYY-MM-DD starts it at
00:00:00Z of that day; an RFC 3339 timestamp in any UTC offset is used
as given. Defaults to 365 days before now.
Example
2026-01-01One side of a date range: an RFC 3339 timestamp in any UTC offset, used as given, or a bare YYYY-MM-DD naming a whole UTC day.
Inclusive end of the window. A bare YYYY-MM-DD ends it at
23:59:59.999999Z of that day, so the whole last day is plotted; an
RFC 3339 timestamp in any UTC offset is used as given. Defaults to now.
Example
2026-12-31Filter on what a risk is linked under, using the same vocabulary as
the register: null (top-level), any (linked children only), or a
parent id as RSK-<n> or a bare number. Repeat to union. Defaults to
null — parity with the register, so the chart plots bundle parents
only.
Responses
Section titled “Responses”Get remediation agility for an organization
The compact set of risk fields used to compute remediation agility.
object
Example
[ { "urgency": "Info" }]