https://api.auditrails.io, and every endpoint is versioned under /v1/. Request and response bodies use application/json.
DSAR (Data Subject Access Request) workflows are available exclusively through the AuditRails dashboard and are not exposed via the bearer-token API.
Base URL
Request & Response Conventions
Every request must include theContent-Type: application/json header alongside your Authorization header. Every response — including errors — contains an X-Request-Id header in req_<ULID> format. Hold on to this value when contacting support; it uniquely identifies the exact server-side transaction.
Error Format
When a request fails, AuditRails returns a structured error body so you always know what went wrong and where to learn more.Endpoint Catalog
The table below lists every available endpoint grouped by functional category. Click an endpoint name to jump to its dedicated reference page.Ingestion
Read & Query
Compliance
Quick-Start Example
The snippet below ingests your first event in a singlecurl command. Replace at_live_xxx with your production API key.
Authentication
Learn how API keys work, the difference between live and test keys, and how to handle auth errors.
Rate Limits
Understand per-IP, per-plan, and test-key rate limits, and how to handle 429 responses gracefully.
Error Codes
Browse the full list of machine-readable error codes returned by the API.
SDKs
Use an official AuditRails SDK to get automatic retries, typed responses, and more.