Introduction

What MailingCore is, who it's for, and how it fits in your stack.

MailingCore is a developer-first email SaaS platform hosted in the EU. It lets you send transactional emails and newsletters from your application without building or operating your own mail server.

It is not a generic MTA or relay: it is the platform layer (REST API, SDK, dashboard, templates, domains, quotas) on top of transports such as AWS SES or SMTP.

Who it's for

Developers integrating from Next.js, React, Node, or any backend with an API key.
Product teams managing templates, domains, campaigns, and analytics from the dashboard.
B2B integrators syncing contacts and campaigns via API (multi-tenant pattern).
24/7 support with Botpress chatbots opening helpdesk incidents via transactional email — see Botpress and helpdesk.

What you can do

Area	Capabilities
Transactional	`POST /emails/send`, queued delivery, batch, scheduling
Templates	Draft/Published versioning, language variants, library
Deliverability	SPF/DKIM/DMARC domain verification, open/click tracking
Newsletter	Contacts, campaign fan-out, hosted unsubscribe pages
Integration	API keys with scopes, outbound webhooks with HMAC signatures

Basic architecture

Create an account in the dashboard and a tenant (workspace).
Generate an API key with the permissions you need (email:send, etc.).
Send from your server (recommended) or with the mailingcore-js SDK.
Optionally: verify your sending domain and publish templates in the editor.

Your app  →  MailingCore API (api.mailingcore.com)  →  SES / SMTP  →  Recipient inbox

Next step

Continue with Key concepts or Quickstart for your first send.