How to Test Inbound Webhooks
The most common scenario where you would need to do a test with Inbound Webhook is where a customer raises a question of the information we parse into the payload (from the headers and information available in the email we receive).
For example, customer may claim that there is a part of the message missing. As explained in our API docs, some parameters like StrippedTextReply are parsed in a best effort manner. But with other parameters, like TextBody or HTMLBody, the same rule applies as with outbound emails - Postmark does not make any changes in transit, it just takes what it gets and, like an excellent courier it is, delivers (in case of inbound, it delivers it to a webhook).
If a customer is claiming otherwise, you can:
1. Ask for original message source (that they would need to obtain from the person who sent them the message)
2. Test receiving message with identical message content sent to your own inbound address.
The second option may sound complicated, but in reality it is really easy to do. You can ask customer to email you (or email yourself) to the email address listed in your Inbound Stream Settings. If you want to take it a step further, you can set up an MX record for your custom domain (if you have one) just as a customer would:
Voila! You’ll immediately see a Retry delivery attempt in the Activity of your inbound Stream, and you’ll be check the Plain Text/HTML/Raw Source and JSON tab.
Since inbound is just another type of webhook, if you want to see how the actual payload looks, you’ll want to follow the process described below to set up a test webhook with Requestbin/Pipedrive: