Skip to main content
Sente writes an audit event whenever something sensitive happens to an account — a credential is read or overwritten, a browser session is opened or exported, a connection is revoked, a run is taken over. The trail is insert-only: there is no API to edit or delete an event, and events outlive the resources they describe. Events are org-scoped and never carry secret values — no passwords, no TOTP seeds, no session state. meta holds only descriptive fields (see the action table below).

The audit event object

Actions

These are the actions the API emits today.
Run outcomes (completed, failed, blocked) are not audit events — they live on the run itself and on the webhooks. The audit trail records deliberate acts on credentials, sessions, accounts, and takeover.

List audit events

GET /v1/audit-events
Response 200: an array of audit event objects, newest first.
An unknown action is not an error — it just matches nothing and returns []. There is no pagination cursor: page by narrowing since and raising limit. Another org’s events are never returned, and there is no endpoint to fetch a single event by id.