Kind Evidence — GET /api/v1/analytics/kind-evidence

Kind Evidence

Evidence-checklist record backing the AI-classified failure kind (AI-4) — for the kind-badge popovers. Two lookup modes:

Endpoint: GET /api/v1/analytics/kind-evidence

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
test_fingerprint	query	no	string or null
test_case_id	query	no	string or null
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	Not documented (application/json)
422	Validation Error	HTTPValidationError (application/json)

Response fields not documented. The API specification does not describe the body of every response this endpoint returns, so this page cannot list those fields. The body is not empty. To see it, call the endpoint on your own installation. All endpoints with undocumented responses.

Errors this endpoint returns, read from its source code:

• 403, with the message “You do not have access to this project”
• 422, with messages such as “Invalid test_case_id format”, “Provide test_case_id, or project_id + test_fingerprint”, “project_id is required”

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: Analytics
• Operation ID: kind_evidence_api_v1_analytics_kind_evidence_get
• Source code: backend/app/routers/analytics.py, line 479
• Specification: OpenAPI JSON