Change merchant application status from "UW Level 1: Pending" to "UW Level 1: Pending Review"

Time	Status	User Agent
Retrieving recent requests…

Time

Status

User Agent

Retrieving recent requests…

Initiate Underwriting Review

Transitions a merchant application from "UW Level 1: Pending" to "UW Level 1: Pending Review". This signals to the underwriting team that the ISO has acknowledged the pending state and the application is actively under review. An optional comment can be included to communicate context to the underwriter or to the internal workflow system.

Endpoint

POST /api/v1/merchant/underwritingReview

Authentication

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

Authorization: Basic {base64(username:password)}

When to use

Call this endpoint after the application has been set to "UW Level 1: Pending" and an underwriter is ready to begin formal review. This status transition locks in the review phase and signals downstream workflows. The typical flow is: submit application → underwritingPending → underwritingReview → underwriter decision (approve/decline/request more documents).

Request Body

Field	Type	Required	Description
id	integer (int32)	Yes	The merchant profile ID of the application to advance to review.
comment	string	No	Optional note visible to underwriters, explaining the review context.

{
  "id": 10482,
  "comment": "All documents verified. Proceeding to formal underwriting review."
}

Response

200 OK

Field	Type	Description
data	object	Contains the success flag.
data.success	boolean	`true` if the status was updated successfully.
status	string	HTTP status name (e.g., `"OK"`).
error	string	Error message if the update failed; otherwise null.
warning	string	Non-fatal warning, if any.
validationResults	array	Validation errors, if any.
requestId	integer	Internal request tracking ID.

{
  "data": {
    "success": true
  },
  "status": "OK",
  "error": null,
  "warning": null,
  "validationResults": [],
  "requestId": 84930
}

Error Codes

Code	When it happens
400	The `id` field is missing, or the application is not in "UW Level 1: Pending" status and cannot be transitioned.
401	Invalid or missing Basic Auth credentials.
403	User does not have permission to advance this merchant application to review.
404	No merchant application found with the given ID.
500	Internal server error.

Common Mistakes

Calling this endpoint when the application is not in "UW Level 1: Pending" status — the transition will be rejected with a 400 error.
Calling underwritingReview before calling underwritingPending — these must be called in sequence.
Expecting this endpoint to trigger document validation — it only updates the status; document completeness must be verified beforehand.

Related Endpoints

POST /api/v1/merchant/underwritingPending — Set the application to "Pending" before calling this endpoint.
GET /api/v1/merchant/underwritingNotes — Check for open notes that need to be addressed before advancing.
GET /api/v1/merchant/status — Verify the current application status.

Example

curl -X POST https://hq.staging.netevia.dev/api/v1/merchant/underwritingReview \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 10482,
    "comment": "All documents verified. Proceeding to formal underwriting review."
  }'