List Project Compliance Packs — GET /api/v1/compliance-packs
List Project Compliance Packs
The newest packs in one project, or across every project the caller can see, and how many there are (total is counted, not len(items)).
Endpoint: GET /api/v1/compliance-packs
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 |
|---|---|---|---|---|---|
project_id | query | no | string or null | ||
limit | query | no | integer | 10 | |
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 | CompliancePackListRead (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_project_compliance_packs_api_v1_compliance_packs_get - Source code:
backend/app/routers/compliance_packs.py, line 178 - Specification: OpenAPI JSON