Allows a partner to change a customer's login credentials without requiring OTP confirmation from Netevia.
Change User Login (Without OTP)
This endpoint allows a partner to update a customer's login (username, email, or phone number used for authentication) without triggering an OTP (One-Time Password) confirmation from Netevia. Partners are responsible for applying their own security validations — such as multi-factor authentication, internal approval workflows, or manual verification — before calling this endpoint. The change takes effect immediately upon a successful response.
Endpoint
POST /api/Partners/users/changeLogin
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint when your platform manages its own login-change security flow and does not need Netevia to send an OTP to the customer. This is appropriate for partners who have implemented custom identity verification steps (such as biometric confirmation or an internal approval process) and want to update the customer's login credential as the final step. It is not suitable for self-service customer-initiated flows where Netevia's OTP verification is the desired security gate.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| userId | integer (int32) | Yes | The unique identifier of the customer whose login is being changed. |
| login | string | Yes | The new login value (e.g., username, email, or phone number). Must be between 6 and 14 characters. |
{
"userId": 1048293,
"login": "[email protected]"
}Response
200 OK
A 200 OK response indicates the login was successfully updated. The response body is empty on success.
{}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields (userId or login), or login length is outside the 6–14 character limit |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to change login for the specified user |
| 404 | No customer found with the provided userId |
| 500 | Internal server error |
Common Mistakes
- Providing a
loginvalue shorter than 6 or longer than 14 characters — the schema enforcesminLength: 6andmaxLength: 14, and the request will fail validation. - Using a string for
userIdinstead of an integer —userIdmust be a 32-bit integer, not a quoted string. - Calling this endpoint without first performing partner-side identity verification — this endpoint bypasses Netevia OTP, so it is the partner's responsibility to confirm the change is authorized before calling it.
Related Endpoints
POST /api/Partners/users/changePassword— Change a customer's password on behalf of a partner.POST /api/auth/v2— Obtain a Bearer token for authentication.POST /api/auth/refresh— Refresh an existing Bearer token before expiry.
Example
curl -X POST https://api.banking.netevia.dev/api/Partners/users/changeLogin \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"userId": 1048293,
"login": "[email protected]"
}'Success