Login Nickname Management

This endpoint allows authenticated users to change their login nickname. The request requires both a new login nickname and the current account password to verify identity before applying the change. Once successfully updated, the new nickname takes effect immediately for subsequent logins.

Endpoint

POST /changeLogin

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 user wants to update the login nickname associated with their Netevia account. This is appropriate during onboarding flows that allow nickname personalization, or when a user requests a login name change through account settings. The system enforces uniqueness, preventing a nickname already in use by another account from being assigned.

Request Body

Field	Type	Required	Description
login	string	Yes	The new login nickname. Must be between 6 and 14 characters.
password	string	Yes	The current account password used to authorize the change.

{
  "login": "jsmith2024",
  "password": "Secur3P@ssword!"
}

Response

200 OK

A 200 response indicates the login nickname was successfully updated. The response body confirms success with no additional payload fields.

{}

Error Codes

Code	When it happens
400	Missing required fields, login nickname does not meet length requirements (6–14 characters), or the requested nickname is already taken
401	Token missing, expired, or invalid
403	Insufficient permissions
404	Resource not found
500	Internal server error

Common Mistakes

Providing a login value shorter than 6 characters or longer than 14 characters — the field has strict length constraints that will trigger a 400 error.
Omitting the password field — both login and password are required; the password is used to verify the user's identity before the change is applied.
Attempting to set a login nickname already in use by another account — the API will reject duplicate nicknames to prevent conflicts.
Using an expired Bearer token — tokens last only 10 minutes; refresh via POST /api/auth/refresh before calling this endpoint.

Related Endpoints

POST /api/auth/v2 — Obtain a Bearer token using username, password, and partnerId
POST /api/auth/refresh — Refresh an existing Bearer token before it expires

Example

curl -X POST https://api.banking.netevia.dev/changeLogin \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "login": "jsmith2024",
    "password": "Secur3P@ssword!"
  }'