Receive Login(s) to Email
This endpoint allows users to recover their forgotten login credentials by submitting their registered email address. If the email is associated with an account, the login information (such as username or nickname) is sent to that address. No authentication is required to call this endpoint.
Endpoint
POST /v2/forgotLogin
Authentication
No authentication is required for this endpoint. It is publicly accessible to support account recovery flows.
When to use
Use this endpoint when a user has forgotten their login nickname but still has access to their registered email address. It is part of the account recovery flow and should be called before directing users to password reset or re-authentication steps. This endpoint does not expose passwords — only non-sensitive login identifiers are sent via email.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| string | Yes | The registered email address associated with the user's account. Must be a valid, non-empty string. |
{
"email": "[email protected]"
}Response
200 OK
| Field | Type | Description |
|---|---|---|
| restoreState | string (nullable) | Indicates the outcome state of the restore operation (e.g., email sent, not found). |
| errors | array of strings (nullable) | List of error messages if the operation failed or the email was not found. |
| success | string (nullable) | A success message confirming the login recovery email was sent. |
{
"restoreState": "EmailSent",
"errors": null,
"success": "Login credentials have been sent to the registered email address."
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing or invalid email field (e.g., empty string or malformed email format) |
| 404 | No account found associated with the provided email address |
| 500 | Internal server error |
Common Mistakes
- Submitting an empty or missing
emailfield — this will trigger a 400 validation error sinceemailhasminLength: 1and is required. - Providing an email address not registered in the system — the API will return an error response rather than sending an email.
- Expecting password information in the recovery email — this endpoint only sends non-sensitive login identifiers such as username or nickname, never passwords.
- Adding an
Authorizationheader — this endpoint does not require authentication; however, including a token will not cause an error.
Related Endpoints
POST /api/auth/v2— Authenticate with username, password, and partnerId to obtain a Bearer tokenPOST /api/auth/refresh— Refresh an existing Bearer token before it expires
Example
curl -X POST https://api.banking.netevia.dev/v2/forgotLogin \
-H "Content-Type: application/json" \
-d '{
"email": "[email protected]"
}'