Get profile info of a profile assigned to merchant

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

Get Underwriting Assigned To

Returns the profile information of the underwriter or reviewer who has been assigned to a specific merchant profile. The response includes the assignee's full name, email address, phone number, and profile ID. This is useful for ISOs who need to contact the underwriter handling their merchant's application directly.

Endpoint

GET /api/v1/merchant/underwriting/assignedTo

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 to identify or contact the specific underwriter responsible for reviewing a merchant's application. During the underwriting workflow — particularly when a merchant is in UnderwritingPending or UnderReview status — knowing who is assigned can help ISOs reach out for status updates or escalation. This endpoint also provides the profileId which may be used in other assignment or task management operations.

Query Parameters

ParameterTypeRequiredDescription
merchantProfileIdinteger (int32)YesThe merchant profile ID to look up the assigned underwriter for

Response

200 OK

FieldTypeDescription
fullNamestringFull name of the assigned underwriter
emailstringEmail address of the assigned underwriter
phonestringPhone number of the assigned underwriter
profileIdintegerProfile ID of the assigned underwriter
requestIdintegerUnique identifier for this API request
successbooleantrue if the request completed successfully
errorstringError message if no underwriter is assigned or the request failed
validationErrorsarrayField-level validation errors
{
  "fullName": "Sarah Thompson",
  "email": "[email protected]",
  "phone": "+1-555-302-7841",
  "profileId": 204,
  "requestId": 88790,
  "success": true,
  "error": null,
  "validationErrors": []
}

Error Codes

CodeWhen it happens
400merchantProfileId is missing or not a valid integer
401Invalid or missing Basic Auth credentials
403User does not have permission for this operation
404Merchant profile not found or no underwriter has been assigned yet
500Internal server error

Common Mistakes

  • Calling this endpoint for a merchant that has not yet been submitted to underwriting — no underwriter will be assigned until the merchant enters the UW workflow.
  • Treating a null or empty response as an error — if success is true but fullName is empty, no underwriter has been assigned yet rather than the request failing.

Related Endpoints

  • GET /api/v1/underwriting/statuses — check the current underwriting status of the merchant
  • GET /api/v1/uwTasks/getByMerchantId — list UW task tickets assigned to the merchant
  • GET /api/v1/underwriting/status-history — review the full underwriting status history

Example

curl -X GET "https://hq.staging.netevia.dev/api/v1/merchant/underwriting/assignedTo?merchantProfileId=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