Soryxa Email Validation

Email validation API for signup decisions

Validate email and domain quality, score risk, and return allow, block, or review decisions before weak records enter your product or CRM.

Short answer: Soryxa is an email validation API and email verification API for submitted addresses. It checks syntax, domain, MX, disposable, role, catch-all, and risk signals, then returns one policy decision your workflow can use.

Get API Key View Pricing View API Try Email Validation
Policy-first decisions: allow, block, or review
Rich validation signals across syntax, domain, and risk
Easy to integrate with REST API, SDKs, and webhooks

Validation decisions

Syntax Valid
Domain (MX) Valid
Disposable provider No
Role account No
Score 87 /100
SMTP status Valid

Decision

Allow

87

Score /100

Recommended action

Allow and send or proceed

sales@catch-all-domain.com Review - 62
info@spam-domain.test Block - 15

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": "Domain MX",
        "status": "passed",
        "message": "Domain accepts mail."
      }
    ]
  },
  "usage": {
    "remaining": 249,
    "limit": 250
  }
}

Input

Email address

Send one email per request. Add policy_key as an echoed flow label; it does not select a separate ruleset.

Signals

Validation evidence

Syntax, TLD, MX records, SMTP status where available, disposable providers, role accounts, catch-all, bogus signals, and risk score.

Decision

Allow, review, or block

Return score, reason code, checks, usage, and an allow, review, or block decision.

Best for

Signup and intake quality

Signup protection, CRM intake, form validation, and workflow quality gates.

Validation Signals Behind Every Signup Decision

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.
Optional automated-client review Opt-in published policy uses visitor_headers to recognize supported versioned HTTP-client User-Agent tokens. Review the request in your own workflow without changing the email score or creating a persistent email Review Queue item.
Policy import and pattern testing Preview CSV or text allow and block artifacts, then test up to 25 emails against draft patterns. Catch recoverable import failures and unintended matches before publishing.
Review queue Surface uncertain cases for manual review. Reduce false positives and protect growth.
Policy quality feedback Tag false positives, false negatives, expected outcomes, and uncertain cases in Usage Logs or Review Queue. Build seven-day evidence before changing policy.
Agency Client Hub Create isolated client workspaces, record the agency as billing owner, view allowance, and switch among owned clients. Separate client tokens and rules while keeping workspace ownership explicit.
Needs attention dashboard Review and block changes, upstream health, and p95 or p99 tail latency. Prioritizes operational signals that need follow-up.

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.

Built for developers

Simple API. Clear responses. Actionable decisions.

Request

POST /api/v1/validate
Authorization: Bearer SORYXA_API_KEY
Content-Type: application/json

{
  "email": "user@acmecorp.com",
  "policy_key": "signup"
}

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"
    ],
    "checks": [
      {
        "name": "Domain MX",
        "status": "passed",
        "message": "Domain accepts mail."
      }
    ],
    "score": 87
  },
  "usage": {
    "remaining": 249,
    "limit": 250
  }
}

Shortened example. View the full response fields.

Default decision policy, customizable

Decision Default trigger When to use
Allow 70-100 after rules Continue when no explicit rule or invalid signal blocks the address.
Review Below 70 by default Route low-score, risky, or unavailable results to review.
Block No score band by default Block explicit list, disposable, bogus, invalid, or configured rule matches.
BLOCK_DISPOSABLE Policy code Disposable email blocked by team rules.
The default review threshold is 70. Score-only blocking is disabled until a team sets a block threshold above zero. Explicit blocking rules apply before score review; classification fallback is evaluated after score thresholds.

Soryxa is built for signup decisions, not only raw verification.

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.

Validation and verification are used together here: validation describes the full decision workflow, while verification describes checks that confirm whether a submitted address and its domain appear usable. Soryxa does not find or generate email addresses.

Validate email API Reason codes Rules and review Preview Email Validation Demo Compare alternatives Benchmark method

Methodology and sources

How we scope email validation claims

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 August 17, 2026.

Signup-risk benchmark

Review benchmark scope, evidence limits, and validation-risk definitions.

Validate email docs

Inspect request fields, response fields, rollout data, and correlation headers.

Reason codes

Map allow, block, and review decisions to explainable reason codes.

Soryxa pricing

Compare monthly plans and one-time packs of 5,000 checks for $15 USD plus applicable tax.

Validation demo preview

Preview the decision model before wiring validation into a live signup flow.

Pay-as-you-go email validation

Cover a one-time import or signup spike with prepaid checks.

Deliverability use case

Connect validation decisions to send-risk and reputation-protection workflows.

API errors

Handle auth, billing, validation, and limit errors.

Usage and credits

Plan request volume, limits, and credit behavior.

Batch validation

Upload lists, retry partial jobs, and export decisions.

Webhooks and connectors

Connect decisions to downstream systems.

How Soryxa fits your workflow

User submits form

Collect email during signup, checkout, or CRM intake.

Validate email

Soryxa API evaluates email and domain quality.

Policy decision

Allow, review, or block based on risk and rules.

Take action

Proceed, queue for review, or show a message.

Log and improve

Store decisions, reasons, and signals for analysis.

Security, privacy, and data control

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.

Data minimization

We process only what is required to deliver a decision.

Secure processing

HTTPS protects data in transit. At-rest controls depend on the configured infrastructure and storage services.

Access controls

Authenticated, team-scoped access with scoped API tokens and explicit token revocation controls.

Retention and deletion

Keep data only as needed and export or delete when required.

Privacy Request Support

Privacy request support helps teams export or delete personal data when required.

Validate emails before they impact growth

Stop fake signups, reduce bounces, and protect deliverability.

Get API Key View Pricing View API

Workflows that benefit from Soryxa

Use email validation at intake and before send-heavy workflows to protect onboarding quality and sender reputation.

Email Validation for Signups

Validate new signups before onboarding and CRM syncs begin.

Deliverability protection

Protect sender reputation by filtering risky addresses before sends start.

Frequently asked questions

Common implementation questions for teams adding Soryxa to signup, CRM, and deliverability workflows.

What does Soryxa check during email validation?

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.

Is Soryxa built for real-time signup protection?

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.

Can developers use Soryxa through an API?

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.

Read more about email validation and verification

These posts support signup protection, deliverability planning, and email quality workflows.