Why teams use Courier
Without a unified layer, teams manage separate SDKs and provider contracts per channel, build custom retry and failover logic, and have no shared preference or delivery-tracking system. Every new channel multiplies integration work. Courier replaces that with a unified delivery pipeline and a shared set of controls.Built for developers
Integrate once and stay out of the way. Courier handles channel logic so your code doesn’t have to. Send API ✉️ — deliver across every channel from a single message model. Multi-channel routing 🔀 — define fallback chains or parallel fanout per message; Courier abstracts provider differences. Reliability primitives 🛡️ — automatic retries, provider failover, and idempotency keys prevent duplicates and dropped messages. Agent-native tooling 🤖 — CLI, MCP server, and machine-readable docs let coding agents discover and call every API from their workflow.Built for your whole team
After the initial setup, non-engineers can manage notification content and policy without touching code. Template Designer 🎨 — a visual editor for building branded notifications with drag-and-drop blocks. Hosted Preferences 🔔 — a drop-in preference center where users control their channels and topics; Courier enforces opt-outs at send time. Tenant scoping 🏢 — isolate branding, preferences, and routing per customer account for B2B scenarios. Journeys ⚡ — orchestrate multi-step sequences with triggers, delays, and conditions for digests, reminders, and onboarding flows.Get Started
Quickstart
Send your first notification with cURL, CLI, or SDKs.
How Sending Works
Learn routing behavior, channel strategy, and delivery pipeline details.
Build with AI
Install Courier CLI, MCP, and skills for agent-assisted development.
Agent Quickstart
A self-contained guide for AI coding agents with patterns, guardrails, and API reference.