GuidesRecipesAPI ReferenceChangelog
Changelog
Back to All
Improved

April 2026 Update

13 days ago by ReadMe API

🌷 April 2026 Update: New to_username signals in the Email and Phone APIs surface the most likely username linked to an email or phone number, combining data breaches with reference sources and a confidence rating to weigh in your fraud decisions.

New Signal: Email & Phone to Username

The Email and Phone enrichments now return the most likely username associated with the input, combining different data sources. Each result comes with a confidence level so you can prioritise stronger matches.

🔍 Key Features

  • 👤 New to_username signal: returns the most likely username tied to the email or phone, with confidence baked in (e.g. {"value":"john_doe","confidence":"HIGH"})
  • ✅ Auxiliary signals: has_to_username (boolean) and has_to_username_confidence (HIGH / MEDIUM / LOW) make it easy to filter and prioritise cases at a glance
  • 🔎 Usernames in the data breach card: on the Email and Phone profile pages, the data breach card now lists the usernames linked to each breach, with a count when the same username appears multiple times

Email

📊 **Example Output **

{
  "email_to_username": "{\"value\":\"john_doe\",\"confidence\":\"HIGH\"}",
  "email_has_to_username": true,
  "email_has_to_username_confidence": "HIGH"
}
  • email_to_username (string): JSON string with the most likely username extracted across all sources, plus its confidence level.
  • email_has_to_username (boolean): true when a username match was found, false when sources were available but no match was returned, null when no sources were available.
  • email_has_to_username_confidence (string): Confidence of the extracted username: HIGH, MEDIUM, or LOW.

Phone

📊 **Example Output **

{
  "phone_to_username": "{\"value\":\"john_doe\",\"confidence\":\"HIGH\"}",
  "phone_has_to_username": true,
  "phone_has_to_username_confidence": "HIGH"
}
  • phone_to_username (string): JSON string with the most likely username extracted across all sources, plus its confidence level.
  • phone_has_to_username (boolean): true when a username match was found, false when sources were available but no match was returned, null when no sources were available.
  • phone_has_to_username_confidence (string): Confidence of the extracted username: HIGH, MEDIUM, or LOW.

[image: Email and Phone profile pages, Data Breaches card showing the username list, and Summary card showing the new to_username field with its confidence]


Session Analytics

Session now has its own dedicated Analytics dashboard, giving you a complete view of your session traffic, the threats behind it, and the signals driving every score, with all metrics filterable by time period.

🔍 Key Features

  • 📊 Traffic at a glance: total and average daily sessions, plus daily session trends across your selected period
  • 🛡️ Threat visibility: see how many malicious sessions were prevented or detected, how sessions break down by risk level, and the top trust and risk signals driving scores
  • 🤖 Bot & manipulation detection: separate human from automated/bot traffic and surface headless browsers, IP masking (VPN), device spoofing, and AI agents
  • 🌍 Device, network & geography breakdown: analyse sessions by device type, operating system, browser, connection type, ISP, and country

Improved Proxy Detection

We've upgraded our proxy detection engine to more accurately identify when an IP address is hiding behind a proxy, including hard-to-spot datacenter proxies that are often used to mask fraudulent activity.

🔍 Key Features

  • 🛡️ More reliable proxy detection: higher precision in spotting proxied IPs, including datacenter proxies commonly used to evade controls
  • 🎯 Stronger fraud prevention: more accurate IP signals feed directly into better risk decisions
  • 🔄 No integration changes: your existing IP checks keep working exactly as before, just with sharper detection

📚 Resources