List My Assigned Failures — GET /api/v1/me/assigned-failures

List My Assigned Failures

Return the caller’s FAILED/BROKEN TestCase rows, newest first.

Endpoint: GET /api/v1/me/assigned-failures

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

Name	In	Required	Type	Default	Description
project_id	query	no	string or null		Project UUID or “all”
days	query	no	integer	30	Time window (created_at)
release_id	query	no	array of string or null		Only failures from runs in this release. Repeatable (OR, at most 20): a release UUID or ‘unattributed’.
suite_name	query	no	array of string or null		Only failures in these suites (effective suite, case-insensitive). Repeatable (OR, at most 50), 1-500 characters.
page	query	no	integer	1
size	query	no	integer	25
scope	query	no	string	mine	‘mine’ = caller’s assigned failures only; ‘team’ = all failures across project (QA_LEAD/ADMIN only)
X-API-Key	header	no	string or null		API key, as an alternative to the access token (see Authentication).

Request body

No request body.

Responses

Status	Meaning	Body
200	Successful Response	MyFailureListResponse (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

• Group: My Failures
• Operation ID: list_my_assigned_failures_api_v1_me_assigned_failures_get
• Source code: backend/app/routers/my_failures.py, line 130
• Specification: OpenAPI JSON