Postmark is a transactional email delivery service focused on speed and deliverability for application email. The Postmark connector reads outbound and inbound messages, opens and clicks, bounces, delivery statistics, templates, message streams, suppressions, webhooks, inbound rules, bulk send status, servers, domains, and sender signatures, and can send single, batch, template-based, and bulk email, and create and manage templates, streams, suppressions, webhooks, servers, domains, and sender signatures.
Power end-to-end data operations for your Postmark API with Nexla. Our bi-directional Postmark connector is purpose-built for Postmark, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Postmark or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Postmark workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Nexla connects to the Postmark API with a Postmark API token. Postmark has two kinds of token, and each endpoint works with only one of them:
Server API token: in Postmark, go to Servers, select your server, and open the API Tokens tab. A server token works with one server's data: sending email, bounces, templates, outbound and inbound messages, statistics, webhooks, inbound rules, suppressions, and message streams.
Account API token: in Postmark, go to Account, and open the API Tokens tab. An account token manages the account as a whole: servers, domains, sender signatures, pushing templates between servers, and data removal requests. Not every Postmark user role can see this tab; if you can't, ask your account owner.
A Nexla credential holds one token. Create one credential for each token type you need, and pick the matching credential when you set up a source or destination. Every endpoint template below is marked (server token) or (account token); with the wrong kind of credential, Postmark rejects the request with HTTP 401 Unauthorized. A server token reads and writes only its own server's data, so create a separate server-token credential for each Postmark server you work with.
For details, see Postmark's API authentication guide. Both tokens carry full access to what they cover, including sending email, so treat them like passwords. If a token is compromised, regenerate it on the same API Tokens tab.
Sends go to real recipients
Destinations that send email deliver it to the real addresses in your records as soon as the destination is activated, and Postmark counts every message against your plan. Eight destination templates send email and are marked Sends email below: Send Email, Send Batch Emails, Send Email With Template, Send Batch With Templates, Send Bulk Email, Push Templates To Server, Create Sender Signature, and Resend Sender Confirmation (the last two email a confirmation link to the sender address; Push Templates To Server sends nothing itself, but changes what live sends contain). Test sending templates with your own addresses first, or with a server whose delivery type is Sandbox, which accepts messages without delivering them.
Bulk API needs approval
The Send Bulk Email, List Bulk Email Requests, and Get Bulk Email Status templates use Postmark's Bulk API, which Postmark must approve for your account before use. Until then, Postmark rejects these requests. Contact Postmark support to request access.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field. Include the token type, and for a server token the server it belongs to, so the right credential is easy to pick later.
In the Authentication Type menu, select Server API Token or Account API Token, and paste the matching token from Prerequisites into the field. Nexla sends it in the X-Postmark-Server-Token or X-Postmark-Account-Token header on every request.
Do not select No Authentication. That option is left over from an earlier version of the connector and cannot work: every Postmark API request needs a token, so every source and destination that uses such a credential fails.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Nexla tests a server-token credential by reading the token's server, and an account-token credential by listing the account's servers.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Postmark connector tile, then select the credential that will be used to connect to Postmark, and click Next; or, create a new Postmark credential for use in this flow. Pick a server-token or account-token credential to match the template you plan to use.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Postmark endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area.
Templates that say "Results are paged automatically" read every page; all other templates make a single request. List templates return one record per item, such as one record per bounce or message. Templates that need an ID, such as a message or template ID, read data for that one object; use the matching list template to find the ID. The templates send none of Postmark's optional filters, such as date ranges, tags, recipients, or message streams; to filter, use Manual configuration.
Lists sent messages with their recipients, subject, status, tag, and received time.
Results are paged automatically, 500 records per page. Postmark returns at most 10,000 records for a search, so very large result sets are cut off at 10,000.
Covers the default transactional stream (outbound) only; the template sends no stream, recipient, tag, or date filter.
Lists open events for sent messages, with the recipient, email client, operating system, platform, location, and whether it was the first open.
Results are paged automatically, 500 records per page. Postmark returns at most 10,000 records for a search, so very large result sets are cut off at 10,000.
Lists link click events for sent messages, with the recipient, link, client, operating system, and location.
Results are paged automatically, 500 records per page. Postmark returns at most 10,000 records for a search, so very large result sets are cut off at 10,000.
Lists bounces on the server with each bounce's type, recipient address, message ID, bounce time, and whether the address is now inactive.
Results are paged automatically, 500 records per page. Postmark returns at most 10,000 records for a search, so very large result sets are cut off at 10,000.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Counts hard bounces, soft bounces, transient errors, and SMTP API errors each day.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Counts the emails sent with open tracking each day.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Counts opens by platform (desktop, mobile, webmail) each day.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Counts clicks by platform (desktop, mobile) each day.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Counts clicks by where the link was in the email (HTML or text part) each day.
Returns one record per day across Postmark's whole retention window, for the default transactional stream (outbound). The template sends no date range, tag, or stream filter.
Lists processed inbound messages with the sender, recipients, subject, mailbox hash, status, and date.
Results are paged automatically, 500 records per page. Postmark returns at most 10,000 records for a search, so very large result sets are cut off at 10,000.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Postmark data sources can also be manually configured to ingest data from any valid Postmark API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or optional filters that the templates do not send, such as a date range, tag, recipient, or messagestream filter. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers. Postmark endpoint URLs take the form https://api.postmarkapp.com/...; Postmark's search endpoints require the count and offset query parameters. See the Postmark API reference for the available endpoints.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Postmark data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Postmark destination, and select the Send to Destination option from the menu. Select the Postmark connector from the list of available destination connectors, then select the credential that will be used to connect to Postmark, and click Next; or, create a new Postmark credential for use in this flow. Pick a server-token or account-token credential to match the template you plan to use.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Postmark endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Unless a template says otherwise, each record in the Nexset is sent as the JSON body of one request, one record at a time, so shape each record to match the request body that Postmark documents for the endpoint. Postmark field names are case-sensitive and start with a capital letter, such as From and HtmlBody. ID settings, such as a template or domain ID, are fixed on the destination and apply to every record it sends. Templates are marked Sends email when they cause Postmark to send email, and Side effect when they delete data or make other changes that cannot be undone from Nexla.
Sends one email for each record. Each record is the request body: From, To, Subject, HtmlBody or TextBody, and optionally MessageStream, Tag, and tracking settings. The From address must be a confirmed sender signature or on a verified domain.
Sends email: sends one email to the record's recipients.
Sends one email for each record, built from a Postmark template. Each record includes TemplateId or TemplateAlias, TemplateModel (the template variables), From, and To.
Sends email: sends one email to the record's recipients.
Sends up to 500 template-based emails in one request. Each record is one message, shaped like a Send Email With Template record; Nexla groups records into batches of up to 500.
Submits one bulk send request per record. Each record is the request body: From, Subject, HtmlBody or TextBody, and a Messages array with each recipient and its variables. Check progress with the Get Bulk Email Status source template.
Sends email: sends an email to every recipient in the record's Messages array.
Requires the Postmark Bulk API, which Postmark must approve for your account first.
Creates a template or layout from each record. A record carries Name, Subject, HtmlBody or TextBody, and optionally Alias, TemplateType, and LayoutTemplate.
Checks template content and renders it with test data, without saving anything. A record carries Subject, HtmlBody, TextBody, and optionally TestRenderModel.
Copies changed templates from one server to another. A record carries SourceServerID, DestinationServerID, and PerformChanges (set it to false to preview the changes without applying them).
Sends email: the push itself sends no message, but pushed templates go live on the destination server at once, so the next emails that server sends with them use the new content.
Side effect: overwrites templates on the destination server.
Suppresses recipient addresses on a message stream, so Postmark stops sending to them. Each record carries an EmailAddress field; Nexla groups records into batches of 50.
Side effect: stops sending to the addresses on that stream.
Enter the Message Stream ID. This is the stream's ID, such as outbound or broadcast; use the List Message Streams template to find it.
Removes suppressions from a message stream, so Postmark sends to the addresses again. Each record carries an EmailAddress field; Nexla groups records into batches of 50.
Side effect: re-enables sending to the addresses on that stream.
Enter the Message Stream ID. This is the stream's ID, such as outbound or broadcast; use the List Message Streams template to find it.
Updates the settings of the server the server token belongs to, such as its name, color, open and link tracking, and webhook URLs. Each record contains only the fields to change.
Adds a sending domain from each record. A record carries Name and optionally ReturnPathDomain. Use the Get Domain source template to see the DNS records to add.
Asks Postmark to erase all data it holds for a recipient. A record carries RequestedBy, RequestedFor (the recipient's address), and NotifyWhenCompleted. Check progress with the Get Data Removal Status source template.
Side effect: permanently deletes the recipient's data from Postmark; it cannot be recovered.
Postmark destinations can also be manually configured to send data to any valid Postmark API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The Postmark API expects JSON request bodies. Nexla adds the token header from the credential, so leave X-Postmark-Server-Token and X-Postmark-Account-Token out of the request headers.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Postmark endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Postmark endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.