didit-email-verification

Automating email verification involves sending a configurable one-time code to a user's address and validating it to confirm ownership. This skill handles sending and checking codes with policy-based actions for breached or disposable addresses.

Yes, email verification can automatically decline risky addresses based on policy. The process detects breached, disposable, and undeliverable addresses, and can include optional fraud signals like IP and device data to enhance risk scoring.

You need an API key for authentication and the requests library to call the verification endpoints. The system supports configurable code lengths and alphanumeric options to customize the OTP generation for your security flows.

Adding fraud signals improves email verification by collecting IP, device, and user agent data during the code check. This contextual data enhances risk scoring and helps detect fraudulent onboarding attempts more accurately.

One-time codes rely on email deliverability and user access to the inbox. If an address is undeliverable or breached, the verification will fail or be declined based on your configured policy, preventing the onboarding flow from proceeding.

Use policy-based email verification during user onboarding, password resets, or security checks. It ensures users own their addresses and automatically blocks disposable or breached emails, reducing fraud before granting access.