Verify a request signature (self-test)
Rebuilds the canonical string from what you send and verifies the detached JWS against the caller’s own public keys. Use it to get your signing implementation right before the first real transaction.
Always answers 200 (except on a malformed body), including when the
signature is invalid: a 401 here would be indistinguishable from “your
token expired” and would send you debugging the wrong thing. Creates
nothing and moves nothing.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Headers
Optional client-generated idempotency token (recommended for safe retries).
Request
HTTP method of the hypothetical request. Defaults to POST.
Unix seconds, same value as X-Request-Timestamp.
Value of Idempotency-Key, or empty when the route has none.
Lowercase hex SHA-256 of the body. Omit and we compute it from body — that is the step most integrators get wrong.
Detached JWS <protected>..<signature>.
Response
Verification result (including failures).
Present only when valid is false. One of request_signature_invalid, request_timestamp_skew, unknown_kid, body_hash_mismatch, signature_missing, no_credential, no_public_key.
Keys currently usable by this credential (past their grace period).
Present when the signed-host edge would have refused this same call and let it through only because it is the self-test. One of request_timestamp_skew, request_signature_invalid, unknown_kid, request_signature_required, credential_not_yet_active. Absent when the edge accepted the signature.
Present while the credential is still in its activation grace. Until this instant every other route refuses it with credential_not_yet_active.