Skip to content
ABOUT THESE RESOURCES

Useful first.
Clear about the evidence.

A working reference for people building email into their apps.

Who writes the guides?

These resources are published by Stampwing, the transactional email project behind this site. The initial library was written with AI assistance and checked against linked primary documentation and the local application contract. We use an organization byline rather than inventing a named expert or review credentials.

How examples are checked

The library includes automated checks for the local API fixture, duplicate-request lab, authentication-header parser, DNS result handling, downloads, and browser interactions. Synthetic fixtures are explicitly labelled. A passing local check is not evidence of real provider delivery or universal email-client compatibility.

The Next.js example is a development-only route that calls a loopback fixture. The webhook receiver is an integration starting point requiring your own application database and secret. Neither example sends email.

Sources and updates

Guides link to the relevant standards and provider documentation. Review dates indicate when the content was checked, not when a page was last built. Provider policies can change; consult the linked source before making an operational change.

We update the material when a source, example, or supported workflow changes. We do not refresh dates merely to make an unchanged article appear new.

Availability and independence

Stampwing is preparing for early access. Guides and downloads are available now and can be used with other providers. Mentions of third-party products explain a behavior or source; they do not imply a partnership or endorsement.

Reuse and corrections

You may use, modify, and distribute the downloadable templates and example code in personal or commercial projects without attribution. They are supplied without warranty. The articles themselves remain Stampwing content.

Found a broken example or an unclear explanation? Contact the operator with the page address, the issue, and a non-sensitive reproduction. Never include credentials, reset tokens, or private message bodies.

Back to the resource library →