Get the list of all tickets

Get All Tickets

This endpoint retrieves a complete list of all support and service tickets associated with the currently authenticated client. Each ticket record includes its status, topic, creation date, and any associated update field request type. This is useful for clients who need a full overview of their ticket history, including open, in-progress, and closed items.

Endpoint

GET /api/tickets/all

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 client needs to view all of their submitted support or service tickets in one call. It is suitable for building ticket dashboards, tracking the lifecycle of requests, or auditing historical interactions with the banking platform. Because the endpoint returns all tickets without filtering, it is best used when a complete record is needed rather than a targeted lookup.

Response

200 OK

FieldTypeDescription
ticketIdinteger (int32)Unique identifier for the ticket.
createdDatestring (date-time)ISO 8601 date-time when the ticket was created.
statusstringCurrent status of the ticket (e.g., Open, Closed, In Progress). Nullable.
textstringThe body or description text of the ticket. Nullable.
topicstringThe topic or subject category of the ticket. Nullable.
topicIdinteger (int32)Numeric identifier for the ticket topic.
userProfileIdinteger (int32)Identifier of the user profile that owns the ticket.
parentTicketIdinteger (int32)Identifier of a parent ticket if this is a follow-up or child ticket. Nullable.
updateFieldRequeststring (enum)The type of profile field update requested via the ticket. See enum values below. Nullable.

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": 100123,
    "createdDate": "2024-03-15T10:30:00Z",
    "status": "Open",
    "text": "I need to update the email address on my business account.",
    "topic": "Profile Update",
    "topicId": 5,
    "userProfileId": 98765,
    "parentTicketId": null,
    "updateFieldRequest": "Email"
  },
  {
    "ticketId": 100124,
    "createdDate": "2024-02-10T08:45:00Z",
    "status": "Closed",
    "text": "Please update the legal business name as per the attached documentation.",
    "topic": "Business Information Update",
    "topicId": 7,
    "userProfileId": 98765,
    "parentTicketId": null,
    "updateFieldRequest": "LegalBusinessName"
  },
  {
    "ticketId": 100125,
    "createdDate": "2024-04-01T14:50:00Z",
    "status": "In Progress",
    "text": "Requesting review for loan approval based on latest business financials.",
    "topic": "Loan Review",
    "topicId": 12,
    "userProfileId": 98765,
    "parentTicketId": 100123,
    "updateFieldRequest": "LoanApprove"
  }
]

Error Codes

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

Common Mistakes

  • Expecting the response to be a JSON object with a tickets key — the endpoint returns a top-level JSON array, not a wrapped object.
  • Assuming parentTicketId will always be populated — it is nullable and will be null for top-level tickets that have no parent.
  • Treating updateFieldRequest as a free-form string — it is a strict enum; only the documented values are valid when this field is present.
  • Not refreshing the Bearer token before it expires (10-minute lifetime); calls made with an expired token will return 401.

Related Endpoints

  • POST /api/tickets — Create a new support or service ticket
  • GET /api/tickets/{ticketId} — Retrieve details for a specific ticket by ID
  • PUT /api/tickets/{ticketId} — Update an existing ticket

Example

curl -X GET https://api.banking.netevia.dev/api/tickets/all \
  -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