Mailbeam Documentation
Everything you need to integrate real-time email verification into your application.
Mailbeam is a REST API for verifying whether an email address can actually receive mail. You send one address to POST /v1/verify and get back a status, a score and the reason behind it, or you submit up to 500,000 addresses to POST /v1/verify/batch and collect the results asynchronously. Authentication is a Bearer token; there is nothing else to install.
- Base URL
- https://api.mailbeam.dev
- Current version
- /v1/ — 12 months deprecation notice
- Auth
- Authorization: Bearer mb_live_…
- Batch ceiling
- 500,000 addresses per job
Quickstart
First verification in 5 minutes.
Authentication
API keys, Bearer tokens, and key rotation.
Rate limits
Quotas, headers, and backoff strategy.
Errors
Error codes, structure, and handling.
Webhooks
Real-time event delivery and HMAC verification.
SDKsRoadmap
Official libraries for Node, Python, PHP, Ruby, Go.
Looking for the API Reference?
Full endpoint documentation with request/response schemas and interactive examples.
Go to API ReferenceMigrating from another provider?
Frequently asked questions
Is the Mailbeam API available right now?
Yes. The public API is live and open to anyone who signs up. The Free plan covers 1,000 verifications a month with no card required, and an API key is waiting in the dashboard the first time you open it.
What do I need to make my first Mailbeam API call?
An API key, sent as a Bearer token in the Authorization header, and a JSON request to an endpoint under https://api.mailbeam.dev/v1/. The quickstart walks through a single verification end to end.
How does Mailbeam version its API?
The current version is v1 and every endpoint sits under /v1/. Backwards compatibility is maintained within a version; breaking changes go into a new version, and the old one is deprecated with at least 12 months notice.
What is the difference between real-time and batch verification?
Real-time verification uses POST /v1/verify, answers one address per request and stores no address at all. Batch verification uses POST /v1/verify/batch, accepts up to 500,000 addresses per job, runs asynchronously and keeps results for 72 hours so you can collect them.
Answers checked against the API contract on .