Skip to content
Splashify Pro
Email docsEmail

Send raw

Send a fully-formed MIME message (RFC 5322). For when you need control over headers, attachments, multipart structure, or DKIM-signed forwarding.

POST

/api/v1/partner/email/send-raw

Request body

json
{
  "raw_message_base64": "RnJvbTogaGVsbG9AeW91cmNvbXBhbnkuY29tDQpUbzogY3VzdG9tZXJAZXhhbXBsZS5jb20NClN1YmplY3Q6IEhlbGxvDQpDb250ZW50LVR5cGU6IHRleHQvcGxhaW47IGNoYXJzZXQ9dXRmLTgNCg0KSGVsbG8h",
  "configuration_set_name": "production"
}

The message must have one From: header with one address, and that address must be on a verified identity.

Response

json
{
  "success": true,
  "results": [
    {
      "recipient": "[email protected]",
      "message_id": "0192b6a8-...",
      "status": "queued"
    }
  ]
}

results carries one entry per recipient, the same as /send. A request that cannot be sent answers 400: base64 or message that cannot be read, a message over 10 MB, a Subject: longer than 16 KB, a from that is not the one in the message, or an address that is not verified.

What you control

  • All headers — From, To, Cc, Bcc, Subject, Reply-To, Message-ID, arbitrary X- headers, In-Reply-To, References
  • MIME structure — multipart/alternative, multipart/mixed, multipart/related (inline images via Content-ID:)
  • Attachments — encode each part with the right Content-Type + Content-Disposition + Content-Transfer-Encoding
  • Custom headers — anything not on the reserved list

Your bytes go out as they are, so a Bcc: header would reach every recipient. Leave it out and put those addresses in to.

What we override

  • Date: — set to send time if missing
  • Message-ID: — added if missing
  • DKIM-Signature — we always sign with our shared key
  • Return-Path — set to our bounce address for VERP routing

Nothing else is added or changed. If your message has Date: and Message-ID:, recipients get your exact bytes plus the DKIM-Signature header, except when the message is rebuilt (below).

When a message is rebuilt

When we cannot deliver a message from our usual sending servers, we may send it from another of our sending servers, which rebuilds it from its parts instead of sending your bytes. Only marketing messages (category marketing, or a broadcast) and messages without a Message-ID: of their own are ever rebuilt. A reply (In-Reply-To: or References:) is never rebuilt, and neither is a message we cannot rebuild exactly, such as a signed or encrypted message, a calendar invite, or one with Cc:: it waits for our usual sending servers.

A rebuilt message keeps your From, To, Reply-To and Subject, its text and HTML exactly as written (tracking links and pixels included), its inline images and its attachments. On it:

  • Message-ID: and Date: are set by us. When we are told the Message-ID: the recipient got, the message's smtp_message_id is that one; otherwise smtp_message_id is left as it was.
  • List-Unsubscribe, List-Unsubscribe-Post and List-Id are kept.
  • X- headers, Precedence, Auto-Submitted, List-Help, List-Subscribe, Received and DKIM headers are not kept. The message is signed with your domain's DKIM 2 record.

What we leave to you

  • Tracking: no open pixel and no link rewriting, whatever the configuration set says. email.opened and email.clicked do not fire.
  • Unsubscribe: no unsubscribe link and no List-Unsubscribe headers, and {{unsubscribe_url}} is not filled in. For marketing mail you must include them yourself.
  • Replies: replies go to your own Reply-To: and email.replied does not fire.

When to use this

  • Sending forwarded mail with original headers preserved
  • Replying inside an existing thread (In-Reply-To / References)
  • Multipart with attachments
  • Custom List-Id / List-Help / List-Subscribe / List-Unsubscribe headers

For simple HTML+text sends, use /send — much less ceremony.

Example

Building a multipart message in Node:

javascript
import { createMimeMessage } from "mimetext";

const msg = createMimeMessage();
msg.setSender("[email protected]");
msg.setRecipient("[email protected]");
msg.setSubject("Receipt + invoice attached");
msg.addMessage({ contentType: "text/plain", data: "See attached." });
msg.addMessage({ contentType: "text/html", data: "<p>See attached.</p>" });
msg.addAttachment({
  filename: "invoice.pdf",
  contentType: "application/pdf",
  data: pdfBase64,
});

const rawB64 = Buffer.from(msg.asRaw()).toString("base64");

await fetch("https://api.splashifypro.com/api/v1/partner/email/send-raw", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ raw_message_base64: rawB64 }),
});