Send Ticket Notification
This endpoint triggers a notification for a specific support ticket within the banking application. It allows partners to inform users in real-time about important updates related to their tickets, such as status changes or resolution events. The notification type is controlled by an event code passed as a path parameter.
Endpoint
POST /netevia/ticket/{ticketId}/notification/{e}
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 a support ticket's status changes and affected users need to be notified promptly. It is particularly useful in customer support workflows where timely communication — such as ticket resolution, escalation, or status updates — improves customer satisfaction. Partners can trigger specific event-based notifications by selecting the appropriate event code.
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| ticketId | integer (int32) | Yes | The unique identifier of the ticket for which the notification is being sent. |
| e | integer (int32) | Yes | The notification event code. Accepted values: 0, 1, 2 (see event codes below). |
Event Code Values (e)
e)| Value | Meaning |
|---|---|
| 0 | Ticket created / initial notification |
| 1 | Ticket status update |
| 2 | Ticket resolved / closed notification |
Response
200 OK
A successful response indicates the notification was triggered. No response body is returned.
{}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required path parameters or invalid event code value |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to send notifications for this ticket |
| 404 | Ticket not found for the given ticketId |
| 500 | Internal server error |
Common Mistakes
- Passing an event code value outside the accepted enum range (
0,1,2) will result in a 400 error. - Using an expired or missing Bearer token will return a 401 error — always refresh the token before making calls.
- Providing a
ticketIdthat does not exist or belongs to a different partner will return a 404 error.
Related Endpoints
POST /netevia/ticket— Create a new support ticketGET /netevia/ticket/{ticketId}— Retrieve details of a specific ticketPUT /netevia/ticket/{ticketId}— Update the status or details of an existing ticket
Example
curl -X POST https://api.banking.netevia.dev/netevia/ticket/10042/notification/1 \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"Success