curl -X POST https://verification.didit.me/v3/email/risk/ \
-H 'x-api-key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"email": "alice@example.com",
"country_code": "US",
"vendor_data": "lead-123",
"metadata": {"source": "signup_prescreen"}
}'from didit import Didit
# Reads DIDIT_API_KEY.
client = Didit()
result = client.email.assess_risk(
email="alice@example.com",
)
print(result)import Didit from "@didit-protocol/sdk-node";
// Reads DIDIT_API_KEY.
const didit = new Didit();
const result = await didit.email.assessRisk({
email: "alice@example.com",
});
console.log(result);ctx := context.Background()
// Reads DIDIT_API_KEY.
client := didit.NewClient()
result, err := client.Email.AssessRisk(ctx, didit.EmailAssessRiskParams{
Body: didit.EmailRiskRequest{
Email: "alice@example.com",
},
})
if err != nil {
log.Fatal(err)
}
fmt.Printf("%+v\n", result)import me.didit.Didit;
import me.didit.types.EmailRiskRequest;
// Reads DIDIT_API_KEY.
Didit client = new Didit();
var result = client.email().assessRisk(EmailRiskRequest.builder()
.email("alice@example.com")
.build());
System.out.println(result);<?php
require 'vendor/autoload.php';
use Didit\DiditClient;
// Reads DIDIT_API_KEY.
$didit = new DiditClient();
$result = $didit->email->assessRisk([
'email' => 'alice@example.com',
]);
print_r($result->toArray());require "didit"
# Reads DIDIT_API_KEY.
didit = Didit::Client.new
result = didit.email.assess_risk(email: "alice@example.com")
puts result.to_husing System;
using System.Text.Json;
using Didit;
// Reads DIDIT_API_KEY.
using var client = new DiditClient();
var result = await client.Email.AssessRiskAsync(new EmailRiskRequest
{
Email = "alice@example.com",
});
Console.WriteLine(JsonSerializer.Serialize(result));{
"request_id": "82397be9-5921-4970-a979-2d5b43e08b33",
"status": "Approved",
"email": {
"status": "Approved",
"email": "alice@example.com",
"is_breached": false,
"breaches": [],
"is_disposable": false,
"is_undeliverable": false,
"verification_attempts": 0,
"verified_at": null,
"warnings": [],
"lifecycle": [],
"matches": [],
"email_intelligence": {
"score": 4,
"deliverable": "high",
"breach_risk_level": "Low",
"breach_risk_index": 4,
"is_recent_breach": false,
"is_frequent_breached": false,
"is_disposable": false,
"is_free_domain": false,
"is_breached": false,
"no_of_breaches": 0,
"reason_codes": []
},
"enrichment": {
"score": 4,
"deliverable": "high",
"breach_risk_level": "Low",
"breach_risk_index": 4,
"is_recent_breach": false,
"is_frequent_breached": false,
"is_disposable": false,
"is_free_domain": false,
"is_breached": false,
"no_of_breaches": 0,
"reason_codes": []
}
},
"vendor_data": "lead-123",
"metadata": {
"source": "signup_prescreen"
},
"created_at": "2026-09-01T10:30:00.123456+00:00"
}Email Risk API: Deliverability & Breach Signals
Risk-score an email address without sending an OTP. Deliverability, disposable-domain, breach, and fraud signals in one server-to-server call.
curl -X POST https://verification.didit.me/v3/email/risk/ \
-H 'x-api-key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"email": "alice@example.com",
"country_code": "US",
"vendor_data": "lead-123",
"metadata": {"source": "signup_prescreen"}
}'from didit import Didit
# Reads DIDIT_API_KEY.
client = Didit()
result = client.email.assess_risk(
email="alice@example.com",
)
print(result)import Didit from "@didit-protocol/sdk-node";
// Reads DIDIT_API_KEY.
const didit = new Didit();
const result = await didit.email.assessRisk({
email: "alice@example.com",
});
console.log(result);ctx := context.Background()
// Reads DIDIT_API_KEY.
client := didit.NewClient()
result, err := client.Email.AssessRisk(ctx, didit.EmailAssessRiskParams{
Body: didit.EmailRiskRequest{
Email: "alice@example.com",
},
})
if err != nil {
log.Fatal(err)
}
fmt.Printf("%+v\n", result)import me.didit.Didit;
import me.didit.types.EmailRiskRequest;
// Reads DIDIT_API_KEY.
Didit client = new Didit();
var result = client.email().assessRisk(EmailRiskRequest.builder()
.email("alice@example.com")
.build());
System.out.println(result);<?php
require 'vendor/autoload.php';
use Didit\DiditClient;
// Reads DIDIT_API_KEY.
$didit = new DiditClient();
$result = $didit->email->assessRisk([
'email' => 'alice@example.com',
]);
print_r($result->toArray());require "didit"
# Reads DIDIT_API_KEY.
didit = Didit::Client.new
result = didit.email.assess_risk(email: "alice@example.com")
puts result.to_husing System;
using System.Text.Json;
using Didit;
// Reads DIDIT_API_KEY.
using var client = new DiditClient();
var result = await client.Email.AssessRiskAsync(new EmailRiskRequest
{
Email = "alice@example.com",
});
Console.WriteLine(JsonSerializer.Serialize(result));{
"request_id": "82397be9-5921-4970-a979-2d5b43e08b33",
"status": "Approved",
"email": {
"status": "Approved",
"email": "alice@example.com",
"is_breached": false,
"breaches": [],
"is_disposable": false,
"is_undeliverable": false,
"verification_attempts": 0,
"verified_at": null,
"warnings": [],
"lifecycle": [],
"matches": [],
"email_intelligence": {
"score": 4,
"deliverable": "high",
"breach_risk_level": "Low",
"breach_risk_index": 4,
"is_recent_breach": false,
"is_frequent_breached": false,
"is_disposable": false,
"is_free_domain": false,
"is_breached": false,
"no_of_breaches": 0,
"reason_codes": []
},
"enrichment": {
"score": 4,
"deliverable": "high",
"breach_risk_level": "Low",
"breach_risk_index": 4,
"is_recent_breach": false,
"is_frequent_breached": false,
"is_disposable": false,
"is_free_domain": false,
"is_breached": false,
"no_of_breaches": 0,
"reason_codes": []
}
},
"vendor_data": "lead-123",
"metadata": {
"source": "signup_prescreen"
},
"created_at": "2026-09-01T10:30:00.123456+00:00"
}POST /v3/email/risk/ when you need email intelligence without asking the user to enter a one-time code.
It does not send an email. It creates an API session, enriches the address, applies your email-risk rules, and returns the same normalized email block used by Email Verification in one synchronous response.
When the request is saved, Didit can also use the scored email as aggregate evidence in Networks. Network graphs may show high-risk email intelligence, breach context, and social-profile coverage on shared email signals, but they do not reveal the raw email address to other organizations.
Interpret the response
statusis the final decision for this API session. It is normallyApproved; the risk evaluation can produceIn RevieworDeclined.email.is_breached,email.is_disposable, andemail.is_undeliverableare the stable yes/no signals for application logic.email.breacheslists the most recent known breaches containing the address when coverage is available, with the breach date and the data classes exposed.email.email_intelligence.scoreuses a 0-100 risk scale where a higher number means higher risk.breach_risk_level(Low,Medium,High) andno_of_breachesare derived views.email.email_intelligence.reason_codesexplains which normalized signals contributed to the result. Values can grow over time, so do not reject unknown codes.email.email_intelligenceandemail.enrichmentare compatibility aliases with the same normalized object. New integrations can reademail.enrichment.email.matcheslists other sessions of your application where the same address was used by a different user. Use it for duplicate-account detection.request_idis the API session id. Store it withvendor_dataif you need to correlate the result with later webhooks or console activity.
email.email_intelligence and email.enrichment are best-effort fields. A completed lookup can omit both when no usable intelligence data is returned for that address, domain, or plan. Build rules on is_breached, is_disposable, and is_undeliverable first and treat missing intelligence as “unknown”, not “safe”.Social footprint add-on
Setenable_social to true to add a email_social block to the response under email: the online platforms this email address is registered on, grouped by category, with the summary counts and any profile details our data partners return.
email.email_social.profiles_registeredandemail.email_social.profiles_checkedare the headline numbers: platforms where the email address is confirmed registered, out of the platforms evaluated.email.email_social.registered_platformsandemail.email_social.not_registered_platformslist each platform with itscategoryandscope(global, orlocalfor region-specific platforms).email.email_social.categoriesgives the registered count and ratio per category, andemail.email_social.profilescarries per-platform profile details when a platform exposes them (name, photo URL, about text, privacy status, business-account flag).- Summary indexes (
digital_footprint_diversity,digital_sophistication_index,engagement_depth_index,subscription_affordability_index) are 0-10 composites. Every count can benullwhen the check returned no data for it.
profiles_registered: 0 is a real answer, not a failure: the platforms were checked and the email address was found on none of them, which is a common synthetic-identity signal. This endpoint does not act on it by itself - use email_no_social_presence_action in a workflow to turn it into a Review or Decline verdict.
The block is absent when enable_social is not set, and also when the social check could not be completed - in which case it is not billed.
Sandbox behavior
Sandbox keys validate the request and return deterministic approved data. They do not send an email, consume credits, create a session, or contribute to Networks. Withenable_social set, they also return a deterministic email_social block.
Billing
Email Risk API calls cost $0.04 at list price, less than full Email Verification would because no email is sent. A live request is billable once the lookup starts, even when some best-effort fields are unavailable. The social footprint add-on is billed separately: oneemail_social unit per request on top of the Email Risk API price, whenever the check completes. The credit check before the lookup covers both.Authorizations
Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is wrong, revoked or expired; 403 means no key was sent, the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.
Headers
Optional retry-safety key you choose for one operation, up to 255 characters (a UUID works). A request repeated with the same key, endpoint, query and body is answered with the first response, same status and same body, and runs and bills nothing a second time. The same key with another endpoint, query or body returns 409 idempotency_key_reused, and while the first request is still running, 409 idempotency_key_in_progress with Retry-After. A failed request (any 4xx or 5xx) is not stored, so you can send it again with the same key. Keys belong to your application, whether you call with an API key or an access token. See Retries and idempotency.
1 - 255Body
Response
The risk evaluation completed. Inspect status for the decision; HTTP is always 200 for completed lookups.