/api/v1/underwriting/statuses

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

Get Underwriting Statuses

Returns a list of underwriting status records for all merchants the authenticated user has access to. Each record includes the merchant's current application status, their underwriting pipeline status, the last update timestamp, any comments, and the name of the assigned underwriter. This endpoint provides a high-level overview of the entire underwriting portfolio.

Endpoint

GET /api/v1/underwriting/statuses

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 to build a dashboard view of all merchants in your UW pipeline, or to poll for status changes across all accounts at once. It is particularly useful for ISO operations teams who need to monitor which merchants require attention (e.g., those in PendingReview, RequestChanges, or Pending underwriting status). For a single merchant's full history, use GET /api/v1/underwriting/status-history instead.

Response

200 OK

Returns an array of UnderwritingStatusModel objects.

FieldTypeDescription
merchantProfileIdintegerInternal merchant profile ID
merchantIdstringExternal merchant identifier (e.g., MID from the processor)
statusstring (enum)Overall merchant application status (see allowed values below)
underwritingStatusstring (enum)UW pipeline status: Initialized, Pending, PendingReview, Completed
lastUpdatestring (date-time)ISO 8601 timestamp of the most recent status change
commentstringNotes left during the last status update
underwriterstringName of the underwriter currently assigned to the merchant

Allowed status values: NotSubmitted, Approved, PreApproved, Declined, Deactivated, WithDrawn, Closed, Pending, PendingPreUw, InCredit, ConditionallyApproved, RequestChanges, PreUnderwriting, Prospect, Draft, Received, UnderReview, PendingReview, PendingReviewPreUw, Cancelled, T2UnderReview, T2Approved, T2Declined, T2Any, T2Closed, T2Cancelled, Underwriting, MPAInProcess, MPACancelled, MPADeclined, MPADeleted, MPAError, MPABoarded, CRPOSEquipment, New, ElavonSigned, ElavonSubmitted, ElavonProcessorReceived

[
  {
    "merchantProfileId": 48201,
    "merchantId": "MID-887241",
    "status": "UnderReview",
    "underwritingStatus": "Pending",
    "lastUpdate": "2026-05-20T09:00:00Z",
    "comment": "Awaiting driver's license and bank statements.",
    "underwriter": "Sarah Thompson"
  },
  {
    "merchantProfileId": 48309,
    "merchantId": "MID-901155",
    "status": "Approved",
    "underwritingStatus": "Completed",
    "lastUpdate": "2026-05-18T16:45:00Z",
    "comment": "All documents verified. Application approved.",
    "underwriter": "Marcus Reyes"
  }
]

Error Codes

CodeWhen it happens
401Invalid or missing Basic Auth credentials
403User does not have permission for this operation
500Internal server error

Common Mistakes

  • Polling this endpoint too frequently — for high-volume ISOs with many merchants, cache results and poll at a reasonable interval rather than on every page load.
  • Confusing status (the overall merchant application status) with underwritingStatus (the internal UW pipeline stage) — both fields exist on each record and serve different purposes.
  • Expecting only active merchants — this endpoint may return merchants in all states including Declined, Closed, and Cancelled.

Related Endpoints

  • GET /api/v1/underwriting/status-history — get the full status change history for a single merchant
  • POST /api/v1/underwriting/pending-review — move a merchant back into the review queue after corrections
  • GET /api/v1/merchant/underwriting/assignedTo — get contact details for the underwriter assigned to a specific merchant

Example

curl -X GET https://hq.staging.netevia.dev/api/v1/underwriting/statuses \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)"
Headers
string
enum
Defaults to application/json

Generated from available response 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