APIddress is an email validation API designed for developers and businesses that need to know whether an email address is real and deliverable. It provides a clear verdict by exposing the individual checks behind each decision, rather than a simple pass/fail. This transparency allows teams to set their own thresholds for blocking, flagging, or allowing addresses. Currently in pre-launch, APIddress is accepting wishlist signups that reserve an API key with 2,000 free validations per month and founding-member pricing for a year. The product serves any organization that collects or manages email addresses, from startups to enterprises, and targets teams that rely on email for user acquisition, communication, and data integrity.
The fundamental problem APIddress addresses is the high cost of undetected bad emails. Fake signups waste resources on onboarding and support; typos cause failed delivery and lost leads; disposable addresses inflate user counts and drive fraud; role-based inboxes blur ownership and compliance. Without granular checks, teams often block too aggressively or let too many risky addresses through. APIddress solves this by surfacing each risk factor — syntax errors, missing MX records, non-existent mailboxes, disposable domains, role addresses, and catch-all configurations — in a single API call. This saves engineering time, reduces bounce rates, and improves sender reputation. For email marketers, cleaner lists mean higher engagement; for product teams, deliverable contacts mean retained users.
APIddress returns six distinct verdicts per email: deliverable, risky, disposable, role-based, malformed, and no MX/typo. Each verdict is backed by the individual signals that produced it. For example, a 'deliverable' verdict means the mailbox exists and accepts mail; a 'risky' verdict indicates catch-all, role inbox, or low reputation; 'disposable' flags throwaway domains like Mailinator that are often associated with fraud and churn; 'role-based' identifies shared addresses such as info@ or support@ that have no single owner; 'malformed' catches RFC syntax violations before any request leaves the system; and 'no MX/typo' detects domains that cannot receive mail and suggests the likely fix, such as correcting 'gmial.com' to 'gmail.com'. This granularity lets users decide what to block, flag, or let through.
The same API endpoint supports both real-time validation for online forms and batch processing for existing contact databases. For real-time use, a single POST request to /api/v1/validate-email returns the verdict and its supporting signals in milliseconds. For batch jobs, users can submit large datasets and score millions of rows per hour; the service has demonstrated throughput of 22 million rows per hour. This dual capability means teams can wire up the API once and reuse it everywhere an email enters the system — from signup forms to CRM imports. The response includes not only the verdict but also details like typo suggestions, allowing developers to implement custom logic such as offering a corrected email to the user.
admin
Beyond the six core verdicts, APIddress provides extra signals that help users make informed decisions. When an email has a common domain typo, the API returns a suggested correction, reducing user frustration and preventing accidental data loss. For 'risky' verdicts, the system checks whether the domain is a catch-all, where any address at the domain might accept mail but not be individually valid. It also scores the sender reputation of domains, flagging those known for low trust. These additional insights are surfaced as part of the response, giving developers the context to implement custom logic — for example, routing risky addresses to a separate queue for manual review rather than immediately blocking them.
APIddress works by combining multiple verification layers into a single API call. When a request is made, the service first checks syntax against RFC standards. If malformed, it returns immediately without further processing, saving resources. Next, it queries the domain’s MX records to confirm the domain can receive mail. If no MX records are found, the address is marked undeliverable and a typo suggestion is offered. Then it checks if the domain belongs to a known disposable provider. After that, it performs a mailbox existence check by connecting to the mail server to confirm the inbox exists. It also determines if the address is role-based or part of a catch-all. Each check is executed in parallel where possible, and the results are combined into a JSON response listing the verdict and all supporting signals. The entire workflow is documented in the API docs and accessible via a simple RESTful interface.
Concrete use cases demonstrate APIddress’s impact. For signup and onboarding, blocking fake and mistyped emails at the form reduces fake signups by 31%, ensuring every new account is reachable from day one. For checkout and receipts, confirming the buyer’s address before payment increases receipt delivery by 4.2%, improving customer satisfaction and reducing support tickets. For list and CRM cleanup, scoring millions of existing contacts in batch and retiring addresses that quietly bounce can process 22 million rows per hour, slashing bounce rates. For sender reputation, keeping bounce rates below 0.3% helps maintain domain trust and avoid spam folders. These measurable outcomes — fewer fake accounts, higher delivery rates, cleaner lists, and better sender scores — rely on the API’s granular verdicts and reliable performance.
APIddress is built for developers and teams who manage email-based workflows: SaaS companies onboarding users, e-commerce businesses sending receipts, marketing teams running email campaigns, operations teams cleaning CRM data, and product managers reducing fraud. It integrates via a simple REST API, compatible with any language or platform that can make HTTP requests. The product is currently in pre-launch with open wishlist access. Signing up reserves an API key with 2,000 free validations each month and founding-member pricing locked for a year — no credit card required. The service is GDPR-safe and emphasizes data privacy. In summary, APIddress delivers transparent, actionable email verification that lets teams control their email quality, reduce bounces, and improve delivery, all through a single API that shows its work.
Developers integrating email verification into signup flows, checkout processes, and data pipelines. Product managers at SaaS companies looking to reduce fake signups and improve user engagement. Email marketers needing clean lists to increase deliverability and reduce bounce rates. Operations teams responsible for CRM data hygiene and batch cleaning. E-commerce businesses that rely on transactional emails for order confirmations and receipts. Any organization that collects email addresses and needs to verify their validity in real time or batch.