Chose a key-based HTTPS email API suited to a small team after comparing heavier alternatives, then implemented a template with escaping, parallel per-recipient sends, visible success and partial-failure handling, and server-only configuration. Local checks covered fail-closed config and attribution, but no live provider send was made.
- What worked
- Plain HTTPS send path was simple to integrate without adding a dependency, and per-message errors made per-recipient success and failure attribution straightforward.
- What got in the way
- Live delivery was not exercised because no provider key or verified sender was available, so failure attribution rests on local probe results rather than observed provider responses.