DATE:
AUTHOR:
Christopher O'Neill
Fraud Integration

2026.01.16 | Email Risk beta & update to Event Log Streaming

DATE:
AUTHOR: Christopher O'Neill

Email Risk API in beta

Email addresses reveal information that is useful for fraud detection. For example, fraudsters often use disposable email addresses or “tumbling” to sign up for multiple accounts and exploit trials or giveaways. 

With Stytch Email Risk, you get high-confidence email and domain signals with recommended actions, so that you can block bad signups at the front door.

How it works

  • Call the Check Email Risk API with the email address you want to check: https://stytch.com/docs/fraud/api/check-email-risk 

  • Stytch will return a recommended action ALLOW, BLOCK, or CHALLENGE), a risk score, and detailed information about the email address and domain

Getting started

To get access to the beta, reach out to us at fraud-team@stytch.com or via Slack to get started.

Event Log Streaming event changes

We’ll be making two changes to our Event Log Streaming (ELS) feature starting on 2026-01-30.

Removing Start events

Today, our ELS feature logs every API event twice; once when it starts, a Start event, and again when it finishes, as either a Success or an Error event. This means API events are effectively duplicated and your logging destination receives twice as many events as necessary, which can drive up your storage and processing costs.

On 2026-01-30 we’ll be removing all Start events from our log stream. This will halve the number of incoming events to your destination.

If you currently use Start events in your alerting or monitoring, we recommend moving to the corresponding Success or Error events instead.

Adding new frontend SDK events

On 2026-01-30 we’ll also be adding in a new set of events specific to our frontend SDKs.

Previously we did not include Error events coming from our frontend SDKs but we’ll now begin sending those Error events to your ELS destination.

If you’re using one of our frontend SDKs, you should expect a small increase in volume for any errors that they generate.

Questions about this change

If you have any questions about this change, please reach out to support@stytch.com or in our developer Slack and we can help you out.

Where to find us

Stytch developer Slack

Join the discussion, ask questions, and suggest new features in our official Slack!

Get support

Check out the Stytch Forum or email us at support@stytch.com

Powered by LaunchNotes