Get Ticket
This endpoint retrieves detailed information about a specific support or service ticket within the Netevia Banking platform. It returns the ticket's current status, message history, file attachments, and any relationship to a parent ticket. It can be used by customer service representatives, administrators, or customers tracking the progress of their own submitted tickets.
Endpoint
GET /api/tickets
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint when you need to display the full details of an existing support or service ticket to an end user or agent. This is useful for support dashboards that show ticket status and conversation history, or for polling ticket updates after a ticket has been submitted. Partners can also use it to surface ticket resolution progress directly within their own application interface.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| ticketId | integer (int32) | Yes | The unique numeric identifier of the ticket to retrieve. |
Response
200 OK
Ticket object (netevia.client.models.ticket)
| Field | Type | Description |
|---|---|---|
| ticketId | integer (int32) | The unique identifier of the ticket. |
| createdDate | string (date-time) | The date and time the ticket was created (ISO 8601). |
| status | string | The current status of the ticket (e.g., Open, In Progress, Resolved, Closed). |
| ticketMessages | array of ticketMessage | List of messages associated with the ticket. Null if no messages exist. |
| ticketAttachments | array of ticketAttachment | List of file attachments associated with the ticket. Null if no attachments exist. |
| parentTicketId | integer (int32) | ID of the parent ticket if this ticket is a sub-ticket. Null if no parent. |
ticketMessage object
| Field | Type | Description |
|---|---|---|
| ticketMessageId | integer (int32) | The unique identifier of the message. |
| createdBy | string | The name or identifier of the user who created the message. |
| text | string | The content of the message. |
| createdDate | string (date-time) | The date and time the message was created (ISO 8601). |
ticketAttachment object
| Field | Type | Description |
|---|---|---|
| ticketMessageId | integer (int32) | The ID of the ticket message this attachment belongs to. Null if not linked to a specific message. |
| fileName | string | The stored file name of the attachment. |
| contentType | string | The MIME type of the attachment (e.g., image/png, application/pdf). |
| fileBase64 | string | The Base64-encoded content of the attachment file. |
| createdDate | string (date-time) | The date and time the attachment was uploaded (ISO 8601). |
| originalFileName | string | The original file name as provided by the uploader. |
{
"ticketId": 98241,
"createdDate": "2026-05-15T10:32:00Z",
"status": "In Progress",
"ticketMessages": [
{
"ticketMessageId": 1001,
"createdBy": "[email protected]",
"text": "We have received your request and are currently investigating the issue.",
"createdDate": "2026-05-15T11:00:00Z"
},
{
"ticketMessageId": 1002,
"createdBy": "[email protected]",
"text": "Thank you. Please let me know when it is resolved.",
"createdDate": "2026-05-15T11:45:00Z"
}
],
"ticketAttachments": [
{
"ticketMessageId": 1001,
"fileName": "screenshot_2026-05-15.png",
"contentType": "image/png",
"fileBase64": "iVBORw0KGgoAAAANSUhEUgAA...",
"createdDate": "2026-05-15T11:00:00Z",
"originalFileName": "screenshot.png"
}
],
"parentTicketId": null
}Error Codes
| Code | When it happens |
|---|---|
| 400 | The ticketId query parameter is missing, non-numeric, or otherwise invalid. |
| 401 | Token missing, expired, or invalid. |
| 403 | Insufficient permissions — the authenticated user does not have access to the requested ticket. |
| 404 | No ticket was found matching the provided ticketId. |
| 500 | Internal server error while processing the request. |
Common Mistakes
- Passing
ticketIdas a string instead of an integer — the schema defines it asint32, so non-numeric values will result in a400error. - Querying a ticket that belongs to a different partner or customer context — ensure the authenticated token has permission to view the requested ticket, or a
403will be returned. - Expecting
ticketMessagesorticketAttachmentsto always be present — both fields are nullable and may benullor absent when no messages or attachments exist. - Not refreshing the Bearer token before it expires (10-minute lifetime) — stale tokens will result in a
401response.
Related Endpoints
POST /api/tickets— Create a new support or service ticket.POST /api/tickets/message— Add a message to an existing ticket.POST /api/tickets/attachment— Upload a file attachment to a ticket.
Example
curl -X GET "https://api.banking.netevia.dev/api/tickets?ticketId=98241" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"