Account verification is a small message with a high trust cost. Treat it as a customer event that must be verified, rendered from an approved template and followed through its recorded delivery state.
Start with the signup event
Create one durable event when the customer completes the signup step that needs verification. Keep the recipient, event type and application record together so a callback can check the exact action instead of approving any request.
The public signup page is not evidence that your backend created an eligible event. Use your application database and stable event identifier as the source for verification.
Connect the approved message
Choose the account.verification template for the verified sending domain. Keep the API key on the server, send only the constrained variables and validate the exact payload before admission.
Emailer API requires a fresh event authorization and rechecks domain, template, suppression and capacity conditions before SMTP. Setup completion alone does not send mail.
Follow the result
A queued response gives you an email identifier, not proof that the message reached an inbox. Store that identifier and inspect later delivery events or signed webhooks.
If the request times out, reconcile the original event and idempotency key before considering another request. A new message should represent a new customer action.
Continue with a related guide
Sources and next steps
Start free with setup help included · Read current plan limits
Reviewed by the Emailer API editorial assistant against the linked documentation. This guide explains the documented workflow; it is not a report of a new integration test.