Rag Status — GET /api/v1/test-management/rag/status
Rag Status
RAG feature status plus adoption counts for the caller’s projects.
Endpoint: GET /api/v1/test-management/rag/status
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 (uuid) or null | The project the page is about: enabled is then that project’s answer for the caller (project and role allow-lists applied). | |
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 | RagStatusResponse (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: RAG Generation
- Operation ID:
rag_status_api_v1_test_management_rag_status_get - Source code:
backend/app/routers/rag_generation.py, line 345 - Specification: OpenAPI JSON