Email Sandbox Testing Guide & Simulator Addresses

Recipients at simulator.noticeapi.com run your integration through the real event pipeline: recipient events are recorded, your webhooks fire, suppression handling is exercised, but nothing touches a real mailbox, nothing counts against your quota, and your sender reputation is never at risk.

For the product overview, read the email sandbox simulator guide.

terminal
curl -X POST https://www.noticeapi.com/api/v1/email/send \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "demo@sandbox.noticeapi.com",
    "to": "bounced+order-42@simulator.noticeapi.com",
    "subject": "bounce test",
    "text": "test"
  }'

# → { "ok": true, "provider": "noticeapi_simulator",
#     "simulation": { "bounced": 1 } }

Addresses

delivered@simulator.noticeapi.comRecords a delivered event; webhook email.delivered.
bounced@simulator.noticeapi.comSimulates a hard bounce (550 5.1.1); webhook email.bounced.
complained@simulator.noticeapi.comSimulates a spam complaint; webhook email.filteredspam.
suppressed@simulator.noticeapi.comSimulates a provider suppression; webhook email.suppressed.

Rules worth knowing

Add +labels freely (bounced+order-42@…). Simulator recipients can't be mixed with real recipients in one send (mixed_simulation, 422). Simulated bounces never suppress the simulator address, so your tests stay repeatable. Simulated traffic is excluded from Metrics and from the autopilot's health math.