Get the list of new tickets

Get New Tickets

This endpoint retrieves a list of all new or unresolved support and service tickets associated with the currently authenticated client. New tickets are those that have been recently created and are still in an open or unaddressed status, awaiting further action or resolution. Use this endpoint to track ongoing issues or requests that have not yet been resolved.

Endpoint

GET /api/tickets/new

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 partner or client application needs to display a dashboard or notification feed of open support tickets. It is useful for customer service workflows where agents or customers need to see which issues are still pending resolution. This endpoint should be polled or called on page load to present the current state of unresolved tickets.

Response

200 OK

FieldTypeDescription
ticketIdinteger (int32)Unique identifier for the ticket
createdDatestring (date-time)ISO 8601 timestamp of when the ticket was created
statusstringCurrent status of the ticket (e.g., open, pending)
textstringBody or description of the ticket
topicstringHuman-readable topic or category label for the ticket
topicIdinteger (int32)Numeric identifier for the ticket topic/category
userProfileIdinteger (int32)ID of the user profile who created the ticket
parentTicketIdinteger (int32)ID of the parent ticket if this is a follow-up or sub-ticket; null if top-level
updateFieldRequeststring (enum)If the ticket is a profile update request, identifies which field needs updating. See enum values below.

updateFieldRequest Enum Values:

ValueDescription
EmailRequest to update the customer's email address
PhoneRequest to update the customer's phone number
AddressRequest to update the customer's address
PrimAuthEmailUpdate primary authorized user email
PrimAuthPhoneUpdate primary authorized user phone
PrimAuthAddressUpdate primary authorized user address
Owner1EmailOwner4EmailUpdate email for business owner 1–4
Owner1PhoneOwner4PhoneUpdate phone for business owner 1–4
Owner1AddressOwner4AddressUpdate address for business owner 1–4
EmployerUpdate employer information
EmployerIdentificationNumberUpdate employer identification number (EIN)
BusinessStartDateUpdate the business start date
DateOfBirthUpdate date of birth
SsnUpdate Social Security Number
GivenNameUpdate first name
MiddleNameUpdate middle name
FamilyNameUpdate last name
DoingBusinessAsNameUpdate DBA name
LegalBusinessNameUpdate legal business name
LoanApproveTicket related to a loan approval action
[
  {
    "ticketId": 1042,
    "createdDate": "2026-06-01T10:23:45Z",
    "status": "New",
    "text": "I need to update my business address on file.",
    "topic": "Profile Update",
    "topicId": 3,
    "userProfileId": 80021,
    "parentTicketId": null,
    "updateFieldRequest": "Address"
  },
  {
    "ticketId": 1058,
    "createdDate": "2026-06-05T14:11:00Z",
    "status": "New",
    "text": "Please verify my loan application documents.",
    "topic": "Loan",
    "topicId": 7,
    "userProfileId": 80035,
    "parentTicketId": null,
    "updateFieldRequest": "LoanApprove"
  }
]

Error Codes

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

Common Mistakes

  • Calling this endpoint without a valid Bearer token will result in a 401 error; ensure the token has not expired (lifetime is 10 minutes) and refresh via POST /api/auth/refresh when needed.
  • This endpoint returns only new (unresolved/open) tickets — it does not return resolved, closed, or archived tickets; use a separate endpoint to retrieve the full ticket history.
  • The updateFieldRequest field is an enum and may be absent or null for tickets that are not profile-update requests; always handle null gracefully in your client code.
  • parentTicketId is nullable — a null value means the ticket is a top-level ticket, not a sub-ticket or follow-up.

Related Endpoints

  • GET /api/tickets — Retrieve all tickets (all statuses) for the authenticated client
  • 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 or resolve an existing ticket

Example

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