Evidence

Record the digest of any regulated decision

The client hashes its own salted record and sends only the SHA-256; the record never reaches RiskRouter. The entry becomes a leaf of an RFC 6962 Merkle tree. A refused write answers 503 with recorded: false, never a success. Specification: https://riskrouter.eu/spec Optionally the client signs its own claim (signer_key_id, claimed_at, client_signature, all three or none): the signature is verified against a registered key before anything is written and then sits inside the leaf (leaf_version 3). See /spec#signed.

post/api/v2/evidence

Request

  • Base URL: https://api.riskrouter.eu
  • URL: https://api.riskrouter.eu/api/v2/evidence
  • Auth: one of:
    • HTTP bearer
    • API key in header X-RiskRouter-Key

Request body

record_digeststring required
kindstring required
signer_key_idstring

Optional, with claimed_at and client_signature: the id of a key registered with POST /api/v2/evidence/keys.

claimed_atstring

The client's own timestamp, exactly as signed.

client_signaturestring

ECDSA P-256 over SHA-256 of riskrouter-evidence-claim|v3|kind|record_digest|signer_key_id|claimed_at, IEEE P1363 r||s, base64.

chain_tagstring

Optional, with chain_seq: the completeness chain this record belongs to, 64 hex characters derived from a secret you keep. See /spec#chains.

chain_seqinteger

Optional, with chain_tag: this record's position in its chain, from 1. Out of turn answers 409 CHAIN_OUT_OF_TURN.

Response

Recorded.

okboolean
recordedtrue

Changes

No recorded changes to this operation across all 1 revision of this API.