Courier
Notification infrastructure with visual journeys.
Courier blends notification infrastructure with marketing-style journeys. Visual template builder, drop-in inbox UI, native Slack and Teams routing. Bridges product notifications and customer engagement.
Judged purely as an API. What the request contract guarantees on retry, how complete the webhook event coverage is, whether suppressions are readable and writable programmatically, and how much the message log retains when something needs debugging in production.
Against high-frequency programmatic sends where a missed delivery is a product failure, Courier covers webhook coverage, event stream, the suppressions API, batch sending, and SDK breadth, and does not cover idempotency keys and operating track record. Whether that gap matters depends on how central those are to the build.
- Idempotency keys: No
- Webhooks: Yes
- Event stream: Yes
- Operating since: 2019
- Suppressions API: Yes
- Best published rate per 1,000: Tiers not published in comparable form
- Batch sending: Yes
- SDKs: node, python, go, ruby, php, java
- Deliverability: Inherits providers you connect.
Inherits providers you connect.
Teams that need both product notifications and marketing-style journeys.
- › Visual journey editor
- › Native Slack/Teams routing
- › Drop-in inbox component
- › Less code-first than Knock
- › Pricing climbs with volume
Features at a glance
| API | Yes |
| SMTP | No |
| SDKs | node, python, go, ruby, php, java |
| Webhooks | Yes |
| Templates | rich |
| React Email | No |
| Batch send | Yes |
| Scheduled send | Yes |
| Suppressions | Yes |
| Multi-tenant | Yes |
| Inbound parsing | No |
| Event stream | Yes |
| Idempotency keys | No |
| Dedicated IP | No |