Overview
Integration
User guide
API reference
Webhooks
Introduction
Official libraries
- Rails gem
- Ruby gem
- .NET
- Java
- PHP
- Craft plugin
- Node.js
- CLI
- WordPress plugin
- Grunt plugin
- Zapier Actions
Community libraries
- Classic ASP
- Clojure
- ColdFusion
- Django
- Drupal module
- Elixir
- Erlang
- Google Go
- Grails plugin
- Haskell
- Java
- Laravel
- Magento extension
- Node.js
- Objective-C
- Perl
- Pharo Smalltalk
- PHP 5
- PowerShell Snap-in
- Python
- Scala
- Swift
- WordPress
- Zend
Tools and Integrations
Sending email with API
- Send a single email
- Send batch emails
Sending email with SMTP
Processing email
- Configure an inbound server
- Inbound domain forwarding
- Parse an email
- Configure inbound blocking
- Sample inbound workflow
Tracking opens
- Tracking opens per Server
- Tracking opens per email
- Message opens API
Tracking links
Managing your account
- Managing sender signatures
- Managing servers
Sandbox mode
- Server sandbox mode
- Generate fake bounces
Overview
- Endpoint URL
- Authentication
- HTTP response codes
- API error codes
Email
- Send a single email
- Send batch emails
Bulk
- Send bulk emails
- Get the status/details of a bulk API request
Bounce
- Get delivery stats
- Get bounces
- Get a single bounce
- Get bounce dump
- Activate a bounce
- Bounce types
- Rebound
Templates
- Send email with template
- Send batch with templates
- Push templates to another server
- Get a template
- Create a template
- Edit a template
- List templates
- Delete a template
- Validate a template
Server
- Get the server
- Edit the server
Servers
- Get a server
- Create a server
- Edit a server
- List servers
- Delete a server
Message Streams
- List message streams
- Get a message stream
- Edit a message stream
- Create a message stream
- Archive a message stream
- Unarchive a message stream
Messages
- Outbound message search
- Outbound message details
- Outbound message dump
- Inbound message search
- Inbound message details
- Bypass rules for a blocked inbound message
- Retry a failed inbound message for processing
- Message opens
- Opens for a single message
- Message clicks
- Clicks for a single message
Domains
- List domains
- Get domain details
- Create domain
- Edit domain
- Delete domain
- Verify DKIM
- Verify Return-Path
- Verify an SPF record
- Rotate DKIM keys
Sender signatures
- List sender signatures
- Get sender signature
- Create a signature
- Edit a signature
- Delete a signature
- Resend a confirmation
- Verify an SPF record
- Request a new DKIM
Stats
- Get outbound overview
- Get sent counts
- Get bounce counts
- Get spam complaints
- Get tracked email counts
- Get email open counts
- Get email platform usage
- Get email client usage
- Get click counts
- Get browser usage
- Get browser platform usage
- Get click location
Triggers: Inbound rules
- List inbound rule triggers
- Create an inbound rule trigger
- Delete a single trigger
Webhooks
- List webhooks
- Get a webhook
- Create a webhook
- Edit a webhook
- Delete a webhook
Suppressions
- Suppression dump
- Create a Suppression
- Delete a Suppression
Data Removal
- Create a Data Removal request
- Check a Data Removal request status
Webhooks overview
- What is a webhook?
- Protecting your webhook
- Testing your webhook
- Retry attempts
Bounce webhook
- What is a bounce webhook?
- Set the webhook URL
- Bounce webhook data
- Testing with curl
- How you can use the data
- Rebound
Inbound webhook
- What is an inbound webhook?
- Inbound webhook data
- Testing with curl
- How you can use the data
- Errors and retries
- Set the webhook URL
Open tracking webhook
- What is an open webhook?
- Set the webhook URL
- Open webhook data
- Testing with curl
- How you can use the data
Delivery webhook
- What is a delivery webhook?
- Set the webhook URL
- Delivery webhook data
- Testing with curl
- How you can use the data
Click webhook
- What is a click webhook?
- Set the webhook URL
- Click webhook data
- Testing with curl
- How you can use the data
Spam complaint webhook
- What is a spam complaint?
- Set the webhook URL
- Spam complaint webhook data
- Testing the spam complaint webhook with curl
- How you can use the data
Subscription change webhook
- What is a subscription change?
- Set the subscription change webhook URL
- Subscription change webhook data
- Testing the subscription change webhook with curl
- How you can use the subscription change data
SMTP API Error
- What is an SMTP API Error
- Set SMTP API Errors for a Server
- SMTP API Error Data
- Testing the SMTP API Error
- How can you use SMTP API Error
Inbound domain forwarding
If you have access to your DNS records, Postmark includes a simple way for you to configure your MX records to point to our mail servers, so that all email sent to a domain or sub-domain is processed by Postmark. If you do not have access to your DNS records, we support email being forwarded by 3rd party mail services .
1. Set an MX Record Choose a domain that you would like to listen on for incoming email to be processed by Postmark. In your DNS configuration, create an MX record that points to inbound.postmarkapp.com and give it a value of 10.
If you plan on just using your root domain for your inbound domain forwarding, then you'd add @ as the Name value in the MX record in your DNS configuration:
However, we typically recommend that you use a separate subdomain for your inbound domain forwarding. For example, example.yourdomain.com . You would add the subdomain value to the Name field in your MX record:
You may also use a “wildcard” inbound domain such as *.yourdomain.com which will cause all messages addressed to any subdomain of yourdomain.com to be routed to your inbound endpoint. For example, if you register *.yourdomain.com with Postmark and your DNS host, you may then use an inbound address such as user@client1.yourdomain.com and it will be routed to your inbound endpoint. In the MX record, you'd list * as the Name value:
2. Set the domain Inbound domains are unique across Postmark and are Stream-specific. You can configure the Inbound Domain on the Stream settings page.
Alternatively, you can use the Server API to set the Inbound Domain on your server.
Example request with curl curl "https://api.postmarkapp.com/servers/:serverid" \
-X PUT \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "X-Postmark-Account-Token: account token" \
-d "{InboundDomain: 'inbound.yourdomain.com'}"
Example JSON response {
"Name": "Production Testing",
"Color": "blue",
"SmtpApiActivated": false,
"RawEmailEnabled": false,
"InboundHookUrl": "http://hooks.example.com/inbound",
"BounceHookUrl": "http://hooks.example.com/bounce",
"OpenHookUrl": "http://hooks.example.com/open",
"PostFirstOpenOnly": false,
"InboundDomain": ""
}
3. Enable SMTP Enable SMTP on the server’s settings page.
4. Receive emails You can now receive emails sent to any address on the inbound forwarding domain and they will be processed using Postmark.