6. Certifications

POST /certifications with the range (dates or sequence numbers). Issuance is asynchronous: you get 202 with an id, and poll GET /certifications/{id} — or get notified via the certification.completed webhook. When completed you'll have:

• the signed PDF report, in two versions, Spanish and English, so it holds up before recipients in any jurisdiction without translation: a synthesis and attestation of the range's sequence integrity, with the configuration versions in force and the declarant designation 🔒. Both versions are signed separately, carry the same verification code and the same evidence, are equally authentic and each is verified on its own. reports lists both (language, URL and SHA-256); report_url is the one in the language of your Accept-Language;
• the evidence ZIP: data or digests, timestamps, sequences and chained digests;
• the verification code: anyone can check the report on the public verification page, without being a customer.

Registering and certifying are separate moments: evidence accumulates quietly and you may never need it — like insurance. Certify when you do.