A Resend-compatible API: keep your SDK, change the base URL
The BillionSend API has the same paths, request shapes and error format as Resend's. Install Resend's own SDK for your language, point it at BillionSend and use a bs_ API key. Your code stays as it is.
What Resend-compatible API does
Official SDKs, no fork
Node.js, Python, Go, Ruby, PHP, Rust, Java and .NET use Resend's own packages. There is no BillionSend SDK to install or keep up to date.
Same errors, same shapes
Errors come back as statusCode, name and message, like Resend's, so your existing error handling keeps working. Pagination uses the same limit, after and before cursors.
Tested with the official SDK
We run the official resend SDK against our API in contract tests, so a change that would break an SDK call fails before it ships.
More than the Resend API has
On top of Resend's endpoints you get inboxes and received mail, contact verification, email metrics, unsubscribe records, usage and deliverability insights.
Differences are explicit
Where BillionSend differs, for example inline base64 attachments only or unsubscribes scoped to the sending domain, the API basics page lists it. Unsupported settings are rejected with a 422, never silently ignored.
Move your account with one command
The migration tool copies contacts, segments, topics, templates, webhooks, domains and suppressions from Resend. Your code then needs two settings changed.
Point the SDK at BillionSend
Set the base URL when you create the client, or export RESEND_BASE_URL, and use your bs_ key. The base URL has no trailing slash in Node.js. Other languages set it in their own way; the SDK page lists each one.
import { Resend } from "resend";const resend = new Resend("bs_...", { baseUrl: "https://api.billionsend.com" });await resend.emails.send({ from: "Acme <hello@mail.example.com>", to: "user@example.org", subject: "Hello", html: "<p>It works.</p>",});