Send from product code
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 →Choose REST for application sends, SMTP for existing mail integrations, or inbound webhooks for replies and email-driven workflows. Postscale connects these paths through verified domains, with primary service data hosted in the EU/EEA.
Need provider-level comparison? Review Postscale as an EU transactional email provider for product teams.
Start with what your application needs to do. Sending from a domain and receiving its mail are separate choices; an outbound integration does not require moving your business inbox.
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 →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 →Configure inbound MX, accepting addresses or catch-all, and routing rules. Verify signed webhooks and retrieve stored messages for your workflow.
Build an inbound workflow →A focused API surface with production controls, predictable resources, and the operational visibility to run email confidently.
Trigger password resets, OTPs, magic links, receipts, confirmations, account alerts, and product notifications through REST, SDKs, or SMTP relay.
Point MX records at Postscale and receive parsed inbound messages, headers, bodies, attachments, and sender metadata as signed JSON webhooks.
Move Rails, Django, Laravel, WordPress, PHP, and legacy systems by swapping SMTP host and credentials instead of rewriting send code.
Hard bounces, complaints, unsubscribes, and manual blocks are checked before sending so known-bad recipients do not keep damaging reputation.
Create masked addresses for signup flows, marketplaces, feedback tools, and support workflows where users should not expose their real inbox.
Track delivered, bounced, deferred, and complained events, import provider suppressions, review DMARC reports, and ramp new senders deliberately.
The public API uses explicit resources and familiar JSON. Move from a first request to production without changing integration models.
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 docsconst 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);The dedicated sending page for password resets, OTPs, receipts, confirmations, alerts, and product notifications.
Read moreUse SMTP relay when an existing app, framework, CMS, or legacy system already sends mail through SMTP.
Read moreReceive email as signed parsed webhooks for support inboxes, reply handling, and email-driven workflows.
Read moreHow Postscale combines EU/EEA-hosted primary service data, masked aliases, suppressions, DMARC reports, and clear GDPR documentation.
Read moreCompare Postscale with SES when raw sending cost is not the only buying criterion.
Read morePlan endpoint mapping, webhook migration, suppression imports, DNS changes, and staged cutover.
Read moreAn 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.
Yes. REST sends and SMTP-originated sends share the same verified domains, logs, suppressions, and webhook event pipeline.
No. Postscale focuses on transactional and product email workflows: verification, password reset, receipts, account alerts, inbound replies, masked aliases, and app notifications.
Outbound usage counts per accepted recipient, including To, Cc, and Bcc. Accepted inbound messages count toward the same monthly quota.
The free tier includes everything required to evaluate the API. No credit card required.
Create a free account