The hash chain, what a certificate claims, and how verification actually works.
Certificates API
Fetch an issued certificate, and the public endpoints anyone can use to verify one independently. See the certificates guide for what a certificate actually claims and why the chain matters.
GET
/certificate/:userIdBearer tokenReturns the certificate already issued for a user's completed deletion. Re-fetched, not re-signed — repeated calls return byte-identical output.
| Name | In | Type | Required | Description |
|---|---|---|---|---|
userId | path | string | Yes | The user whose deletion certificate you're retrieving. |
GET
/public-keyNone — publicReturns the current signing key as a PEM-encoded public key.
GET
/.well-known/jwks.jsonNone — publicReturns the current set of verification keys in standard JWKS format — covers every currently-valid key version, keyed by kid.
GET
/certificate-chain/by-hash/:hashNone — publicReturns the certificate whose own hash matches :hash, for walking the chain backward toward the genesis certificate.
| Name | In | Type | Required | Description |
|---|---|---|---|---|
hash | path | string | Yes | The sha256 hash of the certificate to look up. |
- 404 if no certificate with that hash was ever issued.
Base URL, auth conventions, and the full endpoint index.