Verify Single Email
Verify a single email address in real-time. Returns status, substatus, and enrichment data immediately. Costs 0.2 credits; cached results are free for 24 hours.
Use this endpoint to verify a single email address in real-time. OrbiSearch checks DNS records, MX records, and the target mail server to determine whether the mailbox exists and is accepting mail. The response includes aDocumentation Index
Fetch the complete documentation index at: https://orbisearch.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
status, a detailed substatus, a plain-English explanation, domain-level signals (mx_record, is_domain_catch_all, is_secure_email_gateway), and enrichment flags such as is_disposable and is_role_account.
See the response schema for the meaning of each status and substatus value.
Caching
Results are cached for 24 hours. If you verify the same email address within that window, the result is returned immediately at no credit cost. The response format is identical whether the result is fresh or cached.Rate limits
This endpoint is rate-limited to 20 requests per second per API key. Exceeding this limit returns a429 Too Many Requests response. See errors for how to handle rate limit responses.Authorizations
API key for authentication
Query Parameters
Email address to verify.
320"jane.doe@acme.com"
Timeout in seconds (3-90).
3 <= x <= 9070
Response
Successful Response
Verification result for a single email address.
The email address that was verified.
"test@example.com"
Overall verification status: safe (deliverable), risky (uncertain), invalid (undeliverable), unknown (verification failed).
safe, risky, invalid, unknown ^(safe|risky|invalid|unknown)$"risky"
Plain-English explanation of the verification result.
"Risky to email. The mailbox may or may not exist, as the domain accepts all mail. Send with caution."
Email service provider (Google Workspace, Gmail, Microsoft Outlook, etc.).
"Google Workspace"
Specific reason for the status (e.g., catch_all, disposable, role_account, invalid_syntax).
"catch_all"
The main mail server the domain uses to receive email. Null if the domain has no mail server configured — when that happens, substatus will be no_mx_records.
"aspmx.l.google.com"
True if the domain accepts mail for any username (catch-all). Null if we could not determine whether the domain is catch-all.
false
True if the domain is protected by a secure email gateway — Proofpoint, Mimecast, Barracuda, or Trend Micro.
false
True if this is a temporary/disposable email service, false if not, null if unknown.
false
True if this is a generic role-based email (info@, support@, etc.), false if not, null if unknown.
true
True if this is from a free email provider (gmail.com, yahoo.com, etc.), false if not, null if unknown.
false
How confident we are in the result, on a 0–100 scale. You can control yield of valid emails vs potential bounce rate by filtering safe/deliverable emails on this field.
0 <= x <= 10099