List audit events.
curl --request GET \ --url 'https://stratum.example.com/v1/audit?outcome=success&order=asc' \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Exact match on the audit event name (dotted form, e.g. iam.access.denied). page one event class exactly instead of over-fetching by outcome and narrowing client-side.
Exact match on outcome.errorCode (e.g. INSUFFICIENT_PERMISSIONS) — slice denials/failures by reason.
Page order by event timestamp. asc (the default) is oldest-first and is what every existing caller and page token assumes.
desc exists because oldest-first is the wrong default for reading a log: on a cluster with any history the first page is the install bootstrap, and an operator handed an event id by /v1/audit/integrity/verify cannot reach that row without paging the whole log. A page token is only valid for the order it was issued under; reusing one across orders walks the wrong way.
Responses
Section titled “Responses”Audit events.
object
object
object
object
object
object
object
Example
{ "events": [ { "outcome": { "status": "success" } } ]}