post
https://api.banking.netevia.dev/api/support/createContactSupportTicket
Create Contact Support Ticket
This endpoint creates a new support ticket associated with a customer's email address and a specific support topic. It is used to open a communication thread with the Netevia support team regarding account or profile-related issues. Upon success, the response returns the full ticket record including its unique ID, topic details, and creation timestamp.
Endpoint
POST /api/support/createContactSupportTicket
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 customer or partner needs to contact Netevia support about a specific issue such as an account update request, a dispute, or a general inquiry. It is appropriate when you want to programmatically open a support case rather than directing the user to a manual support channel. The topicId field allows routing the ticket to the correct support queue.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| string (email) | Yes | Email address of the contact submitting the ticket. Must be a valid email format. | |
| text | string | Yes | The body or message of the support ticket. Minimum length of 1 character. |
| topicId | integer (int32) | No | ID of the support topic category to route the ticket. Obtain available topic IDs from the support topics listing. |
{
"topicId": 3,
"text": "I need to update the phone number associated with my account. Please advise on next steps.",
"email": "[email protected]"
}Response
200 OK
| Field | Type | Description |
|---|---|---|
| ticketId | integer (int32) | Unique identifier for the newly created support ticket. |
| ticketTopicId | integer (int32) | ID of the support topic associated with this ticket. |
| ticketTopic | object | Expanded topic details. See ticketTopic object below. |
| ticketTopic.id | integer (int32) | Unique ID of the topic. |
| ticketTopic.name | string | Display name of the support topic. |
| ticketTopic.responseTime | string | Expected response time for this topic (e.g., "24 hours"). |
| ticketTopic.isDeleted | boolean | Whether this topic has been soft-deleted. |
| ticketTopic.isHidden | boolean | Whether this topic is hidden from public display. |
| userProfileId | integer (int32) | Internal profile ID of the user who submitted the ticket. |
| created | string (date-time) | ISO 8601 timestamp of when the ticket was created. |
| text | string | The message body submitted in the ticket. |
| parentTicketId | integer (int32) | null | ID of a parent ticket if this is a follow-up reply; null for new tickets. |
| isNew | boolean | Indicates whether the ticket is new and has not yet been reviewed by support. |
| updateFieldRequest | string | Enum indicating a profile field update type requested via the ticket (e.g., Phone, Email, Address, Ssn, DateOfBirth, LegalBusinessName). |
| ipAddress | string | null | IP address from which the ticket was submitted. |
{
"ticketId": 10245,
"ticketTopicId": 3,
"ticketTopic": {
"id": 3,
"name": "Account Update Request",
"responseTime": "24 hours",
"isDeleted": false,
"isHidden": false
},
"userProfileId": 88401,
"created": "2026-06-08T14:32:00Z",
"text": "I need to update the phone number associated with my account. Please advise on next steps.",
"parentTicketId": null,
"isNew": true,
"updateFieldRequest": "Phone",
"ipAddress": null
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields (email or text) or validation error (e.g., invalid email format, empty text) |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to create a support ticket |
| 404 | Specified topicId not found |
| 500 | Internal server error |
Common Mistakes
- Omitting the
emailortextfields — both are required; the request will return a 400 error without them. - Providing an invalid email format for the
emailfield — the value must conform to standard email formatting. - Submitting an empty string for
text— the field requires a minimum length of 1 character. - Using an incorrect or stale
topicId— verify valid topic IDs before submission to ensure proper routing.
Related Endpoints
GET /api/support/getContactSupportTickets— Retrieve a list of support tickets for the authenticated userPOST /api/support/replyToContactSupportTicket— Post a reply to an existing support ticketGET /api/support/getSupportTopics— Retrieve available support topic categories and their IDs
Example
curl -X POST https://api.banking.netevia.dev/api/support/createContactSupportTicket \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"topicId": 3,
"text": "I need to update the phone number associated with my account. Please advise on next steps.",
"email": "[email protected]"
}'