SDKs
Official SDKs for Node.js, Python, Go, Ruby, PHP, Rust, Java, and .NET — plus a CLI, and a clean REST API for everything else.
MailBlastr ships official SDKs for eight languages — Node.js (`mailblastr` on npm), Python, Go, Ruby, PHP, Rust, Java, and .NET — plus a CLI. Each wraps the same REST API with the idioms of its ecosystem.
Underneath them all is a clean REST API: predictable request and response shapes, mb_-prefixed API keys, the Bearer auth scheme, a consistent error envelope, and standard pagination conventions. So every language has two good options: install the official SDK, or hit the JSON API directly with any HTTP client.
Official Node.js SDK
Install the mailblastr package and instantiate the client with your mb_ API key. Every method returns { data, error } — error is null on success, or { statusCode, name, message } on failure, so there are no exceptions to catch for API errors.
npm install mailblastrimport { Mailblastr } from 'mailblastr';
const mb = new Mailblastr('mb_xxxxxxxxx');
const { data, error } = await mb.emails.send({
from: 'Acme <hello@yourdomain.com>',
to: ['delivered@mailblastr.dev'],
subject: 'Hello from MailBlastr',
html: '<p>Your first email 🎉</p>',
});
if (error) console.error(error.name, error.message);
else console.log('sent', data.id);The client exposes one property per resource — emails (with nested emails.receiving), batch, domains, audiences, contacts, contactProperties, campaigns, segments, topics, templates, automations, webhooks, logs, events, apiKeys, and polls — each modeled on the same create / get / list / update shape used throughout these docs.
const mb = new Mailblastr('mb_xxxxxxxxx', {
baseUrl: 'https://www.mailblastr.com/api', // optional — defaults to the MailBlastr host
});pip install mailblastr), Ruby (gem install mailblastr), PHP (composer require mailblastr/mailblastr), Rust (cargo add mailblastr), .NET (dotnet add package Mailblastr), Go, and Java — see SDKs & CLI for every package manager command.Call the REST API directly
Every endpoint in these docs is plain JSON over HTTPS at https://www.mailblastr.com/api. Authenticate with an Authorization: Bearer mb_xxxxxxxxx header. Each API page shows ready-to-run snippets for every official SDK plus raw cURL.
import { Mailblastr } from 'mailblastr';
const mb = new Mailblastr('mb_xxxxxxxxx');
const { data, error } = await mb.emails.send({
"from": "Acme <hello@yourdomain.com>",
"to": ["delivered@mailblastr.dev"],
"subject": "Hello from MailBlastr",
"html": "<p>It works!</p>"
});
console.log({ data, error });com.mailblastr:mailblastr coordinate. Android is the exception: the default transport uses java.net.http (Java 11+), which Android does not ship, so an Android app must supply its own HttpTransport implementation. Any other language with an HTTP client (Elixir, …) can call the API directly.Any HTTP client works
Prefer no dependency? The API is plain JSON over HTTPS, so the standard HTTP client in any language can call it directly. Point your client at https://www.mailblastr.com/api with your mb_ key and send a request:
- Node.js — the official
mailblastrSDK, or the built-infetch. - PHP — the official
mailblastr/mailblastrpackage, or Guzzle / the cURL extension. - Python — the official
mailblastrpackage, orrequests/httpx. - Ruby — the official
mailblastrgem, orNet::HTTP/Faraday. - Go — the official Go module, or
net/http. - Java — the official
com.mailblastr:mailblastrartifact, orjava.net.http.HttpClient. - Rust — the official
mailblastrcrate, orreqwest. - .NET — the official
MailblastrNuGet package, orHttpClient.
Each API reference page includes ready-to-run snippets for every official SDK — Node.js, Ruby, PHP, Python, Go, Rust, Java, .NET, the CLI — plus raw cURL, so your stack's tab is one click away.
Which should I use?
| You have… | Use |
|---|---|
| A Node.js / TypeScript project | Install the official mailblastr SDK. |
| A Python, Go, Ruby, PHP, Rust, Java, or .NET project | Install the official SDK for that language — see SDKs & CLI. |
| Anything else with an HTTP client | Call the REST API directly. |
| A framework that only speaks SMTP | Use an HTTPS-capable adapter. Raw SMTP is not currently deployed. |