Get all TicketTypes

Get All TicketTypes

This endpoint returns the complete list of ticket type enum values available within the Netevia Banking platform. Each entry includes the enum name, numeric ID, description, group classification, and the API endpoints where it is applicable. Use this reference to ensure valid ticket type values are supplied in other API requests.

Endpoint

GET /api/enums/TicketType

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 building or validating integrations that require a ticket type field. It provides a canonical, up-to-date list of all valid ticket type identifiers so your application can dynamically populate dropdowns, validate inputs, or map numeric IDs to human-readable labels without hardcoding values.

Response

200 OK

Returns an array of enum description objects.

FieldTypeDescription
namestringThe machine-readable name of the ticket type enum value
idinteger (int32)The numeric identifier for the ticket type
descriptionstringA human-readable description of the ticket type
groupNamestringThe group or category this ticket type belongs to
endpointsarray of stringList of API endpoints where this ticket type is used
[
  {
    "name": "SupportRequest",
    "id": 1,
    "description": "General support request ticket",
    "groupName": "Support",
    "endpoints": [
      "/api/tickets",
      "/api/tickets/{ticketId}"
    ]
  },
  {
    "name": "DisputeResolution",
    "id": 2,
    "description": "Ticket raised for transaction dispute resolution",
    "groupName": "Disputes",
    "endpoints": [
      "/api/tickets",
      "/api/tickets/{ticketId}"
    ]
  },
  {
    "name": "AccountInquiry",
    "id": 3,
    "description": "Inquiry related to account status or details",
    "groupName": "Account",
    "endpoints": [
      "/api/tickets"
    ]
  }
]

Error Codes

CodeWhen it happens
401Token missing, expired, or invalid
403Insufficient permissions
500Internal server error

Common Mistakes

  • Using a hardcoded ticket type ID instead of fetching from this endpoint — IDs may change; always reference this endpoint dynamically.
  • Omitting the Authorization header or supplying an expired token, which results in a 401 response.
  • Expecting a single object in the response — this endpoint always returns an array, even when only one ticket type exists.

Related Endpoints

  • GET /api/enums/CardType — Retrieve all card type enum values
  • GET /api/enums/TransactionType — Retrieve all transaction type enum values
  • POST /api/tickets — Create a new ticket using a valid ticket type ID

Example

curl -X GET https://api.banking.netevia.dev/api/enums/TicketType \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
text/plain
application/json
text/json