Skip to main content
POST
Verify a signed caller-authentication audit event

Body

application/json

Request body for POST /audit/verify: the signed caller-authentication audit event and its stored signature, not a lookup by ID. Checked structurally on the server before signature verification runs. Verification operates on canonical bytes and the signature alone, never on event.type.

event
object
required

The caller-authentication audit event as stored. Only type, occurredAt, and route are structurally required; the event may carry further fields depending on what produced it.

signature
object
required

The signature stored alongside the event. Only production (Supabase) audit sinks sign; in-memory test sinks never produce a genuine one of these.

Response

Verification completed. A 200 does not by itself mean the signature verified, see the valid field.

Response shared by POST /refusal/verify and POST /audit/verify: a bare signature-validity result, no wrapper, no partial-failure detail. Both routes verify a signature over bytes with no database lookup, so there is nothing more specific to report than valid or not.

valid
boolean
required

Whether the signature verifies against Parmana's public key for the stated algorithm and key ID.