Verify addresses. Turn incoming messages into useful data. Connect sending, security and migration to the software your team already uses.
Ebook download registration
Deliverable · not disposable · ebook delivery triggered
Choose the job you want to simplify. Explore planned capabilities and discuss the integration that fits your team.
Validate addresses, understand provider context and categorise messages.
Receive structured email and prepare consistent transactional notifications.
Map invoices to fields and connect email events to reviewed actions.
Investigate suspicious messages, authentication issues and domain changes.
Plan mailbox copies, review progress and catch up before cutover.
MigrateInspect MX, SPF, DKIM and DMARC, or analyse an email header.
Open the email toolboxMaail is operated by a German company. The API specification separates transient address checks from workflows that retain operational state. Agree processing scope, metadata handling and retention during onboarding.
The synchronous address-check contract requires no raw payload retention and no-store responses.
Privacy is a core operating principle shaped by European data-protection standards.
Inbound, sending and migration data is handled only for the workflow you explicitly request.
Transient intelligence endpoints stay separate from services that require operational state.
Each capability solves a concrete job. Together they cover the path from the first address entered into a form to the last message your application receives, sends or moves between providers.
Maail looks beyond syntax and identifies what kind of mailbox you are dealing with. Use the result to qualify signups or trigger gated-content delivery, such as emailing an ebook to a reachable lead.
demo-user-1042@research.example
valid syntax · MX found · mailbox unchecked
Give a workflow its own inbound address. Maail receives the message, normalizes email complexity and delivers a structured event to your application.
invoice-route@inbound.example
email.received → your webhook
Send transactional messages directly or render a reusable template with variables. Your application provides the data; Maail builds and accepts the message.
template: invoice-ready
msg_01K4… · queued
Send raw RFC 822 or structured message content. Maail uses an LLM to understand the intent and returns a decision your mail gateway or product can act on.
Urgent: confirm your credentials
spam · 0.97 · credential_phishing
Connect a source and destination mailbox, then let Maail copy the complete history while preserving the structure users expect. Run a final catch-up pass before switching MX records so nothing is missed.
old-provider.eu → new-provider.eu
18,420 messages · 37 folders · complete
Connect address signals and incoming messages to the decisions your product already owns. Keep approval rules, business mappings, and exceptions explicit.
Catch malformed addresses before creating an account. Use disposable and role-account signals to guide review, not to assume every unusual address is fake.
Explore signup validationRoute invoice and receipt messages to a dedicated intake. Map the event into your ERP or BI system, with human review where financial decisions need it.
Plan invoice intakeCompare DMARC source volumes and alignment with approved senders. Agree alert and ticket rules during monitoring onboarding instead of treating every failure as an attack.
Explore DMARC monitoringCombine role-address signals with message classification to suggest a queue. Keep unknown cases and low-confidence decisions available for your team to review.
Explore support routingConnect confirmations and shipping notices to your order workflow. Validate sender context and business identifiers before changing fulfilment state.
Plan order eventsAdd domain, role-account, and likely-name signals to CRM records when evidence is available. Treat inferred details as hints, not verified identity.
Explore address analysisChoose an email verification workflow for your offer. Each guide covers the checks, the user experience and the limits to account for.
Catch address mistakes and help interested readers receive your resource.
Improve your download flowStart with an email address, confirm the subscription and collect preferences progressively.
Simplify newsletter signupCombine address checks with institution matching, inbox confirmation and your eligibility policy.
Plan education accessFind syntax and routing failures early, then use delivery feedback to maintain list quality.
Review the validation flowA step-by-step guide to syntax, MX routing, disposable providers and inbox confirmation.
Read the verification guideUnderstand format checks, international addresses and helpful error handling.
Read the developer guideInspect your policy, read aggregate reports and plan a controlled enforcement rollout. Start with the free tools; discuss ongoing collection and workflows when you are ready.
Decode tags, discover inherited policies and review reporting authorization evidence.
Run the DMARC inspectorReview source volumes and aligned SPF/DKIM outcomes. A failure is a question to investigate, not automatic proof of abuse.
Analyze a reportAgree sender ownership, reporting scope, retention and rollout decisions. Monitoring onboarding is by request, not activated by a lookup.
Explore DMARC monitoringMaail hides transport and parsing details behind predictable resources, events and decisions.
Call the API, send a message or let Maail receive email for a configured route.
Provider data, message structure and model reasoning become a clean response.
Accept the user, reject spam, trigger a workflow or continue with a message ID.
Every request uses Bearer authentication, JSON by default and a stable request ID. Raw email can also be normalized into structured JSON. This v1 draft does not yet specify raw RFC 822 submission or attachment uploads.
https://api.maail.co/v1POST /inbound/domainsPOST /templatesPOST /mailbox-connectionsGET /mailbox-migrations/:idGET /messages/:idFull v1 design specification →
/email/analyzeClassify an email address and decide whether it belongs in your product.
{
"email": "demo-user-1042@research.example"
}{
"data": {
"email": "demo-user-1042@research.example",
"cleanedEmail": "demo-user-1042@research.example",
"status": "valid",
"reasonCodes": ["valid_syntax", "has_mx"],
"mailbox": {"status": "not_checked"}
},
"meta": {"requestId": "req_demo_1042", "apiVersion": "v1"}
}The API design keeps synchronous address checks transient. Batches, inbound mail, sending and migration require their own operational state and retention rules. Confirm the scope and processing terms before integration.
Every plan includes address intelligence, inbound routes, transactional sending, spam classification, and API access. Upgrade when volume grows.
For prototypes and small production workflows.
For products with recurring email workflows.
For higher-volume and business-critical systems.
Additional usage is billed monthly. Mailbox migrations are priced separately by mailbox size and volume.
Validation is one signal, but the product goes further. Maail classifies the mailbox and its context—such as business, education, personal, role-based or disposable—and returns a recommendation your product can use directly.
You create an inbound route and receive an address such as invoice-route@inbound.example. Every message to that route is normalized and delivered as a signed email.received event to your webhook.
Yes. The messages endpoint accepts direct subject, HTML and text content, or a stored template plus variables. Templates are useful for repeated transactional messages but are not mandatory.
It can be used independently, but the strongest mail pipeline combines authentication, reputation, deterministic rules and semantic classification. Maail is the content-aware decision signal in that stack.
Yes. Call the spam endpoint as an additional policy signal and define explicit timeout and fail-open behavior. For deeper analysis without SMTP latency, classify after accepting the message into the queue.
Maail copies messages through IMAP while preserving folder structure, read and flagged states, and internal message dates. Migration jobs are resumable, expose progress and can perform an incremental catch-up pass immediately before the final provider switch.
The synchronous address-check specification requires no raw payload retention. Batches, inbound mail, sending and migration have separate operational retention requirements. Review metadata handling and processing terms during onboarding.
Tell us what arrives, what you need to know and what should happen next.