List Compliance Signing Keys — GET /api/v1/compliance-packs/signing-keys
List Compliance Signing Keys
Every signing key’s PUBLIC half, newest first, retired ones included (they verify the packs they signed). Deployment-wide public data.
Endpoint: GET /api/v1/compliance-packs/signing-keys
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | CompliancePackSigningKeysResponse (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Compliance Pack
- Operation ID:
list_compliance_signing_keys_api_v1_compliance_packs_signing_keys_get - Source code:
backend/app/routers/compliance_packs.py, line 101 - Specification: OpenAPI JSON