Get All Localization Languages

This endpoint returns localization key-value pairs for the Netevia Banking platform across all supported languages or filtered to a specific language. Partners can use this data to render localized UI strings, error messages, and labels in their applications. An optional language query parameter narrows the response to a single locale.

Endpoint

GET /settings/localizationKeys/v2

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 refreshing the localization layer of a partner application that integrates with Netevia Banking. It is suitable for initializing a language bundle on app startup or allowing end users to switch their preferred language at runtime. Calling without a language parameter returns all supported locales at once, which is useful for offline caching or pre-loading.

Query Parameters

Response

200 OK

Returns an array of localization objects. Each object represents one language and its corresponding key-value translation map.

[
  {
    "language": "En",
    "localizationKeys": {
      "welcome_message": "Welcome to Netevia Banking",
      "login_button": "Log In",
      "transfer_success": "Your transfer was successful.",
      "error_invalid_amount": "Please enter a valid amount."
    }
  },
  {
    "language": "Es",
    "localizationKeys": {
      "welcome_message": "Bienvenido a Netevia Banking",
      "login_button": "Iniciar sesión",
      "transfer_success": "Su transferencia fue exitosa.",
      "error_invalid_amount": "Por favor ingrese un monto válido."
    }
  }
]

Error Codes

Common Mistakes

• Passing an unsupported language code (e.g., EN instead of En) — the enum values are case-sensitive; use the exact casing listed in the accepted values.
• Expecting a single object rather than an array — the response is always an array, even when filtered to one language via the language query parameter.
• Not handling null values in localizationKeys — individual translation values may be null if a key has not yet been translated for that locale.

Related Endpoints

• POST /api/auth/v2 — Obtain a Bearer token required to call this endpoint
• POST /api/auth/refresh — Refresh an expiring Bearer token

Example

curl -X GET "https://api.banking.netevia.dev/settings/localizationKeys/v2?language=En" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"