APIddress icon

APIddress

APIddress is an email validation API for real-time and batch checks of deliverability, syntax, disposable, and risk signals to prevent bounces and fraud.

APIddress

Email validation API for real-time and batch checks

APIddress is an email validation API for checking whether an address is deliverable before it enters a signup form, CRM, or outbound workflow. The service returns a structured verdict over HTTPS and JSON, with one authenticated request per validation.

The product is designed to help teams screen malformed, disposable, risky, and undeliverable email addresses in real time or in batch. The docs show a workflow built around an API key sent in the `x-api-key` header, with a quickstart request to `POST /api/v1/validate-email` and a response that includes normalized email data, a verdict status, confidence score, reason, and detailed checks.

Core capabilities

Structured validation verdicts

Validates a single email address and returns a normalized, structured result rather than a simple yes/no answer. The response includes status, confidence, a machine-readable reason, and the canonical email form.

Signal-level checks

Breaks each result into individual signals such as syntax, domain existence, MX records, SMTP probe results, disposable status, role-based status, typo detection, and spam-trap risk. That lets teams apply their own policy on top of the raw checks.

Optional SMTP probing

Supports an optional SMTP-level probe via `check_smtp`. When enabled and a reachable MX host is available, the API can populate SMTP and catch-all signals for a deeper deliverability check.

Policy controls for role addresses

Allows role-based addresses to be handled according to your policy through `allow_role_based`. The docs note that support@ or info@ can be treated as acceptable or flagged as risky depending on the request setting.

Real-time and batch workflows

Provides synchronous and asynchronous workflows beyond single-address validation. The docs list bulk validation for 1–100 addresses, batch jobs for up to 5,000 addresses, and usage endpoints for monitoring quota.

Common uses

  • Signup and onboarding flows

    Validate email addresses at the moment of signup so accounts start with reachable inboxes and fewer obvious typos or disposable addresses.

  • Checkout and receipt delivery

    Check buyer email addresses before payment completion or order confirmation so receipts and transactional messages have a better chance of arriving.

  • List and CRM cleanup

    Score existing contact records in bulk, then filter out invalid or low-quality addresses before they affect campaign performance or CRM hygiene.

  • Email sending and reputation control

    Use validation in outbound systems to reduce bounce rates and keep sender reputation healthier by sending only to verified inboxes.

Pros and Cons

Pros

  • Returns a structured response with verdict, score, normalized email, and per-signal checks.
  • Supports both single-email validation and larger workflows such as bulk validation and batch jobs.
  • Includes optional SMTP probing for deeper deliverability checks.
  • Documents clear error envelopes, rate-limit behavior, and usage endpoints for quota management.
  • Lets teams tune behavior for role-based addresses and typo-like domains.

Cons

  • The public site content provided does not include a full pricing table or plan comparison.
  • Some deeper capabilities, such as SMTP and catch-all signals, depend on an optional probe and may return null when the probe is not run or no reachable MX host is available.

FAQ

What does APIddress do?

APIddress is an email validation API. The docs say it validates email addresses in real time and in batch, and returns a structured verdict with fields such as status, valid, score, reason, suggestion, and a checks object.

How do you start using it?

The docs show a quickstart flow with an API key delivered through a claim link, then a POST request to `https://api.apiddress.com/api/v1/validate-email` with the `x-api-key` header and a JSON body containing an `email` field.

What kinds of checks are included?

The validate-email endpoint can return syntax, domain, MX, SMTP, disposable, role-based, free-provider, catch-all, typo, and spam-trap-risk signals. The SMTP probe is optional and controlled by `check_smtp` in the request.

What does the response tell you?

The docs list `valid`, `invalid`, `risky`, `disposable`, and `unknown` as status values. The `valid` field is a convenience boolean, and the `score` ranges from 0 to 1.

Is pricing available yet?

The pricing page advertises an early-access wishlist with 2,000 free validations a month and founding-member pricing reserved for launch, but it does not show a public pricing table on the page content provided.

Quick Facts

Category
Developer Tool
Primary use
Email validation and deliverability screening
API host
https://api.apiddress.com
Authentication
API key in `x-api-key` header
Key endpoint
POST `/api/v1/validate-email`
Launch status
Launching soon / private beta