Allowed Modules

This endpoint returns the full list of platform modules that the authenticated partner is permitted to use. It is used to determine which features and capabilities are available within the partner's integration context. Use this endpoint during application initialization or when building dynamic navigation and permission-gating logic.

Endpoint

GET /settings/allowedModules

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 when your application starts up or when you need to determine which features the current partner account has access to. It is useful for dynamically enabling or disabling UI sections, API routes, or business logic paths based on module availability. Partners with different service tiers or configurations may have different sets of allowed modules.

Response

200 OK

Returns the list of modules allowed for the authenticated partner. The exact structure of the response reflects the partner's enabled feature set.

{
  "modules": [
    "Cards",
    "Transfers",
    "Rewards",
    "EWA",
    "SubProfiles",
    "ExternalAccounts"
  ]
}

Error Codes

Code	When it happens
401	Token missing, expired, or invalid
403	Insufficient permissions to access settings
500	Internal server error

Common Mistakes

Calling this endpoint with an expired token — tokens expire after 10 minutes; refresh using POST /api/auth/refresh before making requests.
Assuming all modules are available by default — module availability is determined by your partner configuration; always check this endpoint before relying on a specific feature.

Related Endpoints

POST /api/auth/v2 — Obtain a Bearer token for authentication
POST /api/auth/refresh — Refresh an existing Bearer token

Example

curl -X GET https://api.banking.netevia.dev/settings/allowedModules \
  -H "Authorization: Bearer YOUR_TOKEN"