Verify a pentest attestation by its verification id (no auth)

GET 
/api/v1/public/attestations/:verification_id

Resolve a keyed ATT-… verification id to its public letter.

Login-less: an auditor pastes the id printed on the PDF and gets back the issued attestation (scope, methodology, severity summary, statement). An unknown id 404s. The id is an HMAC-backed bearer credential stored with the issued letter, so historical letters resolve by their persisted id. No internal identifiers are exposed — the stored letter is already the public-safe subset.

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.