MailChannels Email API now has official SDKs for Node.js, Python, and PHP

Today we’re releasing three official SDKs for MailChannels Email API, a new developer dashboard, and a unified docs site. If you build multi-tenant SaaS, AI agents, or any platform where your users send email through your product, this is the fastest way to get started.

Why SDKs now

MailChannels Email API has always accepted standard JSON over HTTPS, so you could integrate from any language from day one. But every integration started with the same setup work: constructing requests, handling auth headers, parsing responses. The SDKs eliminate that.

What shipped

Node.js — install via npm, yarn, or pnpm:

npm i mailchannels-sdk

Full example:

import { MailChannels } from "mailchannels-sdk";
const mailchannels = new MailChannels(process.env.MAILCHANNELS_API_KEY);
const { data, error } = await mailchannels.emails.send({
  from: { email: "hello@yourdomain.com", name: "Your App" },
  to: { email: "user@example.com", name: "User" },
  subject: "Your notification",
  html: "<p>Hello from your app.</p>",
});

Node.js quickstart →

Python — install via pip or uv:

pip install mailchannels

The SDK reads MAILCHANNELS_API_KEY from your environment automatically.

Python quickstart →

PHP — install via Composer, with Laravel and Symfony integration guides:

composer require mailchannels/mailchannels-php

PHP quickstart →

All three SDKs are open source.

New dashboard

The new MailChannels dashboard at dash.mailchannels.com is the control plane for your Email API account: API keys, domain health checks, account users, and sending configuration in one place.

Unified docs

Everything for the Email API — quickstarts, API reference, webhooks, multi-tenancy, SPF/DKIM/DMARC configuration, troubleshooting — now lives at docs.mailchannels.com.

What makes MailChannels different from other email APIs

Most developer email tools are optimized for a single company sending its own mail. MailChannels is built for platforms where your users, tenants, customers, or agents send through your product. That means per-tenant sender isolation, abuse controls that scope to the source of the problem rather than your entire account, and Domain Lockdown — the mechanism that ties each sending domain to your account so another sender can’t use it without authorization.

If you’re building an app where downstream senders are the product, that’s a materially different problem than sending your own transactional email.

Get started

Start for free →

Read the Email API docs →