---
title: Verification
slug: public-apis/verification
createdAt: 2026-03-11T19:11:07.522Z
---

::::ExpandableHeading
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose:&#x20;**&#x56;erification event overview and guidance on when to send the event.&#x20;

**Audience:** Developers implementing step‑up or identity verification flows.&#x20;

**Applies to:&#x20;**&#x41;ccount Protection integrations evaluating verification challenges and successful verification outcomes.&#x20;

**Does not apply to:&#x20;**&#x50;rimary authentication events, account creation, or financial transactions.
:::
::::

The `verification` call is intended to inform us when a user is verified on your website via a second method such as text or email. It is meant for two-factor authentication on an SMS or email notification, or when you verify email on sign-up.

### Timing

The API call should come to the Interceptas Platform:

- After a user passes a two-factor authentication.
- After they pass error handling, and you retrieve their account details, IP Address, and User Agent.
- Before you send the result of their request.

### Flow

![Verification flow diagram](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/ZNX3jUVIBir99rttgYpjX-20260318-154723.jpg "Verification flow")

1. User navigates to your website and completes a 2FA action.
2. User passes the 2FA action.
3. Client retrieves account information, IP, and user agent.
4. Client calls Accertify API.



***

**See also**:

::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem{headerType="IMAGE" headerImage="https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/4VRPIgGNjk81XwCl3Q2ea-20260326-200545.png"}
[Verification Fields](docId\:RDPe3e4Uo_Q9SpYPN0Dpq)
:::
::::

