Skip to main content
PATCH
/
api
/
cases
/
{id}
/
approval
Approve a case
curl --request PATCH \
  --url http://localhost/api/api/cases/{id}/approval \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "case_assignee": 123,
  "case_action": "<string>",
  "reason_for_escalation": {}
}
'

Documentation Index

Fetch the complete documentation index at: https://docs.cynopsis.co/llms.txt

Use this file to discover all available pages before exploring further.

Prior to reassigning a case from a maker to checker, the maker must perform the ‘case_action’. Depending on the type of case action, a reason for escalation must be stated in the request body. “case_action” types
  • Recommend Changes
  • Recommend True Hit (requires a reason_for_escalation field of value type string)
  • Recommend False Hit
  • Conclude False Hit
  • Conclude True Hit
Requirements
  • Requires View and Assess Case permission
  • The case_assignee_id must be different from the current_user_id.

Authorizations

​
Authorization
string
header
required

JWT token obtained from AWS Cognito or custom authentication service

Path Parameters

​
id
integer
required

A unique integer value identifying this case.

Body

​
case_assignee
integer
​
case_action
string
Minimum string length: 1
​
reason_for_escalation
object

Response

200

Case approved successfully.