Get Authorized User Access Rights
This endpoint allows the main account owner of a business customer to retrieve the access rights and permissions of a specific authorized user (subprofile). It returns a structured set of boolean flags indicating which actions and features the authorized user is permitted to perform. Use this endpoint to audit, verify, and manage access control across your business account.
Endpoint
GET /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 the main account owner needs to verify or audit the permissions assigned to a specific authorized user. This is useful for compliance reviews, security audits, and ensuring that each subprofile only holds permissions appropriate to their role. It is especially relevant before making updates to an authorized user's access level.
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | integer (int32) | Yes | The unique identifier of the authorized user (subprofile) whose access rights are being retrieved. |
Response
200 OK
| Field | Type | Description |
|---|---|---|
| mainAccess | boolean | Indicates whether the authorized user has main (full) access to the account. |
| openBankingCard | boolean | Indicates whether the authorized user can open (create) a banking card. |
| openFinancialAccount | boolean | Indicates whether the authorized user can open a new financial account. |
| makeTransfers | boolean | Indicates whether the authorized user is permitted to initiate transfers. |
| viewAllCardsAndFinancialAccounts | boolean | Indicates whether the authorized user can view all cards and financial accounts linked to the business. |
{
"mainAccess": false,
"openBankingCard": true,
"openFinancialAccount": false,
"makeTransfers": true,
"viewAllCardsAndFinancialAccounts": true
}Error Codes
| Code | When it happens |
|---|---|
| 400 | The provided id is not a valid integer or is malformed. |
| 401 | Token missing, expired, or invalid. |
| 403 | The caller is not the main account owner or does not have permission to view this subprofile's access rights. |
| 404 | No authorized user found with the specified id. |
| 500 | Internal server error. |
Common Mistakes
- Passing a non-integer or string value for
id— the parameter must be a validint32. - Calling this endpoint as an authorized user (subprofile) rather than the main account owner; only the main owner is permitted to retrieve access rights.
- Forgetting that this endpoint is scoped to business customers only — authorized users (subprofiles) are not available on personal accounts.
- Using an expired Bearer token; tokens have a 10-minute lifetime and must be refreshed before expiry.
Related Endpoints
GET /api/usersManagement— List all authorized users linked to the business account.POST /api/usersManagement— Create a new authorized user (subprofile) for a business account.PUT /api/usersManagement/{id}/accessRights— Update the access rights of an authorized user.DELETE /api/usersManagement/{id}— Remove an authorized user from the business account.
Example
curl -X GET https://api.banking.netevia.dev/api/usersManagement/42/accessRights \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"