Get Banking API Error Codes

This endpoint returns the full enumeration of business error codes defined within the Netevia Banking API. Each entry includes a numeric code and a human-readable description, making it easy to map error responses from other endpoints to their meaning. Use this reference to build robust error-handling logic in your integration.

Endpoint

GET /api/enums/bankingErrors

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

Call this endpoint during integration setup to build a local mapping of all possible Banking API error codes to their descriptions. It is also useful for displaying meaningful error messages to end users when other API calls return business error responses. Refreshing this list periodically ensures your integration stays current with any newly added error codes.

Response

200 OK

Returns an array of business error objects.

[
  {
    "code": 1001,
    "description": "Customer profile not found"
  },
  {
    "code": 1002,
    "description": "Insufficient funds"
  },
  {
    "code": 1003,
    "description": "Account is inactive or closed"
  },
  {
    "code": 1004,
    "description": "Transaction limit exceeded"
  },
  {
    "code": 1005,
    "description": "Invalid card status for requested operation"
  }
]

Error Codes

Common Mistakes

• Hardcoding error code meanings in your application without calling this endpoint — the list may grow as the platform evolves, so always fetch it dynamically or refresh it regularly.
• Assuming the description field is always present — it is nullable and may be null for some entries; always guard against null values before displaying to users.
• Calling this endpoint on every individual API request — cache the result locally and refresh it on a scheduled basis (e.g., daily) rather than fetching it per transaction.

Related Endpoints

• GET /api/enums/cardStatuses — Retrieve all possible card status values
• GET /api/enums/transactionTypes — Retrieve all transaction type enumerations
• POST /api/auth/v2 — Obtain a Bearer token for authentication

Example

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