| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Get Comments by Ticket ID
Returns a list of all comments associated with a given ticket, ordered chronologically. Each comment includes the author, timestamp, and full text. This is the primary way to track the conversation thread on a ticket — for example, to check whether an underwriter has responded to an Instant Funding request.
Endpoint
GET /api/v1/tickets/getCommentsByTicketId
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 poll for updates on an open ticket or to display the full conversation history to an ISO agent. This is step 3 in the typical Instant Funding workflow — after creating a ticket with POST /api/v1/tickets/create, call this endpoint periodically to check for responses from the Underwriting department.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
id | integer (int32) | Yes | Merchant profile ID associated with the ticket. |
ticketId | integer (int32) | Yes | ID of the ticket whose comments to retrieve. |
Response
200 OK
| Field | Type | Description |
|---|---|---|
data | array | List of comment objects for the ticket. |
data[].ticketCommentId | integer | Unique ID of the comment. |
data[].createdDate | string (date-time) | ISO 8601 timestamp of when the comment was posted. |
data[].createdBy | string | Username or display name of the comment author. |
data[].text | string | Full text content of the comment. |
requestId | integer | Internal request tracking ID. |
success | boolean | true if the comments were retrieved successfully. |
error | string | Error message if the operation failed. |
validationErrors | array | List of field-level validation issues. |
{
"data": [
{
"ticketCommentId": 7710,
"createdDate": "2026-05-15T09:10:00Z",
"createdBy": "[email protected]",
"text": "Please enable Instant Funding for merchant Sunshine Retail LLC. Banking application submitted."
},
{
"ticketCommentId": 7712,
"createdDate": "2026-05-20T14:32:00Z",
"createdBy": "[email protected]",
"text": "We have reviewed the banking application. Please provide a copy of the voided check to proceed with Instant Funding activation."
},
{
"ticketCommentId": 7715,
"createdDate": "2026-05-21T08:05:00Z",
"createdBy": "[email protected]",
"text": "Voided check has been attached. Please review and proceed."
}
],
"requestId": 98129,
"success": true,
"error": null,
"validationErrors": []
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing or invalid query parameters (id or ticketId). |
| 401 | Invalid or missing Basic Auth credentials. |
| 403 | User does not have permission for this operation. |
| 404 | Ticket not found for the given ticketId. |
| 500 | Internal server error. |
Common Mistakes
- Omitting the
id(merchant profile ID) — bothidandticketIdare required. - Treating an empty
dataarray as an error — a ticket with no comments returnssuccess: truewith an empty array. - Not checking
createdByto distinguish ISO-submitted comments from underwriter responses.
Related Endpoints
POST /api/v1/tickets/comment— Add a new comment to the ticket.GET /api/v1/tickets/getCommentById— Retrieve a single comment by its ID.GET /api/v1/tickets/getTicketById— Check overall ticket status alongside comments.
Example
curl -X GET "https://hq.staging.netevia.dev/api/v1/tickets/getCommentsByTicketId?id=70269&ticketId=48291" \
-H "Authorization: Basic $(echo -n 'username:password' | base64)"