---
title: Login
slug: legacy-fraud-apis/login
createdAt: 2026-03-11T19:27:18.364Z
---

::::ExpandableHeading
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose: **Login event overview and guidance on when to send the event. 

**Audience:** Developers implementing authentication flows. 

**Applies to: **Account Protection and Gaming integrations evaluating user login attempts. 

**Does not apply to: **Account creation, account updates, or non-authentication events.
:::
::::

The `login` call is intended to inform Accertify when a user attempts to log in on your website.

### Timing

The API call should come to the Interceptas Platform:

- After a user attempts to log in to your website.
- After you retrieve their IP and User Agent.
- Before you log them into your website.

### Flow

![Login flow diagram - Gaming](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/Fp6q89XMukCRgyO9gZJ6G-20260318-154722.png "Login flow - Gaming")

1. User navigates to the Client's website and attempts to login.
2. Client validates the credentials to determine if this login would have succeeded or failed.
3. Client pulls relevant account information, IP Address, User Agent, and so forth.
4. Client's backend server calls Accertify whether the credentials were successful or failed.
5. Accertify runs machine learning and consolidates data for response and returns to Client.
6. Client takes action and processes `login` attempt.



***

**See also**:

::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem
[Login Fields](docId:60jPlhTJTFaj5A3VsypM6)
:::
::::