Change UW task status to In Review

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Change UW Task Status to In Review

Updates the status of a specific underwriting task (UW ticket) to InReview, indicating that the ISO has completed the required actions for that task and the underwriting team should now examine it. This is a ticket-level status change, distinct from the merchant-level PendingReview transition. Both may need to be called as part of the same workflow.

Endpoint

POST /api/v1/uwTasks/setStatusInReview

Authentication

Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:

Authorization: Basic {base64(username:password)}

When to use

Use this endpoint immediately after uploading documents or adding comments to a UW task ticket, to signal to the underwriting team that the specific task is ready for their review. For example, after calling POST /api/v1/uwTasks/ticket/addAttachment to upload a driver's license to ticket 1073, call this endpoint to move that ticket from Open to InReview. The UW team uses the InReview status as their queue filter for tasks that need attention.

Request Body

FieldTypeRequiredDescription
idinteger (int32)YesMerchant profile ID that owns the UW task ticket
ticketIdinteger (int32)YesID of the UW task ticket to mark as In Review
{
  "id": 48201,
  "ticketId": 1073
}

Response

200 OK

FieldTypeDescription
statusstring (enum)HTTP status name, e.g., "OK"
errorstringError message if the operation failed
warningstringNon-fatal warning message
validationResultsarrayField-level validation errors, if any
requestIdintegerUnique identifier for this API request
{
  "status": "OK",
  "error": null,
  "warning": null,
  "validationResults": [],
  "requestId": 88831
}

Error Codes

CodeWhen it happens
400id or ticketId is missing, not a valid integer, or the ticket is already in a terminal state
401Invalid or missing Basic Auth credentials
403User does not have permission for this operation
404Merchant or ticket not found
500Internal server error

Common Mistakes

  • Calling this endpoint without first uploading the required documents — the UW team will open the ticket expecting to find new information and find nothing.
  • Forgetting to also call POST /api/v1/underwriting/pending-review at the merchant level if all UW tasks have been addressed — the two status updates operate at different levels (task vs. merchant).
  • Using the wrong ticketId; retrieve valid IDs first from GET /api/v1/uwTasks/getByMerchantId.

Related Endpoints

  • POST /api/v1/uwTasks/ticket/addAttachment — upload a document before calling this endpoint
  • GET /api/v1/uwTasks/getByMerchantId — list UW task tickets to get valid ticketId values
  • POST /api/v1/underwriting/pending-review — transition the merchant-level UW status to PendingReview

Example

curl -X POST https://hq.staging.netevia.dev/api/v1/uwTasks/setStatusInReview \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 48201,
    "ticketId": 1073
  }'
Body Params
int32
int32
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Response

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/json