Send, receive, or relay email from your app

Send emails through the API or SMTP, and receive incoming messages through webhooks. Use the integration that fits your app.

Learn about EU/EEA hosting and data processing.

Choose your email workflow

Choose how your app sends and receives email. Sending through Postscale does not require moving your existing inbox.

Send through the API

Use an SDK or POST /v1/send for password resets, receipts, and notifications. Read the production requirements and handle delivery events after the request is accepted.

Set up transactional sending →

Keep an SMTP integration

Configure relay credentials in a framework, CMS, or existing mail client. Use this path when the application already expects an SMTP server.

Review SMTP relay →

Receive replies and attachments

Set up a receiving domain and routing rules to send parsed messages to your webhook endpoint.

Build an inbound workflow →

Send and receive email

Send transactional email

Trigger password resets, OTPs, magic links, receipts, confirmations, account alerts, and product notifications through REST, SDKs, or SMTP relay.

Receive email as webhooks

Point MX records at Postscale and receive parsed inbound messages, headers, bodies, attachments, and sender metadata as signed JSON webhooks.

SMTP relay

Move Rails, Django, Laravel, WordPress, PHP, and legacy systems by swapping SMTP host and credentials instead of rewriting send code.

Suppression lists

Block sends to addresses on your suppression lists, including hard bounces, complaints, and unsubscribes.

Add privacy aliases

Create masked addresses for signup flows, marketplaces, feedback tools, and support workflows where users should not expose their real inbox.

Monitor deliverability

Track deliveries, bounces, delays, and complaints. Review DMARC reports and gradually increase sending volume.

Send an email with the API.

This Node.js example sends an email and returns a message ID you can use to track delivery.

Run this on your server. A test key records a simulated send; a live key requires account approval and a verified sending domain. An accepted request is not proof of delivery. Sending endpoints do not support Idempotency-Key, so do not automatically retry an ambiguous timeout.

Read API docs
Node.js: send through the email API ready
const response = await fetch("https://api.postscale.io/v1/send", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.POSTSCALE_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    from: "Acme <hello@acme.example>",
    to: ["user@example.com"],
    subject: "Confirm your account",
    html_body: "<p>Your verification code is 482193.</p>",
    text_body: "Your verification code is 482193.",
    tags: ["verification"]
  }),
});
const result = await response.json();
if (!response.ok) {
  throw new Error(result.error || "Send request failed");
}
// Keep this ID to correlate later delivery events.
console.log(result.message_id, result.status);

FAQ

What is an email API?

An email API lets application code submit messages or retrieve received email through HTTP. SDKs wrap those endpoints, webhooks notify your app about events, and SMTP relay is a separate integration option for software that already sends mail.

Can I use the API and SMTP relay together?

Yes. REST sends and SMTP-originated sends share the same verified domains, logs, suppressions, and webhook event pipeline.

Is this for marketing campaigns?

No. Postscale focuses on transactional and product email workflows: verification, password reset, receipts, account alerts, inbound replies, masked aliases, and app notifications.

What counts toward usage?

Outbound usage counts per accepted recipient, including To, Cc, and Bcc. Accepted inbound messages count toward the same monthly quota.

Connect your app to Postscale.

Try Postscale with a free account. No credit card required.

Create a free account