Get merchant underwriting status history

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

Get Merchant Underwriting Status History

Returns the complete history of underwriting status changes for a specific merchant, ordered chronologically. Each entry in the history represents a single status transition, including the application status, the UW pipeline status, the timestamp, comments recorded at the time, and the underwriter responsible. This provides a full audit trail of the merchant's progress through the underwriting process.

Endpoint

GET /api/v1/underwriting/status-history

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 when you need a detailed timeline of a merchant's underwriting journey — for example, to understand why an application was declined, to confirm when a particular status change occurred for compliance purposes, or to troubleshoot a merchant application that has stalled. Unlike GET /api/v1/underwriting/statuses which returns only the current state, this endpoint returns every historical transition.

Query Parameters

ParameterTypeRequiredDescription
idinteger (int32)YesMerchant profile ID whose underwriting status history to retrieve

Response

200 OK

Returns an array of UnderwritingStatusModel objects in chronological order (earliest first).

FieldTypeDescription
merchantProfileIdintegerInternal merchant profile ID
merchantIdstringExternal merchant identifier (e.g., MID from the processor)
statusstring (enum)Application status at this point in time
underwritingStatusstring (enum)UW pipeline status: Initialized, Pending, PendingReview, Completed
lastUpdatestring (date-time)ISO 8601 timestamp when this status was recorded
commentstringNotes added at the time of the status change
underwriterstringName of the underwriter who made or triggered the status change
[
  {
    "merchantProfileId": 48201,
    "merchantId": "MID-887241",
    "status": "New",
    "underwritingStatus": "Initialized",
    "lastUpdate": "2026-04-01T08:00:00Z",
    "comment": "Application created.",
    "underwriter": null
  },
  {
    "merchantProfileId": 48201,
    "merchantId": "MID-887241",
    "status": "Pending",
    "underwritingStatus": "Pending",
    "lastUpdate": "2026-04-15T11:30:00Z",
    "comment": "Submitted to TSYS. Awaiting UW review.",
    "underwriter": "Sarah Thompson"
  },
  {
    "merchantProfileId": 48201,
    "merchantId": "MID-887241",
    "status": "UnderReview",
    "underwritingStatus": "Pending",
    "lastUpdate": "2026-05-10T09:15:00Z",
    "comment": "Driver's license and bank statements required.",
    "underwriter": "Sarah Thompson"
  },
  {
    "merchantProfileId": 48201,
    "merchantId": "MID-887241",
    "status": "PendingReview",
    "underwritingStatus": "PendingReview",
    "lastUpdate": "2026-05-20T14:45:00Z",
    "comment": "Uploaded driver's license and 3 months of bank statements.",
    "underwriter": "Sarah Thompson"
  }
]

Error Codes

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

Common Mistakes

  • Using this endpoint to get the current status when GET /api/v1/underwriting/statuses is more appropriate for portfolio-wide monitoring.
  • Assuming entries are always returned newest-first — parse the lastUpdate field to determine order rather than relying on array position.
  • Expecting this to show UW task ticket activity — this endpoint tracks merchant-level status changes only, not the granular ticket-level history.

Related Endpoints

  • GET /api/v1/underwriting/statuses — get the current status for all merchants (no id required)
  • POST /api/v1/underwriting/pending-review — trigger a PendingReview status transition
  • GET /api/v1/merchant/getAutoUwResults — see automated check results that may have influenced status changes

Example

curl -X GET "https://hq.staging.netevia.dev/api/v1/underwriting/status-history?id=48201" \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)"
Query Params
int32
required
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