Input
Email address
Send one email per request. Add policy_key when a flow needs a named policy.
Validate email and domain quality, score risk, and return allow, block, or review decisions before weak records enter your product or CRM.
Decision
Allow
87
Score /100
Recommended action
Allow and send or proceed
Response summary
{
"success": true,
"data": {
"policy_key": "signup",
"decision": "allow",
"reason_code": "CLASSIFICATION_VALID",
"decision_message": "Email passed all validation checks",
"decision_reasons": [
"Valid email with high quality score"
],
"score": 87,
"checks": [
{
"name": "mx_record",
"status": "passed",
"message": "Domain accepts mail."
}
]
},
"usage": {
"remaining": 249,
"limit": 250
}
}
Input
Send one email per request. Add policy_key when a flow needs a named policy.
Signals
Syntax, MX records, disposable providers, role accounts, catch-all, reputation, risk score, and more.
Decision
Return score, reason code, checks, usage, and an allow, review, or block decision.
Best for
Signup protection, CRM intake, form validation, and workflow quality gates.
Multiple checks combined into one clear decision.
| Signal | What it checks | Why it matters |
|---|---|---|
| Syntax and format | RFC-compliant syntax and format rules. | Catches invalid addresses early. |
| Domain and MX | Domain existence and mail server records. | Verifies the domain can receive email. |
| Disposable provider | Disposable or temporary email providers. | Blocks high-risk, throwaway emails. |
| Free email provider | Gmail, Yahoo, Outlook, and other free providers. | Identify consumer versus business emails. |
| Role account | Generic role addresses such as info, admin, or sales. | Lower deliverability and engagement risk. |
| Catch-all detection | Domains where every address appears possible. | Higher bounce and false-positive risk. |
| Risk scoring | 0-100 score based on syntax, mail-server status where available, disposable, role, catch-all, and domain signals. | Single number to prioritize and act. |
| Reason codes | Explainable reasons for the decision. | Transparent, auditable, and actionable. |
| Policy rules | Customizable thresholds for allow, review, and block. | Adapt to your risk appetite. |
| Review queue | Surface uncertain cases for manual review. | Reduce false positives and protect growth. |
Soryxa provides risk scoring based on syntax, mail-server status where available, disposable, role, catch-all, and domain signals.
Validation signals are combined into a 0-100 score for allow, block, or review decisions.
Mail-server and mailbox signals are used where available and safe to evaluate.
Simple API. Clear responses. Actionable decisions.
POST /api/v1/validate
Authorization: Bearer SORYXA_API_KEY
Content-Type: application/json
{
"email": "[email protected]",
"policy_key": "signup"
}
{
"success": true,
"data": {
"policy_key": "signup",
"decision": "allow",
"reason_code": "CLASSIFICATION_VALID",
"decision_message": "Email passed all validation checks",
"decision_reasons": [
"Valid email with high quality score"
],
"checks": [
{
"name": "mx_record",
"status": "passed",
"message": "Domain accepts mail."
}
],
"score": 87
},
"usage": {
"remaining": 249,
"limit": 250
}
}
Shortened example. View the full response fields.
| Decision | Risk score | When to use |
|---|---|---|
| Allow | 80-100 | High confidence emails. Proceed and send. |
| Review | 50-79 | Uncertain or medium risk. Review before proceeding. |
| Block | 0-49 | High risk or invalid. Do not accept. |
| BLOCK_DISPOSABLE | Policy code | Disposable email blocked by team rules. |
Many email validation APIs return fields. Soryxa returns a decision your product can act on: allow, block, or review. Teams can configure rules, thresholds, and review behavior without hard-coding every validation policy into signup logic.
Methodology and sources
Soryxa claims are tied to the public validation contract, reason-code model, signup-risk benchmark, and documented review behavior. The product returns policy decisions for submitted addresses; it is not an email-finding or contact-discovery product.
Publisher: Elvesora. Reviewed by Elvesora product team. Last updated July 6, 2026.
Review benchmark scope, evidence limits, and validation-risk definitions.
Inspect request fields, response fields, rollout data, and correlation headers.
Map allow, block, and review decisions to explainable reason codes.
Plan validation volume, credits, and upgrade paths before rollout.
Preview the decision model before wiring validation into a live signup flow.
Connect validation decisions to send-risk and reputation-protection workflows.
Collect email during signup, checkout, or CRM intake.
Soryxa API evaluates email and domain quality.
Allow, review, or block based on risk and rules.
Proceed, queue for review, or show a message.
Store decisions, reasons, and signals for analysis.
Scoped processing. You stay in control.
Hosted on DigitalOcean infrastructure covered by DigitalOcean SOC 2 Type II and SOC 3 Type II reports. Soryxa applies application-level access controls, encryption, and retention practices on top of that infrastructure.
We process only what is required to deliver a decision.
Encryption in transit and at rest. Hardened infrastructure.
Role-based access and strict controls around API keys and data.
Keep data only as needed and export or delete when required.
Privacy request support helps teams export or delete personal data when required.
Stop fake signups, reduce bounces, and protect deliverability.
Use email validation at intake and before send-heavy workflows to protect onboarding quality and sender reputation.
Common implementation questions for teams adding Soryxa to signup, CRM, and deliverability workflows.
Soryxa checks email syntax, MX records, mail-server status where available, disposable patterns, role-account patterns, catch-all indicators, domain signals, and risk indicators so teams can allow, block, or review addresses before they enter signup and lifecycle workflows.
Yes. Soryxa is positioned for real-time API validation at signup, before CRM syncs, and before send-heavy workflows where bad addresses can hurt deliverability.
Yes. Soryxa is a web and API product for teams that need email validation and email verification results inside product, CRM, and data-quality workflows.
These posts support signup protection, deliverability planning, and email quality workflows.
Compare Soryxa's official PHP and Laravel SDKs with Mailgun, ZeroBounce, Abstract API, and NeverBounce, including package requirements, silent-mode behavior, decision handling, and when another email validation API may fit better.
Sora
Inconsistent email validation leads to fragmented data and misaligned workflows. Learn why shared validation rules are essential for reliable systems.
Sora
A practical guide to designing email validation rules for B2B workflows. Learn how clear allow, review, and block decisions improve data quality and system consistency.
Sora