| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Get Comment by ID
Fetches a specific comment from a ticket using the comment's unique identifier. The response includes the comment text, the author, and the timestamp when it was created. Use the Get Comments by Ticket ID endpoint first to discover valid comment IDs.
Endpoint
GET /api/v1/tickets/getCommentById
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 retrieve the full details of a known comment — for example, after receiving a webhook notification about a new comment on a subscribed ticket, where the callback body includes the ticket ID and enough context to identify the comment of interest. It is also useful for directly fetching a comment when you already know its ID from a prior list operation.
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 the comment belongs to. |
commentId | integer (int32) | Yes | Unique ID of the comment to retrieve. |
Response
200 OK
| Field | Type | Description |
|---|---|---|
data.ticketCommentId | integer | The 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 | The full text content of the comment. |
requestId | integer | Internal request tracking ID. |
success | boolean | true if the comment was retrieved successfully. |
error | string | Error message if the operation failed. |
validationErrors | array | List of field-level validation issues. |
{
"data": {
"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."
},
"requestId": 98128,
"success": true,
"error": null,
"validationErrors": []
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing or invalid query parameters (id, ticketId, or commentId). |
| 401 | Invalid or missing Basic Auth credentials. |
| 403 | User does not have permission for this operation. |
| 404 | Comment not found for the given commentId on the specified ticket. |
| 500 | Internal server error. |
Common Mistakes
- Passing a
commentIdthat belongs to a different ticket — comment IDs must correspond to the specifiedticketId. - Omitting the
id(merchant profile ID) parameter — all three parameters are required. - Using the merchant profile ID as the
commentIdby mistake — theidfield is the merchant profile ID, not the comment ID.
Related Endpoints
GET /api/v1/tickets/getCommentsByTicketId— List all comments on a ticket to discover validcommentIdvalues.POST /api/v1/tickets/comment— Add a new comment to a ticket.GET /api/v1/tickets/getTicketById— Retrieve overall ticket details and status.
Example
curl -X GET "https://hq.staging.netevia.dev/api/v1/tickets/getCommentById?id=70269&ticketId=48291&commentId=7712" \
-H "Authorization: Basic $(echo -n 'username:password' | base64)"