Generate a pentest attestation letter
GET/api/v1/reports/:report_id/attestation
Generate a dated pentest attestation letter for the report's assessment.
Produces a customer-facing compliance proof : scope tested, methodology, a per-severity finding summary, a no-critical-open statement, the org name for branding, a deterministic HMAC-backed verification id, and a public verification URL. Issuing it persists a verification record so the id resolves at the login-less verification endpoint.
- Scope required:
reports:read. - Response supports ETag revalidation (304 Not Modified).
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 429
- 500
Successful Response
Bad request — malformed input or failed validation.
Missing, expired, or invalid credentials.
Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.
Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).
Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).
Semantic validation failure — request shape was valid but contents were not.
Too many requests — rate limited. Retry after the window resets.
Internal server error — unexpected failure.