Documentation
Migrate from Postmark.
The field names change from PascalCase to lowercase and the token moves into a bearer header. Here is the send call before and after, then what maps to what and what to check.
The send call, before and after
Before, with Postmark's email API (see Postmark's docs for your library version):
After, with Mailtruss:
The changes: field names are lowercase (from, to, subject, html, text); the key goes in an Authorization: Bearer header instead of X-Postmark-Server-Token; and there is no MessageStream, because Mailtruss sends API mail and broadcasts to contacts through separate endpoints. A send returns the new email's id, which you can use to fetch its delivery trace.
If you send over SMTP
Apps that use Postmark's SMTP relay only need new settings. Postmark's relay takes a server token (or an access key and secret) as the credentials; Mailtruss takes any username with an API key as the password:
Details and framework examples are on the SMTP page and in the integration guides.
What maps to what
To,Cc,Bcc(comma-separated strings in Postmark) becometo,ccandbcc, each a string or a list. Postmark's batch endpoint becomesPOST /api/v1/emails/batch, up to 100 emails per call.HtmlBodyandTextBodybecomehtmlandtext.ReplyTobecomesreply_to.TagandMetadatabecometags, a list of name and value pairs you can filter by.Headers(a list of name and value objects) become aheadersobject of name to value.Attachments(Name,Content,ContentType) becomeattachmentswith a base64contentand afilename.- Templates: Postmark sends a template by alias or ID with a
TemplateModel. A Mailtruss template is sent by ID with avariablesobject, and only the published version is ever sent. See Sending. TrackOpensandTrackLinks: tracking is switched on per sending domain (and per message through the API, to switch it off for one message). It is off by default.- Message streams: separate transactional mail from broadcasts. In Mailtruss, API sends are transactional, and
contacts,segments,topicsandbroadcastscover bulk mail with unsubscribe handling. - Scheduling:
scheduled_attakes an ISO 8601 time. - Inbound email: turn on receiving for a verified domain and handle
email.receivedat a webhook. See Receiving email.
Bounces and suppressions
Postmark deactivates addresses that bounced or complained. Export that list from Postmark (its suppression dump endpoint) and add the addresses to Mailtruss with POST /api/v1/suppressions, so you do not mail them again from a fresh sender. Mailtruss then records its own bounces with a plain-language reason and whether a retry is safe: see bounces.
Webhooks
Postmark has a separate webhook per event type and protects them with its own methods (see its docs on protecting a webhook), so verification code has to change. Mailtruss sends every event to one endpoint, signed with the Standard Webhooks scheme, and the client libraries include a verifyWebhook helper. Events are named email.delivered, email.bounced, email.complained, email.opened and email.clicked, so map them in your handler. See Webhooks.
What does not carry over
- Dedicated IP addresses: Mailtruss has none, and sends from shared infrastructure.
- Postmark's template editor and layouts: Mailtruss templates are managed in the dashboard or the API, without a layout system.
- Your history: sent-message history does not move. Keep your Postmark account read-only for as long as you need to look things up.
A safe order to switch
- Create an account and verify your sending domain (DNS records). Postmark's sender signature and DKIM records are separate from Mailtruss's, and the records differ. Check the result with the domain checker.
- Create a key and send a test to
delivered@mailtruss.test, so nothing reaches a real inbox. - Change the client, the key and the request body in one place in your code.
- Point your webhook handler at the new signing secret and event names, then send real mail.
- Import your suppression list, keep Postmark active for a few days while you watch the first real sends, then switch it off.
Your daily limit while you move
A new account starts with a lower daily sending limit that grows for 14 days (day 1: 200; days 2 to 3: 500; days 4 to 7: 1,500; days 8 to 14: 5,000, then your plan's own limit). It protects your sending reputation, which you share with every other customer. Plan the switch around it: send your lowest-risk mail first, and keep your old provider on for the rest until your limit catches up.
If you cannot wait, ask for a higher limit. On a paid plan, open Sending limits in the dashboard and tell us where you are moving from, your volume and what you send. A person reviews it against checks we run ourselves (your domain's authentication, your plan, how your account has behaved) and either approves a limit, asks a question or says no, always with a reason. Approval is never automatic. We reply within 1 working day and decide within 2 working days once we have everything we need. These are targets, not guarantees. How limit reviews work.
Comparing costs first? See Mailtruss vs Postmark, which uses Postmark's own published prices. Mailtruss's are on the pricing page.