Get all comments from ticket

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

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

ParameterTypeRequiredDescription
idinteger (int32)YesMerchant profile ID associated with the ticket.
ticketIdinteger (int32)YesID of the ticket whose comments to retrieve.

Response

200 OK

FieldTypeDescription
dataarrayList of comment objects for the ticket.
data[].ticketCommentIdintegerUnique ID of the comment.
data[].createdDatestring (date-time)ISO 8601 timestamp of when the comment was posted.
data[].createdBystringUsername or display name of the comment author.
data[].textstringFull text content of the comment.
requestIdintegerInternal request tracking ID.
successbooleantrue if the comments were retrieved successfully.
errorstringError message if the operation failed.
validationErrorsarrayList 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

CodeWhen it happens
400Missing or invalid query parameters (id or ticketId).
401Invalid or missing Basic Auth credentials.
403User does not have permission for this operation.
404Ticket not found for the given ticketId.
500Internal server error.

Common Mistakes

  • Omitting the id (merchant profile ID) — both id and ticketId are required.
  • Treating an empty data array as an error — a ticket with no comments returns success: true with an empty array.
  • Not checking createdBy to 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)"
Query Params
int32
required
int32
required
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/json