Get scenario audit trail
GET/scenarios/:scenario_id/audit-trail
Chronological governance audit trail for one scenario, newest first,
read from FlowBeacon's tamper-evident audit_events governance chain.
Included event types: policy_evaluation, policy_assignment_change,
remediation_attempt, remediation_sync, blueprint_uploaded,
blueprint_updated.
Not included: regulation-change ratification events
(regwatch.ratify). They are recorded as global telemetry with no
organization or scenario linkage, so they cannot appear in a
per-automation trail. See
Read the audit trail for the full
pagination walkthrough, retention, and ordering semantics.
Pagination is keyset (cursor) based: pass the previous response's
next_cursor back as ?cursor=. A null next_cursor means the last
page. Offset paging is deliberately not offered — on an append-only
stream it skips and duplicates rows under concurrent writes.
Note: the X-FB-Signature canonical string covers the path only, no
query string, so paging does not change how you sign the request.
Request
Responses
- 200
- 401
- 404
- 422
- 429
One page of the scenario's audit trail, newest first.
Missing or invalid Authorization header or API key.
Scenario not imported into the calling organization. A scenario that
belongs to a different organization returns this same 404 — the
endpoint never confirms that an id exists elsewhere.
An unusable filter: unknown event_type, unparseable from/to,
a cursor we did not issue, or limit outside 1-200. The filter is
rejected rather than dropped, so a bad value can never silently
widen the result set behind a 200.
Rate limit exceeded. Honor Retry-After. Defaults: 60 RPM / 1000 RPH per key.
Response Headers
Seconds to wait before retrying.