Mailazy documentation

Send transactional and marketing email through one platform. REST API + SMTP, visual workflows, AI templates, contact management, and a partner program — all documented here.

Start here

If this is your first time, the Quickstart walks you through creating an API key, sending your first transactional email, and saving a template — in about five minutes.

Browse by topic

Quickstart →

API key, first send, first template. Five minutes from signup to inbox.

Transactional email →

Send via REST API or SMTP relay. Webhooks for delivery, open, click, bounce.

Templates →

Handlebars with versions and partials. AI generation from a plain-English prompt.

Newsletters →

One-off broadcasts: pick a template, target a list, schedule or send now.

Automations →

Event-triggered + delay-based lifecycle flows. Visual step builder, no JSON.

Contacts & lists →

Import CSV, build lists from a filter, manage suppressions and unsubscribes.

API reference →

Auth, errors, rate limits, every endpoint at a glance.

Integrations →

Webhooks, Zapier / Make / n8n, and 80+ direct integrations.

What you can build

Mailazy is a single platform for both transactional email (OTPs, password resets, order receipts) and marketing email (newsletters, lifecycle flows, broadcasts). Marketers ship campaigns in the visual workflow builder while engineers send through the same REST API and SMTP relay — same logs, same analytics, one bill.

Common use cases

SaaS onboarding flows — fire a 5-day welcome series when a user signs up, pause when they activate, branch on plan tier.
E-commerce lifecycle — abandoned-cart, order confirmation, shipping updates, post-purchase nurture.
Authentication / passwordless — magic links, OTPs, password reset — sub-2-second delivery on Gmail.
Weekly newsletters — drag-drop builder or AI-drafted from a prompt, scheduled to a segment.
Customer education — feature announcements segmented by usage metadata.

Architecture in one sentence

Mailazy stores your contacts, lists, templates and suppressions; it accepts marketing campaigns and transactional sends through the same API; a worker drains scheduled sends through your configured SMTP (or your own AWS SES on Marketing tier and up) and writes back delivery + engagement events.

Got questions?

Pricing and trial details are on the pricing page. Anything not covered here — drop a note via contact us; we reply within one business day.