OhBounce.ai API
Stop losing revenue to undeliverable emails. OhBounce.ai combines real-time SMTP probing, AI-powered risk scoring, and a constantly updated threat database to tell you exactly which emails are safe to send to — before you press send.
Powered by AI
Traditional validators check syntax and MX records. OhBounce.ai goes further. Our models are trained on billions of validation signals to predict deliverability even for addresses that would fool a basic DNS check:
Catch-all detection — Domains that silently accept every email are flagged, so you don't mistake acceptance for validity.
Disposable & throwaway detection — Thousands of known temporary-inbox providers and newly registered domains are blocked in real time.
Spam trap identification — Honey-pot and recycled spam trap addresses are identified to protect your sender reputation.
Name & location inference — For real addresses our models return first name, last name, and estimated country — ready to use in personalisation.
Domain age scoring — Newly registered domains carry higher risk. We surface domain age so you can tune your own acceptance threshold.
Common Use Cases
Sign-up forms
Reject invalid emails at registration before they enter your database.
CRM hygiene
Run bulk jobs to clean existing lists and remove hard bounces proactively.
Email campaigns
Scrub your audience before a send to protect deliverability and sender score.
Lead enrichment
Append first name, last name, and country to inbound leads automatically.
API Overview
/api/v1/validateValidate a single email — synchronous, 1 credit.
/api/v1/validate/bulkQueue up to 10,000 emails — async, 1 credit each.
/api/v1/jobs/:idPoll status and fetch paginated results of a bulk job.
/api/v1/balanceCheck your workspace's remaining credit balance.
Base URL
All endpoints accept and return application/json.
Request Format
Send Content-Type: application/json on all POST requests. GET requests do not require a body.
Rate Limits
Requests are limited to 10 per 10 seconds per API key. Exceeding this returns a 429.
Terminology
The address exists, the mailbox is reachable, and the server confirmed it can accept mail. Safe to send.
The address does not exist or the receiving server explicitly rejected it. Do not send.
The domain is configured to accept every incoming email regardless of whether the individual mailbox exists. Deliverability is uncertain — treat with caution.
A temporary inbox from a throwaway-email service (e.g. Mailinator, Guerrilla Mail). These expire quickly and are almost never real users.
An address seeded by ISPs and blocklist operators to catch senders with poor list hygiene. A single hit can severely damage your sender reputation.
Deliverability could not be determined — usually because the server timed out, greylisted the probe, or actively blocked verification. Treat conservatively.
An address tied to a function rather than a person (info@, support@, admin@). High unsubscribe rates make these risky for marketing sends.
A DNS record that identifies the mail server responsible for accepting email for a domain. No MX record means the domain cannot receive mail.
A permanent delivery failure caused by an invalid address or non-existent domain. OhBounce.ai flags these before they reach your ESP.
The unit of usage charged per validated email. One credit is consumed per address, whether validated individually or as part of a bulk job.
Base URL
https://ohbounce.ai/api/v1