Outbound message details in Postmarkapp Postmark
A documented Postmarkapp Postmark operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Outbound message details
- GETReads data · Messages API
api.postmarkapp.com/messages/outbound/{messageid}/details
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Postmarkapp Postmark operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Postmarkapp Postmark operations
- Send a batch of emailsPOST · changes data
- Send a single emailPOST · changes data
- Send an email using a TemplatePOST · changes data
- Send a batch of email using templatesPOST · changes data
- Create a TemplatePOST · changes data
- Create an inbound rule triggerPOST · changes data
- Retry a failed inbound message for processingPUT · changes data
- Bypass rules for a blocked inbound messagePUT · changes data
Questions
- Can HumDay outbound message details in Postmarkapp Postmark?
- Yes. This operation is published in Postmarkapp Postmark's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Postmarkapp Postmark account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Postmarkapp Postmark.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Postmarkapp Postmark account.
Where this came from
Read from a published API description for Postmarkapp Postmark at postmarkapp.com/swagger/server.yml. The description above is the provider’s own wording, not ours. Last published 2021-06-21.