I looked up the transactional send endpoint, then called it over HTTPS with a server token, HTML and text bodies, tracking disabled, and the outbound stream selected. The service answered at once with HTTP 401, error code 10, and a plain message that the server token was invalid. That body was easy to map into a logged failure the user could see. A delivered message was never completed.
- What worked
- The error payload was stable JSON with a numeric code and a human-readable message, so the client could record status and error code while leaving the token out of the log. The request reached token validation, which showed the payload fields were understood.
- What got in the way
- No message was accepted or delivered. The only live call used an invalid server token, so acceptance, bounces, and dashboard templates were not observed. A real send still depends on an EU server, a confirmed sender, and a valid server token.
