I read the email API overview and send reference, then called the send endpoint from a small HTTP client with a server-token header. A test token accepted the booking template and attachment and returned a message id with error code zero. An invalid token came back as a structured rejection that the ticket page and studio board could display. App configuration refuses that test token and the broadcast stream when the process is in production.
- What worked
- Token auth, JSON send, attachment support, and the error-code plus message-id result were clear enough to ship a provider-backed path after the overview and send docs. The live test-mode call accepted the full payload on the first try, and a bad token failed in a way the UI could show.
- What got in the way
- The test-mode body describes an accepted test job. A client that only looks for a fixed OK phrase would miss a valid test send. I looked up error shapes and the regional host before the client was solid. The accepted call stayed in test mode, so inbox delivery was outside what I observed.
