Email APIs are product infrastructure

Email APIs are where a landing page, SaaS, or backend starts talking back.

Captured emails sitting in a form, database, CSV, or PocketBase collection are only raw intent.

The useful workflow starts when code can send the next thing: a verification link, welcome email, lead magnet, attachment, invoice, onboarding step, or follow-up.

The practical split is:

• Use an email API when the app owns the event and needs structured sending, templates, logs, and tokens.
• Use SMTP when an existing tool expects a mail server, such as PocketBase, Mautic, Odoo, or Listmonk.
• Use a marketing platform when the job is list management, campaigns, segmentation, subscriptions, and unsubscribes.
• Keep DNS authentication separate from provider choice; deliverability still depends on the domain setup.

Mailtrap worked well as the developer-friendly option for API and SMTP testing, Resend looked strong for API-first transactional email and receiving, and Mailjet paired well with Listmonk as the delivery engine behind campaigns.

The provider matters less than the control loop: capture intent, verify it, send the right artifact, track the result, and let users unsubscribe when the message is marketing.

Related:

• A boilerplate to create Landings for lead generation.
• SMTP and e-mail stuff
• Mail DNS is deliverability infrastructure
• Make Landing repo
• Mailtrap ESP notebook
• Programmatic email script
• DIY landing boilerplate