Password-reset mail went out through Postmark's email API as one HTTPS POST with a server token, a transactional stream, a tag, and link tracking disabled. The email API and overview docs were enough to shape the payload and error handling without an SDK. The official test token accepted that payload from a direct client call and again from the production server action, each time returning a message id. The test token does not deliver, so inbox and bounce behavior was not observed.
- What worked
- A single authenticated POST matched a one-process app. The test token checked the exact payload and returned a message id, which was enough to confirm the production action path reached the API.
