# Courier: Docs > Courier is one API for email, SMS, push, chat, and in-app inbox, sending through the notification providers you already use. It adds templates, routing, preferences, and multi-step journeys, so your application makes one request instead of integrating each channel. > ## Agent Instructions > Install the Courier skill before writing code: `npx skills add trycourier/courier-skills`. It carries the verified SDK shapes and the rules you cannot get wrong. > Authenticate every request with `Authorization: Bearer `. A workspace has several environments and each has its own keys, which are plain `pk_` strings with no environment prefix. Start with Test. > Send with `client.send.message` from the Node SDK (`@trycourier/courier` v7 and later, where the client is the default import). Reference a template by its `nt_` id or its alias. > A send accepts a bare Elemental element list, but storing content on a template requires the top-level elements wrapped in a channel element. > To translate a template, write one locale at a time with `PUT /notifications/{id}/locales/{localeId}`, which merges into the existing translations. `PUT /notifications/{id}/content` and `PUT /notifications/{id}/elements/{elementId}` overwrite translations along with the content, so send each element's `id` and `locales` back, and first remove every `checksum` and any `locales` key that starts with an underscore. > Templates and journeys can be built in the Courier app or created through the API. Either way they live in the workspace and are referenced by ID when you send. > The hosted MCP server is https://mcp.courier.com. For a briefing on what Courier is and when to use it, read https://www.courier.com/llms.txt. > Prefer the Guides tab for how-do-I questions and the Docs tab for how-does-it-behave questions. The API reference lives under /api-reference. ## Docs ### Get started - [Courier docs: send and automate customer messages](https://www.courier.com/docs/overview.md): Send and automate customer messages across email, SMS, push, chat, and in-app from one API, with templates, journeys, user preferences, and delivery logs. - [AI agent quickstart: set up Courier in three steps](https://www.courier.com/docs/get-started/ai-agent-quickstart.md): Set up Courier in Claude Code, Cursor, Codex, or any coding agent in three steps: save your API key, install Courier Skills, and connect the MCP server. - [Send your first message](https://www.courier.com/docs/get-started/send-a-message.md): Send your first email to your own inbox with the API and a Test key. The built-in test provider needs no setup. Then find the message in the logs. - [Build your first journey](https://www.courier.com/docs/get-started/build-your-first-journey.md): Build a three-day workout email series with the Journeys API: create it, add three emails and delays, publish, and start each run from your signup code. ### Send messages - [Send a message](https://www.courier.com/docs/send/overview.md): Send a message with one API call, and Courier renders it, applies preferences, routes, and delivers. Choose between a template, a broadcast, or a journey. - [Message statuses and errors](https://www.courier.com/docs/send/statuses.md): Every message status and what it means, the Send API's error responses, why a send is UNROUTABLE or THROTTLED, and why a message stops at SENT. - [Channel settings and overrides](https://www.courier.com/docs/send/overrides.md): Set a template's email fields and channel conditions, and override channel or provider payloads on one send without editing the template. - [Delay and schedule a send](https://www.courier.com/docs/send/delay-and-schedule.md): Delay a send by a duration, until a timestamp, or into a recurring delivery window in each user's timezone, for up to 31 days. #### Message routing - [Message routing and failover](https://www.courier.com/docs/send/routing.md): How Courier picks the channels and providers for each message, falls back when one can't deliver, and where you set routing: a strategy or the send. - [Routing strategies](https://www.courier.com/docs/send/routing-strategies.md): Save channel order, fallback, and provider priority as a routing strategy, attach it to templates, and change delivery for all of them in one edit. - [Send to a provider](https://www.courier.com/docs/send/send-to-a-provider.md): Send through one specific provider by naming it in routing instead of a channel, when that's worth it, and what you give up: failover and channel priority. #### Push messages - [Push notifications](https://www.courier.com/docs/send/push/overview.md): How push device tokens are stored on the user and synced by the Courier mobile SDKs, plus setToken, notification permissions, and iOS foreground display. - [Push payloads](https://www.courier.com/docs/send/push/custom-data.md): Attach one data object to a push for FCM, APNs, and Expo, then read it on iOS, Android, React Native, and Flutter, deep-link on tap, or send with no alert. ### Journeys - [Journeys](https://www.courier.com/docs/journeys/overview.md): Multi-step flows that run once per user when triggered, with sends, delays, and branches, and when to pick a journey over a single Send API call. - [Build a journey](https://www.courier.com/docs/journeys/build.md): Build a journey in the canvas or as JSON over the API, give each send node its own scoped template, publish the templates and the journey, then invoke it. - [Journey experiments](https://www.courier.com/docs/journeys/experiments.md): A/B test 2 to 10 template variants at one send node. Traffic splits by weight, recipients keep their variant, and you compare opens and clicks per variant. - [Invoke a journey](https://www.courier.com/docs/journeys/invoke.md): Start a journey run from the API with an idempotency key, find it by run ID, and cancel one run or every run that shares a cancellation token. #### Nodes - [Journey nodes](https://www.courier.com/docs/journeys/nodes.md): The nodes on a journey canvas: send, branch, delay, digest, batch, AI, fetch data, throttle, and cancel, plus when to pick Digest over Batch. - [Journey send node](https://www.courier.com/docs/journeys/nodes/send.md): Send on one channel from a journey template, with conditions, recipient overrides, a send window, Slack and Teams addressing, or an A/B experiment. - [Journey branch node](https://www.courier.com/docs/journeys/nodes/branch.md): Split a journey into paths by conditions on data, profile, tenant, or an earlier send's status. The run takes the first matching path, or the default. - [Journey delay node](https://www.courier.com/docs/journeys/nodes/delay.md): Pause a journey run for a duration or until a timestamp before the next node, with the value set on the node or read at runtime from a context field. - [Journey digest node](https://www.courier.com/docs/journeys/nodes/digest.md): Add the run's event to a subscription topic's digest, released on the user's schedule. The topic holds the schedule, categories, and template mapping. - [Journey batch node](https://www.courier.com/docs/journeys/nodes/batch.md): Collect events at one point in a journey and release them as a single per-user payload when max items, a quiet window, or the max wait period is reached. - [Journey AI node](https://www.courier.com/docs/journeys/nodes/ai.md): Run an OpenAI or Anthropic model prompt in a journey and store its structured output under data.ai_result. Runs on AI credits, in the US datacenter only. - [Journey fetch data node](https://www.courier.com/docs/journeys/nodes/fetch-data.md): Call an external HTTPS endpoint mid-run and merge the JSON response into the context, with templated variables, four merge strategies, and a 10s timeout. - [Journey throttle node](https://www.courier.com/docs/journeys/nodes/throttle.md): Limit how often a user, or everyone, passes a point in the journey within a time window. A run over the limit skips the node and continues without sending. - [Journey cancel node](https://www.courier.com/docs/journeys/nodes/cancel.md): Stop in-flight journey runs from inside a flow with a Cancel node, by run ID or by a cancellation token built from run data like an order or user ID. #### Automations (Legacy) - [Automations (Legacy)](https://www.courier.com/docs/journeys/automations/overview.md): The previous workflow product. Existing automations keep running and new workflows belong in Journeys. Covers its triggers, action nodes, and control flow. - [Automation Designer](https://www.courier.com/docs/journeys/automations/designer.md): Build an automation in the visual designer with a trigger and action nodes, review the diff on publish, and invoke it from the Invoke tab or the API. - [Automation Steps](https://www.courier.com/docs/journeys/automations/steps.md): Field and schema reference for each step in an ad hoc automation API request, from add-to-batch and delay to fetch data, send list, and update profile. - [Automation Batching](https://www.courier.com/docs/journeys/automations/batching.md): Collect automation events and release them as one message after a quiet period, a max wait, or a max item count, scoped globally, per user, or by key. - [Automation Digests](https://www.courier.com/docs/journeys/automations/digest.md): Collect events with an Add to Digest node and release them through a second automation with a Digest trigger, on schedules set on a preferences topic. - [Automation Throttling](https://www.courier.com/docs/journeys/automations/throttle.md): Cap how many automation-triggered messages a user or group receives in a time window, scoped by user ID, globally, or by a dynamic run context key. - [Automation Fetch Data](https://www.courier.com/docs/journeys/automations/fetch-data.md): Call your HTTPS endpoint with GET or POST mid-run and merge the response into the run context, with bearer, basic, or API key auth and a 10-second timeout. - [Automation Get Profile](https://www.courier.com/docs/journeys/automations/get-profile.md): Load a recipient's stored profile into the run context mid-run. Audience and schedule triggers don't load it, so add this step before profile conditions. - [Dynamic Automation Steps](https://www.courier.com/docs/journeys/automations/dynamic.md): Read run data through the refs object, map payload fields to template variables in a send node, and interpolate values into Fetch Data URLs. - [Automation Conditional Logic](https://www.courier.com/docs/journeys/automations/control-flow.md): Branch an automation run with If and Switch nodes that compare data or profile fields, check an earlier send's status, or evaluate a JavaScript expression. - [Cancel an Automation Run](https://www.courier.com/docs/journeys/automations/cancel.md): Stop a scheduled or in-flight automation run with a cancellation token and a Cancel Automation node, or with the cancel button in automation logs. - [Automation Debugger](https://www.courier.com/docs/journeys/automations/debugger.md): Run a saved test event through an automation and select each node to see the data it received, including the profile a GET Profile node fetched. - [Automation Scheduling](https://www.courier.com/docs/journeys/automations/scheduling.md): Invoke an automation on a one-time date, a recurrence rule, or a cron expression. Publishing the template activates the schedule, with no API call needed. - [Automations with Segment](https://www.courier.com/docs/journeys/automations/segment.md): Trigger an automation from a Segment track event, with a checkout example that delays a reminder and cancels it by user ID once the purchase completes. - [Inbound Events](https://www.courier.com/docs/journeys/automations/inbound-events.md): Post an event to Courier over the inbound track API or CourierJS to start an automation, or ingest Segment and RudderStack track and identify calls. - [Automation Webhook Trigger](https://www.courier.com/docs/journeys/automations/webhook-trigger.md): Start an automation from a Courier inbound webhook. Payloads up to 6 MB are accepted, a JSON array starts one run per object, and userId loads the profile. - [Automation Audience Trigger](https://www.courier.com/docs/journeys/automations/audience-trigger.md): Start an automation run for each user who enters or leaves a dynamic audience. Runs carry only the user ID, so add GET Profile to read profile fields. ### Broadcasts - [Broadcasts](https://www.courier.com/docs/broadcasts/overview.md): Send one message to a whole list or audience, now or on a schedule. Each broadcast uses one channel and suits newsletters, launches, and policy updates. - [Send a broadcast](https://www.courier.com/docs/broadcasts/send.md): Create, schedule, and send a broadcast from the console or the API: pick a channel, write the content, choose a list or audience, and send now or later. ### Design - [Design notifications](https://www.courier.com/docs/design/overview.md): Templates, brands, and the Elemental format define what a notification says and looks like. Your customers can design their own in the embedded designer. - [Brands](https://www.courier.com/docs/design/brands.md): Apply one logo, color set, header, and footer to every template you send. Restyle emails with c-- CSS classes, and set a brand per send or tenant. #### Templates - [Templates](https://www.courier.com/docs/design/templates/overview.md): What a template holds (content, channels, routing, brand, and translations), how drafts and published versions work, and how to send it by ID or alias. - [Design Studio](https://www.courier.com/docs/design/templates/design-studio.md): Build a template in the visual editor: drag blocks onto the canvas, write per-channel content, add variables and translations, then preview and publish. - [Design Studio template settings](https://www.courier.com/docs/design/templates/template-settings.md): Every template setting in Design Studio: name, ID, alias, subscription topic, message tags, send conditions, and per-channel provider options. - [Design Studio block settings](https://www.courier.com/docs/design/templates/blocks.md): Every setting on each Design Studio block, with its type and default: text, heading, button, divider, spacer, image, list, column, blockquote, and more. - [Template variables and Handlebars helpers](https://www.courier.com/docs/design/templates/variables.md): Personalize a template with variables from send data, profile, and tenant fields, plus Handlebars helpers for logic, formatting, and whitespace. - [Manage templates with the API](https://www.courier.com/docs/design/templates/api.md): Create, read, update, and publish templates over the REST API with a draft lifecycle, and manage them as code from Git, the CLI, or an MCP agent. - [Edit email HTML directly](https://www.courier.com/docs/design/templates/html-email.md): Edit a template's email HTML by hand and make it render in Gmail, Outlook, and Apple Mail, with inline CSS, table layouts, and MSO conditionals. - [Device Preview for email](https://www.courier.com/docs/design/templates/device-preview.md): Render a template on real email clients and devices from the editor or the API, get a screenshot of each, and preview HTML you already have. - [Data mapping for push and inbox](https://www.courier.com/docs/design/templates/data-mapping.md): Choose which send data fields reach a push or inbox message on legacy templates. Design Studio templates already pass the full data object through. - [Classic Designer (Legacy)](https://www.courier.com/docs/design/templates/classic-designer.md): Classic Designer is the editor that came before Design Studio. Its templates keep sending with the same ID and alias, and there's no migration step to run. #### Elemental - [Elemental control flow](https://www.courier.com/docs/design/elemental/control-flow.md): Add if, loop, ref, and channels to any element to render on a condition, repeat over an array, check another element's visibility, or target channels. - [Template translations](https://www.courier.com/docs/design/elemental/locales.md): Localize a template by syncing translations from your translation tool over the API, or with AI in Design Studio. Each recipient gets their language. - [Email template fonts](https://www.courier.com/docs/design/elemental/fonts.md): Set an email font in Design Studio or with font_family from 70 fonts (10 web-safe, 60 Google Fonts), and see which email clients load Google Fonts. ##### Elements - [Elemental](https://www.courier.com/docs/design/elemental/overview.md): The JSON format behind every template, the elements Courier renders on each channel, and why a stored template needs channel wrapping that a send does not. - [Elemental text element](https://www.courier.com/docs/design/elemental/elements/text.md): Render body text and headings with bold, italic, color, and alignment, plus inline links and images. Translate formatted text and keep its styling. - [Elemental action element](https://www.courier.com/docs/design/elemental/elements/action.md): Add a button or link with a label and href. Pick a button, secondary, tertiary, or link style, and see how each renders on email, Inbox, and Slack. - [Elemental channel element](https://www.courier.com/docs/design/elemental/elements/channel.md): Set different content per channel in one document, with Elemental elements or raw formats like MJML, Slack blocks, or webhook payloads. - [Elemental meta element](https://www.courier.com/docs/design/elemental/elements/meta.md): Set the title that becomes the email subject, push title, and Inbox title. It takes Handlebars variables, per-channel titles, and translations. - [Elemental image element](https://www.courier.com/docs/design/elemental/elements/image.md): Embed an image with width, alignment, alt text, border, and an optional link, and swap the image URL per locale. Renders on email, push, and Inbox. - [Elemental divider element](https://www.courier.com/docs/design/elemental/elements/divider.md): Render a horizontal rule between content sections, with color, border width, and padding. It renders on email and Inbox, and SMS skips it. - [Elemental group element](https://www.courier.com/docs/design/elemental/elements/group.md): Wrap several elements so one if or loop condition applies to all of them. Nest groups, or show the whole set on chosen channels only. - [Elemental columns element](https://www.courier.com/docs/design/elemental/elements/columns.md): Lay out content side by side in columns, each with its own width and styling, plus container borders, gap spacing, and vertical alignment. - [Elemental list element](https://www.courier.com/docs/design/elemental/elements/list.md): Render ordered or unordered lists, nested up to five levels, from your data. Loop over arrays at any level, link items, or use a custom bullet image. - [Elemental quote element](https://www.courier.com/docs/design/elemental/elements/quote.md): Render a quote block for testimonials or callouts, with alignment, border color, and text styles. It supports Handlebars variables and locale translations. - [Elemental comment element](https://www.courier.com/docs/design/elemental/elements/comment.md): Add notes to an Elemental template that never render on any channel. Document template logic, label sections, or attach an object of structured metadata. - [Elemental HTML element](https://www.courier.com/docs/design/elemental/elements/html.md): Embed raw HTML when no other element produces the structure you need. It renders on email only and supports Handlebars variables and translations. - [Elemental Jsonnet element](https://www.courier.com/docs/design/elemental/elements/jsonnet.md): Generate Elemental content at render time with a Jsonnet template, using variables, functions, conditionals, and loops to build structured JSON. #### Embedded designer - [Courier Create](https://www.courier.com/docs/design/embedded-designer/overview.md): Mount Courier Create's template and brand editors in your React app with a tenant-scoped JWT, so customers design their own notifications. - [Courier Create template editor](https://www.courier.com/docs/design/embedded-designer/template-editor.md): Mount TemplateEditor in your React app, restrict channels, offer variables, control auto-save, render it in a modal, and publish from your own button. - [Courier Create brand editor](https://www.courier.com/docs/design/embedded-designer/brand-editor.md): Let a tenant edit its logo, colors, and email footer with BrandEditor and BrandProvider. Scope the token for brand writes and publish the brand on its own. - [Tenant Templates API](https://www.courier.com/docs/design/embedded-designer/api.md): Read, write, publish, and version a tenant's templates with the endpoints Courier Create uses, with your API key on the server or a tenant-scoped JWT. ### In-app - [In-app Inbox](https://www.courier.com/docs/in-app/inbox.md): Add a real-time notification center to your web and mobile apps. Courier hosts the feed, and you choose how much of the UI you build. - [Toasts](https://www.courier.com/docs/in-app/toasts.md): Pop up new inbox messages the moment they arrive, so users notice them while working in your app. Toasts share the inbox feed, so you send nothing extra. - [Preference center](https://www.courier.com/docs/in-app/preference-center.md): Let users choose which notifications they get, and on which channels, in your app or on a page Courier hosts. Courier enforces their choices on every send. ### Recipients - [Users and profiles](https://www.courier.com/docs/recipients/overview.md): Save a user's email, phone, and chat details on a profile, then send by user_id. Covers each channel's fields, push tokens, and merge, replace, or patch. #### Lists & audiences - [Lists and audiences](https://www.courier.com/docs/recipients/lists-and-audiences/overview.md): Address a group instead of naming each person: a list you curate by hand, or an audience Courier keeps current from rules. Compare the two and pick one. - [Lists](https://www.courier.com/docs/recipients/lists-and-audiences/lists.md): Hand-picked groups of users, like beta testers, addressed with list_id. Covers dotted list IDs, wildcard patterns across many lists, and tenant scoping. - [Audiences](https://www.courier.com/docs/recipients/lists-and-audiences/audiences.md): Rule-based groups that update as profiles change, addressed with audience_id. Filter on profile fields, nest AND and OR rules, and scope sends to a tenant. #### Preferences - [Notification preferences](https://www.courier.com/docs/recipients/preferences/overview.md): How Courier decides at send time whether a user gets a message and on which channels, layering topic defaults, tenant defaults, and the user's own choices. - [Subscription topics and sections](https://www.courier.com/docs/recipients/preferences/model.md): How preferences are modeled as topics in sections, each with a default state and optional channel routing, and which API reads and writes each part. - [Preferences Editor](https://www.courier.com/docs/recipients/preferences/preferences-editor.md): Define subscription topics, sections, defaults, and channel selection in the Preferences Editor, brand the preference page, and map templates to topics. - [Manage user preferences with the API](https://www.courier.com/docs/recipients/preferences/api.md): Read and update a user's topic opt-ins and channels, globally or for one tenant, from your backend or a client SDK. Import them in bulk and track changes. ### Tenants - [Tenants](https://www.courier.com/docs/tenants/overview.md): Model each customer organization as a tenant with its own brand, preference defaults, templates, and properties, then name it on a send to apply them all. - [Tenant context](https://www.courier.com/docs/tenants/context.md): How a tenant's brand, preferences, templates, and properties apply when a send names it, plus parent inheritance, brand order, and tenant auto-infer. - [Send with a tenant](https://www.courier.com/docs/tenants/send.md): Send to a user or a whole tenant with tenant_id, fan out across a tenant hierarchy, handle users in several tenants, and group delivery data by customer. - [Tenant templates](https://www.courier.com/docs/tenants/templates.md): Give one customer its own version of a template. Create, publish, and delete tenant templates over the API, then send them with the tenant/ prefix. - [Tenant default preferences](https://www.courier.com/docs/tenants/preferences.md): Set each topic's starting status for everyone in a tenant, in the console or with the API. Users can still change their own unless the topic is REQUIRED. ### Monitoring - [Monitoring your messages](https://www.courier.com/docs/monitor/overview.md): Look up any message, see how templates and journeys perform, track opens and clicks, and send delivery events to your own systems. - [Message and journey logs](https://www.courier.com/docs/monitor/logs.md): Every message and journey run in one place: delivery status, timeline, rendered content, and why it failed. Search the dashboard or use the API or MCP. - [Template, journey, and broadcast analytics](https://www.courier.com/docs/monitor/analytics.md): See how many messages were sent, delivered, opened, and clicked for each template, journey, and broadcast, and how those rates change over time. - [Metrics API](https://www.courier.com/docs/monitor/template-metrics.md): Get a template's delivery funnel as a time series by provider and channel over the REST API. Set the window and bucket size within your plan's limits. - [Open and click tracking](https://www.courier.com/docs/monitor/tracking.md): How Courier tracks opens and clicks on email, push, and Inbox, how to skip tracking on a link or opens on a send, and how to add a custom tracking domain. - [Observability](https://www.courier.com/docs/monitor/observability.md): Send Courier delivery metrics and logs to Datadog, New Relic, or any OpenTelemetry endpoint, then chart and alert on delivery health in the tool you use. #### Webhooks - [Outbound webhooks](https://www.courier.com/docs/monitor/webhooks/outbound.md): Get a signed POST at your endpoint every time a message changes status, a user changes a preference, or a template or audience changes. - [Inbound webhooks](https://www.courier.com/docs/monitor/webhooks/inbound.md): Point a third-party system's webhooks at a Courier URL to start journeys from its events, with no API key. Covers payloads, userId, and the 6 MB cap. - [Webhook event types](https://www.courier.com/docs/monitor/webhooks/events.md): Every event an outbound webhook sends, for message status, template, audience, and preference changes, with when each one fires and an example payload. - [Verify webhook signatures](https://www.courier.com/docs/monitor/webhooks/security.md): Verify the courier-signature header on outbound webhooks: an HMAC-SHA256 of the timestamp and raw body with your whsec_ secret, compared in constant time. ### Workspaces - [Workspaces](https://www.courier.com/docs/workspaces/overview.md): Courier's top-level container for brands, providers, templates, API keys, and users, and how to choose between a workspace, an environment, and a tenant. - [Environments and API keys](https://www.courier.com/docs/workspaces/environments.md): Production, Test, and custom environments with separate API keys, templates, and logs, and how to migrate templates between them. - [Team access, roles, and SSO](https://www.courier.com/docs/workspaces/team-access.md): Invite teammates, set up Google, GitHub, or Okta SSO and SCIM, and on Enterprise, assign built-in or custom roles that control what each sees in logs. - [Security: how Courier protects your data](https://www.courier.com/docs/workspaces/security.md): How Courier protects your notification data, and the controls you use to secure your workspace: SSO, roles, audit trail, API keys, and signed webhooks. - [Compliance: SOC 2, HIPAA, GDPR, and data requests](https://www.courier.com/docs/workspaces/compliance.md): Courier's SOC 2 Type II, HIPAA, PCI DSS, GDPR, and CCPA programs, where to get the reports, and how to answer data access and deletion requests. - [Regional datacenters: US and EU](https://www.courier.com/docs/workspaces/datacenters.md): Courier runs separate US and EU datacenters. Send EU users' notifications through the EU datacenter to keep their data in Europe for data residency. - [Audit trail](https://www.courier.com/docs/workspaces/audit-trail.md): A log of API key rotations, role changes, publishes, and integration edits, with who and when. Review it in the console or through the Audit Events API. - [Billing: sends, AI credits, and device previews](https://www.courier.com/docs/workspaces/billing.md): What Courier bills for: message sends, AI credits, and the Device Preview add-on. Plan pricing, how each one is counted, and common billing questions. ### Resources - [Postman collection](https://www.courier.com/docs/resources/postman.md): Try every Courier endpoint in Postman with the official collection: fork it, add bearer auth, and keep your Test key in an environment variable. - [Glossary](https://www.courier.com/docs/resources/glossary.md): Courier terms defined in plain language, plus the thirteen prefixes on IDs Courier generates, such as nt_ for templates, and the resource each one names. - [Support and status](https://www.courier.com/docs/resources/help.md): Reach Courier support by email, check service status, read the changelog, and find security reports. Business plans add chat, and Enterprise adds an SLA.