Skip to main content
The drifts endpoints let you trigger configuration drift detection scans, retrieve findings, and manage drift status through resolution. Drifts compare a resource’s current configuration against a captured baseline. Base path: /api/v1/drifts

POST /drifts/detect — trigger drift scan

Starts a drift detection scan across all connected providers. Returns immediately with a job ID you can use to track progress.

Response 202


GET /drifts — list drift findings

Returns a paginated list of drift findings.

Query parameters

provider_id
integer
Filter by provider ID.
resource_id
integer
Filter by resource ID.
severity
string
Filter by severity: critical, high, medium, or low.
type
string
Filter by drift type: configuration, security, or compliance.
status
string
Filter by status: detected, investigating, or resolved.
page
integer
default:"1"
Page number.
per_page
integer
default:"20"
Results per page. Maximum is 100.

Response


GET /drifts/ — get drift details

Returns the full drift record including the JSON diff between the baseline and the current configuration.

PATCH /drifts/ — update drift status

Updates the status of a drift finding. Valid transitions are detected → investigating → resolved.

Request body

status
string
required
New status: investigating or resolved.

POST /drifts//resolve — resolve a drift

Marks a drift as resolved. Optionally captures a new baseline from the current configuration.

Request body

capture_baseline
boolean
default:"false"
When true, captures the current configuration as a new baseline after resolving.

GET /drifts/summary — get drift summary

Returns aggregate drift counts by severity and status.

Response