| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Set Status to Underwriting Pending
Updates a merchant application's status to "UW Level 1: Pending", which places it in the queue for the initial underwriting review. An optional comment can be included to provide context for the underwriter. This is typically called by the ISO after resolving outstanding issues and re-submitting the application for review.
Endpoint
POST /api/v1/merchant/underwritingPending
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 to place a merchant application back into the "Pending" queue after documents have been uploaded or corrections have been made. This transitions the status so underwriters are alerted that the application is ready for their review. It is part of the underwriting status workflow: underwritingPending → underwritingReview → approval or decline.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| id | integer (int32) | Yes | The merchant profile ID of the application to update. |
| comment | string | No | Optional note to accompany the status change (visible to underwriters). |
{
"id": 10482,
"comment": "Voided check and bank statements uploaded. Application ready for 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": 73291
}Error Codes
| Code | When it happens |
|---|---|
| 400 | The id field is missing or the application is in a status that does not allow this transition. |
| 401 | Invalid or missing Basic Auth credentials. |
| 403 | User does not have permission to update the status of this merchant application. |
| 404 | No merchant application found with the given ID. |
| 500 | Internal server error. |
Common Mistakes
- Calling this endpoint when the application is already in "UW Level 1: Pending" or a later status may result in a 400 error.
- Not uploading all required documents before calling this endpoint — underwriters will still flag missing items and the application will cycle back.
- Omitting the comment when there are specific items to communicate to the underwriter; while optional, comments improve workflow clarity.
Related Endpoints
POST /api/v1/merchant/underwritingReview— Advance the application to "UW Level 1: Pending Review" once underwriting begins.GET /api/v1/merchant/underwritingNotes— Retrieve any outstanding underwriting notes before setting to pending.POST /api/v1/merchant/attachment— Upload supporting documents required by underwriters.
Example
curl -X POST https://hq.staging.netevia.dev/api/v1/merchant/underwritingPending \
-H "Authorization: Basic $(echo -n 'username:password' | base64)" \
-H "Content-Type: application/json" \
-d '{
"id": 10482,
"comment": "Voided check and bank statements uploaded. Application ready for review."
}'