Add Comment

Adds a text comment to an existing ticket, enabling ongoing communication between the ISO and the Netevia support or underwriting team. Comments are timestamped and attributed to the authenticated user. All comments posted to a ticket are retrievable via the Get Comments by Ticket ID endpoint.

Endpoint

POST /api/v1/tickets/comment

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 add follow-up information, respond to underwriter questions, or provide status updates on an open ticket. This is the primary communication channel for tickets after creation — for example, confirming a merchant's Instant Funding setup details when prompted by the Underwriting department.

Request Body

{
  "id": 70269,
  "ticketId": 48291,
  "text": "Merchant has confirmed ACH account details. Please proceed with Instant Funding activation."
}

Response

200 OK

{
  "requestId": 98124,
  "success": true,
  "error": null,
  "validationErrors": []
}

Error Codes

Common Mistakes

• Confusing id (merchant profile ID) with ticketId — both are required and serve different purposes.
• Posting an empty string for text, which will cause a validation error.
• Commenting on a ticket that has already been resolved without first checking its current status.

Related Endpoints

• GET /api/v1/tickets/getCommentsByTicketId — Retrieve all comments on a ticket.
• GET /api/v1/tickets/getCommentById — Retrieve a specific comment by its ID.
• POST /api/v1/tickets/create — Create the ticket before adding comments.

Example

curl -X POST https://hq.staging.netevia.dev/api/v1/tickets/comment \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 70269,
    "ticketId": 48291,
    "text": "Merchant has confirmed ACH account details. Please proceed with Instant Funding activation."
  }'