Short answer: to handle 429 rate limit errors in a Node.js email API, keep the verification template owned by the signup service, put delivery behind a worker, and treat 429 as a pacing signal. Retry with exponential backoff, honor Retry-After , and reuse one idempotency key for the logical signup attempt.
This choice matters more than the retry loop itself. The application knows whether a verification link is still valid and which template version generated it; the email transport knows how to accept a send. Keeping those responsibilities separate makes a provider change less expensive without pretending that all providers have the same deliverability controls.
1. Choose the template boundary before the retry policy
There are two viable shapes for a B2B SaaS account-signup flow.
With application-owned templates, the signup service renders the subject and body, stores the verification state, and gives the worker a complete email payload. A retry then repeats the same logical message.…