| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Add Note
Adds a categorized note to a merchant's profile or application record. Notes can represent comments, observations, or important details recorded during the merchant management and onboarding process. Each note must be assigned a message type that routes it to the appropriate team.
Endpoint
POST /api/v1/merchant/note
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 document important events, observations, or follow-up items on a merchant's record during the boarding or ongoing management process. Notes are scoped by messageType so the right team (Risk, Customer Service, Tech Support, etc.) can filter and act on them. This is particularly useful for underwriting review workflows where an audit trail of communications is required.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| id | integer (int32) | Yes | The merchant profile ID to which the note is being added |
| messageType | string (enum) | Yes | Category of the note. One of: CustomerService, Risk, Equipment, POS, Other, TechSupport, Accounting |
| note | string | Yes | The text content of the note |
{
"id": 48291,
"messageType": "Risk",
"note": "Merchant requested increase in monthly volume cap. Reviewing processing history for the past 6 months before approval."
}Response
200 OK
| Field | Type | Description |
|---|---|---|
| data.success | boolean | true if the note was successfully added |
| status | string | HTTP status label (e.g., OK) |
| error | string | Error message if the request failed |
| warning | string | Non-fatal warning message, if any |
| validationResults | array | List of field-level validation errors |
| requestId | integer | Unique identifier for this API request |
{
"data": {
"success": true
},
"status": "OK",
"error": null,
"warning": null,
"validationResults": [],
"requestId": 90341
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Required fields (id, messageType, or note) are missing or invalid |
| 401 | Invalid or missing Basic Auth credentials |
| 403 | User does not have permission for this operation |
| 404 | Merchant with the specified id not found |
| 500 | Internal server error |
Common Mistakes
- Omitting
messageType— all three fields (id,messageType,note) are required. - Using an invalid enum value for
messageType— must be exactly one of the seven listed values (case-sensitive). - Passing a non-existent
id— verify the merchant profile ID using the merchant status or search endpoints before posting a note. - Sending an empty string for
note— the note content must be non-empty.
Related Endpoints
GET /api/v1/merchant/notes— retrieve all notes for a merchantPOST /api/v1/merchant/attachment— upload a file attachment to a merchant recordPOST /api/v1/merchant/approve— submit a merchant for underwriting approval
Example
curl -X POST https://hq.staging.netevia.dev/api/v1/merchant/note \
-H "Authorization: Basic $(echo -n 'username:password' | base64)" \
-H "Content-Type: application/json" \
-d '{
"id": 48291,
"messageType": "Risk",
"note": "Merchant requested increase in monthly volume cap. Reviewing processing history for the past 6 months before approval."
}'