List Run Branches — GET /api/v1/runs/branches
List Run Branches
The project’s branches in the window, newest last run first, for the Runs toolbar.
Endpoint: GET /api/v1/runs/branches
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 | yes | string | The project whose branches to list. | |
days | query | no | integer or null | 30 | Look back window in days (0 = all time) |
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 | RunBranchListResponse (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: Test Runs
- Operation ID:
list_run_branches_api_v1_runs_branches_get - Source code:
backend/app/routers/runs.py, line 343 - Specification: OpenAPI JSON