Failure paths on demand
Use delivered, bounced, complained, and suppressed addresses when your app needs a specific delivery state.
Send to a simulator address and NoticeAPI writes back the outcome you asked for — through the same recipient timeline and signed webhooks your production code will read. No DNS to configure, no quota spent, no sender reputation on the line.
Use [email protected] with simulator recipients while production DNS is still untouched.
Address the message to delivered@, bounced@, complained@, or [email protected].
Fetch email status or listen for signed webhook events to verify your integration handled the outcome.
Mixed real and simulator recipients return mixed_simulation, so test cases cannot leak into production sends.
Each address produces one deterministic outcome you can assert against — and every one repeats the same way across local runs and CI.
Read simulator rulesCreate an accepted and delivered trail for happy-path assertions and webhook checks.
Exercise hard-bounce handling, webhook parsing, and retry decisions without poisoning a real address.
Trigger complaint-shaped events so your app can prove the abuse path before real recipient traffic.
Use delivered, bounced, complained, and suppressed addresses when your app needs a specific delivery state.
Add +labels for local runs, CI smoke tests, and webhook fixtures without creating cleanup work.
Simulator traffic stays out of quota, sender reputation, metrics, and autopilot health math.
Recipient events are recorded and signed webhook callbacks fire through the same handler path your app uses later.
Use simulator sends to prove request shape, recipient timelines, webhook parsing, and suppression handling. Production deliverability still starts with a verified sending domain and real recipient behavior.
No. It records delivery events and webhook callbacks inside NoticeAPI, but no message is delivered to a real mailbox.
No. The API returns mixed_simulation when simulator recipients and real recipients are in the same send. That keeps tests isolated.
Yes. Simulator addresses are deterministic and repeatable, making them useful for local development, CI smoke tests, and webhook handler tests.
No. Simulator events exercise suppression-shaped behavior without poisoning the simulator address or your account health.
Simulator outcomes are free. Move to a verified domain when the path is ready.