| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Retrieve Notes for the Merchant Application
Fetches all notes that have been recorded against a merchant's application during the onboarding or review process. Each note includes the author, the note text, and the date it was created. Notes provide an audit trail of interactions, observations, or decisions made by the ISO or underwriting team throughout the merchant lifecycle.
Endpoint
GET /api/v1/merchant/notes
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 display the history of internal comments and updates attached to a merchant application. This is particularly useful during underwriting review or when a support agent needs to understand prior decisions or context for a merchant record.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | integer (int32) | Yes | The unique internal ID of the merchant application |
Response
200 OK
| Field | Type | Description |
|---|---|---|
| data | array | List of Note objects associated with the merchant application |
| data[].text | string | The body text of the note |
| data[].author | string | Username or display name of the person who created the note |
| data[].date | string (date-time) | ISO 8601 timestamp of when the note was recorded |
| status | string | HTTP status string (e.g., "OK") |
| error | string | Error message if the request failed |
| warning | string | Non-fatal warning message |
| validationResults | array | List of validation errors, each with memberNames and errorMessage |
| requestId | integer (int32) | Internal request tracking ID |
{
"data": [
{
"text": "Application received and initial review completed. Missing bank statement — contacted merchant.",
"author": "jsmith",
"date": "2026-04-15T10:23:00Z"
},
{
"text": "Bank statement uploaded by merchant. Forwarding to underwriting.",
"author": "alopez",
"date": "2026-04-17T14:05:00Z"
}
],
"status": "OK",
"error": null,
"warning": null,
"validationResults": [],
"requestId": 55102
}Error Codes
| Code | When it happens |
|---|---|
| 400 | The id query parameter is missing or not a valid integer |
| 401 | Invalid or missing Basic Auth credentials |
| 403 | User does not have permission for this operation |
| 404 | No merchant application found for the given id |
| 500 | Internal server error |
Common Mistakes
- Providing a non-integer value for
id— this parameter must be a numeric merchant application ID. - Expecting paginated results — this endpoint returns all notes at once; there is no page or limit parameter.
- Confusing this endpoint with the underwriting notes endpoint (
/api/v1/merchant/getUnderwritingNotes), which is specific to underwriting-related observations.
Related Endpoints
POST /api/v1/merchant/addNote— add a new note to a merchant applicationGET /api/v1/merchant/getUnderwritingNotes— retrieve underwriting-specific notesGET /api/v1/merchant/status— check the current status of the merchant application
Example
curl -X GET "https://hq.staging.netevia.dev/api/v1/merchant/notes?id=10045" \
-H "Authorization: Basic $(echo -n 'username:password' | base64)" \
-H "Accept: application/json"