verify

Verify Savings Report

#1296 — is this stored savings report authentic and unaltered?

Public (a partner's finance team has no Badge account). The report id is an unguessable UUID. The stored payload is re-hashed and the signature re-checked on every call, and agent_id / generated_at are served from the SIGNED payload (and must match the row), so a row edited after signing answers valid=false. headline repeats the signed headline facts at PUBLIC precision, for a PUBLIC agent only, so the holder of a PDF/CSV can compare them with the file. Flag off or unknown id -> 404.

This proves the STORED report. To check a file you were handed, POST it to /verify/report.

get/api/v1/verify/report/{report_id}

Request

  • Base URL: https://api.badgeia.com
  • URL: https://api.badgeia.com/api/v1/verify/report/{report_id}
  • Auth: none declared

Path parameters

report_idstring uuid required

Response

Successful Response

validboolean nullable required
status'valid' | 'invalid' | 'unverifiable' required
agent_idstring uuid required
generated_atstring date-time required
payload_sha256string required
key_idstring required
reasonstring nullable
canonical_form'current' | 'legacy' nullable

Changes

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