TL;DR: The simplest welcome-email API is the one that lets your application own the recipient state and the message template while exposing trustworthy delivery events. In a healthtech system, send the welcome message through a narrow adapter, record the provider message ID, and treat a permanent bounce as a state transition that suppresses future sends. Keep templates versioned in your repository unless non-engineers genuinely need an independently governed editing workflow.
A welcome email looks harmless. In a patient portal, it is attached to an account that may contain a typo, a shared clinic address, or an address that must not receive protected information. The delivery decision is therefore larger than choosing an endpoint that accepts JSON.
The operational constraint changes the answer: a send request must be easy, but recipient suppression must be harder to bypass.…