Get Login History Report
This endpoint returns login history records for customers within a specified date range. Each record includes identifying information for the user along with aggregated counts of successful and failed login attempts. Partners can use this data for security monitoring, auditing, and support investigations.
Endpoint
GET /Report/loginHistory
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 to audit customer login activity across a date range and identify unusual access patterns such as repeated failed login attempts. It is also useful for support workflows when a customer reports account access issues, allowing partners to confirm recent login events and detect potential unauthorized access.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| from | string (date-time) | No | Start of the date range for login history. ISO 8601 format (e.g., 2025-01-01T00:00:00Z). |
| to | string (date-time) | No | End of the date range for login history. ISO 8601 format (e.g., 2025-01-31T23:59:59Z). |
| type | integer (enum) | No | Filter by user type. See typeUser enum values: 1, 2, 3, 4, 5. |
Response
200 OK
Returns an array of login history report objects.
| Field | Type | Description |
|---|---|---|
| profileId | integer (int32) | The unique identifier of the customer profile. |
| userProfileId | integer (int32) | The unique identifier of the user profile (subprofile or main user). |
| firstName | string (nullable) | First name of the user. |
| lastName | string (nullable) | Last name of the user. |
| typeUser | integer (enum) | User type classification. Values: 1, 2, 3, 4, 5. |
| string (nullable) | Email address associated with the user account. | |
| successCount | integer (int32) | Number of successful login attempts within the queried period. |
| failCount | integer (int32) | Number of failed login attempts within the queried period. |
[
{
"profileId": 10045,
"userProfileId": 20123,
"firstName": "Jane",
"lastName": "Smith",
"typeUser": 1,
"email": "[email protected]",
"successCount": 12,
"failCount": 2
},
{
"profileId": 10046,
"userProfileId": 20124,
"firstName": "Robert",
"lastName": "Johnson",
"typeUser": 2,
"email": "[email protected]",
"successCount": 5,
"failCount": 0
}
]Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields or validation error (e.g., malformed date-time format) |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to access login history data |
| 404 | Resource not found |
| 500 | Internal server error |
Common Mistakes
- Providing
fromortodates in a non-ISO 8601 format will result in a 400 error; always use thedate-timeformat (e.g.,2025-06-01T00:00:00Z). - Omitting both
fromandtomay return a large dataset; narrow queries with a date range for performance and relevance. - Passing an invalid integer for the
typeparameter (outside of values1–5) will result in a validation error.
Related Endpoints
GET /Report/transactionHistory— Retrieve transaction history records for a customerGET /Report/accountActivity— Retrieve account activity summary for a customer
Example
curl -X GET "https://api.banking.netevia.dev/Report/loginHistory?from=2025-06-01T00%3A00%3A00Z&to=2025-06-07T23%3A59%3A59Z&type=1" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"