Postmark (Edge)

Last updated on Nov 11, 2026

Postmark is an email delivery service that businesses use to send and receive transactional and broadcast emails through an API or SMTP. It provides tools to manage servers, sending domains, templates, and message streams, and to track the delivery, opens, clicks, and bounces of emails.

Hevo uses the Postmark API to replicate the servers, domains, sender signatures, templates, message streams, outbound and inbound messages, bounces, suppressions, and email statistics of your Postmark account to the Destination of your choice. To ingest data, you must provide Hevo with an Account API token. Hevo uses this token to list the servers in your account and reads the data of each server with that server’s own API token, which Postmark returns with the server details. Hevo does not store the server API tokens.


Supported Features

Feature Name Supported
Capture deletes Yes, for the Server, Domain, Sender Signature, Template, Message Stream, and Outbound Statistics objects
History mode No
Custom data (user-configured tables & fields) No
Data blocking (skip objects and fields) Yes
Resync (objects and Pipelines) Yes
API configurable Yes

Handling of Deletes

Hevo ingests all the records of the Domain, Message Stream, Outbound Statistics, Sender Signature, Server, and Template objects in each run. When a record is no longer in Postmark, Hevo sets the value of the metadata column _hevo_marked_deleted to True for the record in the Destination.

Hevo does not capture deletes for the other objects. Postmark does not let you delete messages, bounces, or events, and the messages that Postmark removes after the retention period remain in the Destination. If you remove a suppression in Postmark, the record remains in the Destination.


Source Considerations

  • Postmark keeps outbound and inbound messages, and their events, only for the retention period of your account, 45 days by default. Hevo cannot ingest messages that are older than this period. Read How long are Inbound and Outbound messages stored in activity?.

  • Postmark returns at most 10,000 open or click events for each message stream in a query. If a message stream has more events, Hevo reads them by platform. Any events that remain out of reach are not ingested, and Hevo shows a warning for the object.

  • Hevo ingests only the inbound messages that Postmark has processed. Inbound messages that are blocked, scheduled for retry, or failed are not ingested.

  • If Hevo cannot read the data of a server with its Server API token, Hevo skips that server and continues with the other servers.



Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Nov-11-2026 2.54 New document.

Tell us what went wrong