Skip to main content
Recomputes the organization’s hash chain and tells you whether any entry was altered, removed or inserted after the fact. Every entry is sealed with a hash that includes the previous entry’s hash, so changing history breaks the chain from that point on. See how it works.

Authentication

Accepts either:
  • An API key (X-API-Key: sk_...) with the read:audit-logs scope.
  • A Supabase Bearer session (Authorization: Bearer <token>) with the X-Organization-Id: <org-id> header — the user must be an owner or admin of that organization.

Rate limit

Verifying recomputes the whole chain, so this endpoint is limited to 10 requests per minute, on top of your plan’s limit. Beyond that it returns 429 Too Many Requests.

Example Request

Example Response

Common Errors

403 Forbidden

Not an owner or admin, or the API key lacks the read:audit-logs scope.