Manage Authorized user access

Manage Authorized User Access

This endpoint allows the main business account owner to manage access rights and permissions for authorized users (subprofiles) associated with their account. By submitting a POST request, the owner can grant, modify, or revoke specific capabilities such as opening cards, making transfers, or viewing financial accounts. This helps maintain security and ensures authorized users have only the privileges appropriate to their role.

Endpoint

POST /api/usersManagement/{id}/accessRights

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 business account owner needs to adjust the permissions of an authorized user — for example, when an employee's role changes, when temporary access must be revoked, or when a new subprofile needs a specific set of capabilities assigned. This endpoint is applicable only to business customers who have subprofiles (authorized users) linked to their account.

Path Parameters

ParameterTypeRequiredDescription
idinteger (int32)YesThe unique identifier of the authorized user (subprofile) whose access rights are being managed.

Request Body

FieldTypeRequiredDescription
mainAccessbooleanNoGrants or revokes full main-level access for the authorized user.
openBankingCardbooleanNoAllows or disallows the authorized user to open (request) new banking cards.
openFinancialAccountbooleanNoAllows or disallows the authorized user to open new financial accounts.
makeTransfersbooleanNoAllows or disallows the authorized user to initiate fund transfers.
viewAllCardsAndFinancialAccountsbooleanNoAllows or disallows the authorized user to view all cards and financial accounts on the business profile.
{
  "mainAccess": false,
  "openBankingCard": true,
  "openFinancialAccount": false,
  "makeTransfers": true,
  "viewAllCardsAndFinancialAccounts": true
}

Response

200 OK

FieldTypeDescription
mainAccessbooleanReflects the updated main access setting for the authorized user.
openBankingCardbooleanReflects the updated permission to open banking cards.
openFinancialAccountbooleanReflects the updated permission to open financial accounts.
makeTransfersbooleanReflects the updated permission to make transfers.
viewAllCardsAndFinancialAccountsbooleanReflects the updated permission to view all cards and financial accounts.
{
  "mainAccess": false,
  "openBankingCard": true,
  "openFinancialAccount": false,
  "makeTransfers": true,
  "viewAllCardsAndFinancialAccounts": true
}

Error Codes

CodeWhen it happens
400Missing required fields, invalid permission values, or the authorized user ID is not associated with the authenticated business account.
401Token missing, expired, or invalid.
403Caller is not the main account owner or does not have permission to manage subprofile access rights.
404Authorized user with the specified ID was not found.
500Internal server error.

Common Mistakes

  • Sending an id that belongs to a different business account — each authorized user ID is scoped to the business profile that created it.
  • Omitting all fields from the request body — while no individual field is strictly required, sending an empty object will have no effect; include at least one field to make a meaningful update.
  • Calling this endpoint as a personal customer — authorized users (subprofiles) exist only for business accounts; personal accounts do not support this feature.
  • Using an expired Bearer token — tokens last 10 minutes; refresh before making requests if the token may have timed out.

Related Endpoints

  • POST /api/usersManagement — Create a new authorized user (subprofile) for a business account.
  • GET /api/usersManagement/{id} — Retrieve details and current access rights for a specific authorized user.
  • DELETE /api/usersManagement/{id} — Remove an authorized user from a business account.
  • POST /api/auth/v2 — Obtain a Bearer token for authentication.
  • POST /api/auth/refresh — Refresh an existing Bearer token.

Example

curl -X POST https://api.banking.netevia.dev/api/usersManagement/4821/accessRights \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "mainAccess": false,
    "openBankingCard": true,
    "openFinancialAccount": false,
    "makeTransfers": true,
    "viewAllCardsAndFinancialAccounts": true
  }'
Path Params
int32
required
Body Params
boolean
boolean
boolean
boolean
boolean
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
string
enum
Defaults to application/json

Generated from available request 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