Reject Case — POST /api/v1/test-management/batches/{batch_id}/cases/{case_id}/reject
Reject Case
Endpoint: POST /api/v1/test-management/batches/{batch_id}/cases/{case_id}/reject
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- A minimum role applies. The source code names it.
- You must have access to this generation batch.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
batch_id | path | yes | string (uuid) | ||
case_id | path | yes | string (uuid) | ||
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”| Content type | Body | Required |
|---|---|---|
application/json | RejectCaseRequest | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
204 | Successful Response | No body |
422 | Validation Error | HTTPValidationError (application/json) |
204 returns no body.
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:
reject_case_api_v1_test_management_batches__batch_id__cases__case_id__reject_post - Source code:
backend/app/routers/rag_generation.py, line 256 - Specification: OpenAPI JSON