Adds a new message or comment to an existing support ticket.
Add Message to Ticket
This endpoint allows authorized users to post a new message or comment to an existing support or service ticket. By supplying the ticketId and message text, clients and support staff can maintain ongoing communication within the ticket thread. The response returns the newly created message record including its unique identifier and creation timestamp.
Endpoint
POST /api/tickets/message
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 whenever a partner or end user needs to append follow-up information, ask a question, or respond to the support team within an open ticket. It is appropriate for both initial context after ticket creation and subsequent replies during active resolution. This endpoint is the primary mechanism for threaded ticket communication in the Netevia Banking API.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
ticketId | integer (int32) | No | The unique identifier of the ticket to which the message will be added. |
text | string | Yes | The content of the message to add to the ticket. Minimum length: 1 character. |
{
"ticketId": 123456,
"text": "Can you provide an update on the issue? We are still seeing the error on our end."
}Response
200 OK
| Field | Type | Description |
|---|---|---|
ticketMessageId | integer (int32) | Unique identifier of the newly created ticket message. |
createdBy | string | Identifier or name of the user who created the message. May be null. |
text | string | The content of the message that was added. May be null. |
createdDate | string (date-time) | ISO 8601 timestamp indicating when the message was created. |
{
"ticketMessageId": 987654,
"createdBy": "[email protected]",
"text": "Can you provide an update on the issue? We are still seeing the error on our end.",
"createdDate": "2024-03-15T14:30:00Z"
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields (text) or validation error (e.g., empty string) |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to add a message to the specified ticket |
| 404 | The specified ticketId does not exist or is not accessible |
| 500 | Internal server error |
Common Mistakes
- Omitting the
textfield or sending an empty string —textis required and must have a minimum length of 1. - Passing
ticketIdas a string instead of an integer — the schema expectsint32, not a quoted value. - Using an expired Bearer token — tokens last 10 minutes; refresh via
POST /api/auth/refreshbefore calling this endpoint. - Attempting to message a ticket that belongs to a different partner or customer — this returns 403 or 404.
Related Endpoints
POST /api/tickets— Create a new support ticketGET /api/tickets— List all tickets for the authenticated user or partnerGET /api/tickets/{ticketId}— Retrieve details and message history for a specific ticket
Example
curl -X POST https://api.banking.netevia.dev/api/tickets/message \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"ticketId": 123456,
"text": "Can you provide an update on the issue? We are still seeing the error on our end."
}'