Update Requests

This endpoint returns a map of active field update requests associated with open tickets. Each key in the response represents a field name or request category, and its value indicates the count of pending update requests for that field. Use this endpoint to monitor and manage outstanding field change requests in the ticketing system.

Endpoint

GET /api/tickets/activeUpdateFieldRequests

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 you need to audit or track pending field change requests on active tickets. It is particularly useful for support and compliance workflows where field-level update requests must be reviewed before processing. Partners can poll this endpoint to ensure all pending ticket field updates are addressed in a timely manner.

Response

200 OK

The response is a dynamic object (map) where each key is a field name or request identifier and each value is an integer representing the count of active update requests for that field.

{
  "firstName": 3,
  "lastName": 1,
  "address": 5,
  "phoneNumber": 2
}

Error Codes

Common Mistakes

• Expecting a fixed schema: the response object is dynamic and its keys depend on which fields currently have active update requests; always iterate over the returned keys rather than accessing fixed field names.
• Treating a zero-value or empty response as an error: an empty object {} is a valid response indicating no active field update requests are currently pending.

Related Endpoints

• GET /api/tickets — Retrieve a list of all tickets
• GET /api/tickets/{ticketId} — Retrieve details for a specific ticket

Example

curl -X GET https://api.banking.netevia.dev/api/tickets/activeUpdateFieldRequests \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Accept: application/json"