Reopen Ticket
This endpoint allows users to reopen a previously closed support ticket within the Netevia Banking platform. It is useful when an issue has not been fully resolved or when new information requires further action on a closed case. Submitting a reopen request restores the ticket to active status and requires the caller to provide context text explaining why the ticket is being reopened.
Endpoint
POST /api/support/reopenTicket
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2
Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint when a customer or partner reports that a previously closed support ticket did not fully resolve their issue. It is also appropriate when additional context or documentation has become available after ticket closure. Reopening a ticket routes it back into the active support queue for follow-up action.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| ticketId | integer (int32) | Yes | The unique identifier of the closed ticket to be reopened |
| text | string | Yes | Explanation or additional context for why the ticket is being reopened (minimum 1 character) |
{
"ticketId": 10482,
"text": "The issue persists after the suggested fix. The transaction still shows as pending after 5 business days."
}Response
200 OK
| Field | Type | Description |
|---|---|---|
| ticketId | integer (int32) | Unique identifier of the ticket |
| ticketTopicId | integer (int32) | Identifier of the topic category associated with the ticket |
| ticketTopic | object | Details of the ticket topic (see ticketTopic object below) |
| userProfileId | integer (int32) | Identifier of the user profile that owns the ticket |
| created | string (date-time) | Timestamp when the ticket was originally created |
| text | string | null | The text content of the most recent ticket entry |
| parentTicketId | integer (int32) | null | Identifier of the parent ticket, if this ticket is a follow-up |
| isNew | boolean | Indicates whether the ticket has been read/acknowledged |
| updateFieldRequest | string | null | The type of field update request associated with the ticket, if applicable |
| ipAddress | string | null | IP address from which the ticket was submitted |
ticketTopic object
| Field | Type | Description |
|---|---|---|
| id | integer (int32) | Unique identifier of the topic |
| name | string | null | Display name of the topic category |
| responseTime | string | null | Expected response time for this topic category |
| isDeleted | boolean | Whether the topic has been soft-deleted |
| isHidden | boolean | Whether the topic is hidden from public selection |
updateFieldRequest enum values
Email, Phone, Address, PrimAuthEmail, PrimAuthPhone, PrimAuthAddress, Owner1Email, Owner1Phone, Owner1Address, Owner2Email, Owner2Phone, Owner2Address, Owner3Email, Owner3Phone, Owner3Address, Owner4Email, Owner4Phone, Owner4Address, Employer, EmployerIdentificationNumber, BusinessStartDate, DateOfBirth, Ssn, GivenName, MiddleName, FamilyName, DoingBusinessAsName, LegalBusinessName, LoanApprove
{
"ticketId": 10482,
"ticketTopicId": 3,
"ticketTopic": {
"id": 3,
"name": "Transaction Dispute",
"responseTime": "1-2 business days",
"isDeleted": false,
"isHidden": false
},
"userProfileId": 78901,
"created": "2026-05-15T10:23:00Z",
"text": "The issue persists after the suggested fix. The transaction still shows as pending after 5 business days.",
"parentTicketId": 10400,
"isNew": true,
"updateFieldRequest": null,
"ipAddress": null
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields (ticketId or text), or text is empty |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to reopen the specified ticket |
| 404 | Ticket with the provided ticketId not found |
| 500 | Internal server error |
Common Mistakes
- Omitting the
textfield or sending an empty string —texthas a minimum length of 1 and is required - Attempting to reopen a ticket that is already in an active (non-closed) state — verify ticket status before calling this endpoint
- Using a
ticketIdthat belongs to a different user profile than the authenticated token — ensure the token matches the ticket owner - Forgetting to include the
Authorization: Bearerheader, resulting in a 401 response
Related Endpoints
POST /api/support/createTicket— Create a new support ticketPOST /api/support/closeTicket— Close an active support ticketPOST /api/support/addMessage— Add a message to an existing open ticketGET /api/support/getTickets— Retrieve a list of support tickets for the authenticated user
Example
curl -X POST https://api.banking.netevia.dev/api/support/reopenTicket \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"ticketId": 10482,
"text": "The issue persists after the suggested fix. The transaction still shows as pending after 5 business days."
}'