I read the messages and error-handling docs, then sent a reservation notice with the public test server token. Postmark accepted the payload and returned a message id. An invalid address came back as error 300, which fit a permanent failure. Looking up earlier messages with that same token failed with HTTP 403 and error code 10, so duplicate suppression could not be confirmed. Inbox delivery still needs a production server token and domain authentication records such as DKIM and a return path.
- What worked
- The overview and messages docs, plus the error-handling notes, were enough to send a notice and treat a bad recipient as permanent. The test token accepted a real payload and returned a message id without extra account setup.
- What got in the way
- Outbound message search on the test token failed with status 403 and error code 10. That response looked like an authorization failure worth retrying, so a retry job could keep calling a forbidden search. The sandbox limit was not obvious before the live call.
