MailPace

Send through the MailPace API, a deliberately minimal adapter for address fields and body content.

Capabilities

Repeated headers	Idempotency	Scheduling	Personalized
No	`none`	No	`expanded`

These values come from the adapter's exported capabilities declaration. The field support matrix covers normalized message fields.

The MailPace adapter calls the MailPace send API with plain fetch. It has the smallest adapter surface in the SDK: addresses, subject, and body only, with recipient lists serialized as comma-separated strings.

MailPace@opencoredev/email-sdk/mailpace

Provider docs

Configure

Create a server token in the MailPace dashboard and verify the sending domain.

lib/email.ts

import { createEmailClient } from "@opencoredev/email-sdk";
import { mailpace } from "@opencoredev/email-sdk/mailpace";

export const email = createEmailClient({
  adapters: [mailpace({ apiKey: process.env.MAILPACE_API_KEY! })],
});

Prop

Type

Send

MailPace maps cc, bcc, and replyTo alongside html/text (sent as htmlbody/textbody). That is the whole surface, which makes it a good fit for sign-in alerts, receipts, and other plain notifications.

const result = await email.send({
  from: "Acme <hello@acme.com>",
  to: "user@example.com",
  replyTo: "support@acme.com",
  subject: "New sign-in to your account",
  text: "A new sign-in from Berlin, Germany was detected. If this was not you, reset your password.",
});

console.log(result.id); // MailPace message id (`id` or `message_id` in the response)

No headers, attachments, tags, or metadata

MailPace's send endpoint takes none of these, so any of them throws an EmailValidationError before a request is made. Check your production message shape against the field support matrix before routing through MailPace as a fallback.

Verify from the CLI

MAILPACE_API_KEY="..." npx --package @opencoredev/email-sdk email-sdk doctor --adapter mailpace

MAILPACE_API_KEY="..." npx --package @opencoredev/email-sdk email-sdk send \
  --adapter mailpace \
  --from "Acme <hello@acme.com>" \
  --to user@example.com \
  --subject "MailPace smoke test" \
  --text "It works" \
  --dry-run

Drop --dry-run for one real send to confirm the token and verified domain work end to end.

Frequently asked questions

Does Email SDK support MailPace?

Yes. Email SDK ships a MailPace adapter imported from @opencoredev/email-sdk/mailpace. You keep your MailPace account and credentials; the SDK adds message validation, typed errors, and no-network test adapters around the same send() call used for every other provider.

Which message fields does the MailPace adapter support?

MailPace supports CC recipients, BCC recipients, and Reply-To address. It does not support Custom headers, Attachments, Tags, Metadata, and Scheduled sending (sendAt); Email SDK rejects a message that uses those fields before any request is made.

Can MailPace schedule email for later with Email SDK?

No. MailPace has no provider-side scheduling, so a message with sendAt fails validation. Store the job in your own queue and send when it is due.

Does the MailPace adapter support idempotent sends?

No. MailPace has no provider-side idempotency, so a retried send can be delivered twice. Deduplicate in your own queue before retrying.