curl --request PATCH \
--url https://api.joinworth.com/case/api/v1/customers/{customerID}/cases/{caseID} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"status": "UNDER_MANUAL_REVIEW",
"assignee": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
}
'{
"status": "success",
"data": null,
"message": "Case status updated successfully"
}Cases
Update case status
Updates the status of a case (and optionally the assignee). Only certain status transitions are allowed depending on the case’s current status.
PATCH
/
customers
/
{customerID}
/
cases
/
{caseID}
curl --request PATCH \
--url https://api.joinworth.com/case/api/v1/customers/{customerID}/cases/{caseID} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"status": "UNDER_MANUAL_REVIEW",
"assignee": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
}
'{
"status": "success",
"data": null,
"message": "Case status updated successfully"
}Authorizations
Bearer token authentication (user context).
Path Parameters
ID of the customer that owns the case.
Example:
"550e8400-e29b-41d4-a716-446655440000"
ID of the case to update.
Example:
"6ba7b810-9dad-11d1-80b4-00c04fd430c8"
Body
application/json
New case status. Must be one of the allowed status values.
Available options:
CREATED, ONBOARDING, UNDER_MANUAL_REVIEW, MANUALLY_APPROVED, AUTO_APPROVED, SCORE_CALCULATED, MANUALLY_REJECTED, ARCHIVED, PENDING_DECISION, INFORMATION_REQUESTED, SUBMITTED, AUTO_REJECTED, RISK_ALERT, INVESTIGATING, DISMISSED, ESCALATED, PAUSED, INFORMATION_UPDATED User ID to assign as the case assignee (optional).
Was this page helpful?