Courier

• List Messages — List messages you've previously sent. Filter by status, recipient, notification, provider, tags, or tenant.
• Get Message — Get the full details and status of a single message by its ID.
• Get Message Content — Get the rendered content (HTML, text, subject) of a previously sent message.
• Get Message History — Get the event history for a message, showing each step in the delivery pipeline (enqueued, sent, delivered, etc.).
• List Notifications — List notification templates. Optionally filter by cursor.
• Get Notification Content — Get the published content blocks of a notification template.
• Get Notification Draft Content — Get the draft (unpublished) content blocks of a notification template.
• Create Notification — Create a V2 notification template. name is required. Content may be provided inline or set separately afterwards. A newly created template is a draft; making it live is a separate step this tool cannot perform. Link a routing strategy via notification.routing.strategy_id to control which channels are used. Example: { notification: { name: 'welcome-email', tags: [], brand: null, subscription: null, routing: { strategy_id: 'rs_01abc' }, content: { version: '2022-01-01', elements: [] } } }.
• Get Notification — Retrieve a notification template by ID. Optionally request draft, published, or a version such as v001.
• Replace Notification — Replace a notification template entirely (full document PUT). The template stays a draft; making it live is a separate step this tool cannot perform.
• Put Notification Content — Replace the elemental content of a V2 notification template. Overwrites all elements. Use channel elements to target specific channels. Multi-channel example: elements: [{ type: "channel", channel: "email", elements: [{ type: "meta", title: "Hello" }, { type: "text", content: "Email body" }] }, { type: "channel", channel: "push", elements: [{ type: "meta", title: "Hello" }, { type: "text", content: "Push body" }] }, { type: "channel", channel: "inbox", elements: [{ type: "text", content: "Inbox
• Put Notification Element — Update a single element within a V2 notification template. The template stays a draft; making it live is a separate step this tool cannot perform.
• Put Notification Locale — Set locale-specific content overrides for a V2 notification template. Each element override must reference an existing element by its id. Example for Spanish locale: { notification_id: "nt_01abc", locale_id: "es", elements: [{ id: "elem_meta_1", title: "Restablecer contraseña" }, { id: "elem_text_1", content: "Haga clic en el enlace para restablecer su contraseña." }] }. The template stays a draft; making it live is a separate step this tool cannot perform.
• List Providers — List configured provider integrations for the workspace.
• Get Provider — Fetch a single provider configuration by ID.
• Get Routing Strategy — Retrieve a routing strategy by ID. Returns the full entity including routing, channels, and providers.
• Create Journey — Create a new journey. Always created as a draft; making it live is a separate step this tool cannot perform. Send two nodes: the trigger, and an exit node last. Both are required — a create with no exit node is rejected, and the API reports that as "exit node must be the last node in the journey" even when no exit was sent at all. Send and delay nodes are added afterwards by replace_journey, once journey-scoped templates exist. Node ids are server-generated; do NOT include an id field. Example:
• Get Journey — Get a journey by ID. Pass version=draft to retrieve the working draft, or version=vN for a historical version. Defaults to published.
• Replace Journey — Replace (update) a journey draft. Full document replacement — include all nodes and properties in the body, the trigger included; anything omitted is deleted. The journey stays a draft; making the change live is a separate step this tool cannot perform. This is where send, delay, branch and exit nodes are added, and send node template IDs must already be scoped to this journey. The result carries a "verification" object read back from the server after the write — check it every time. verified:tr
• Create Journey Template — Create a notification template scoped to a journey. Always created as a draft; making it live is a separate step this tool cannot perform. The template can then be referenced in journey send nodes. content.elements must be wrapped in a channel block — the API rejects bare elements. Example: { journey_id: "j-abc", channel: "email", notification: { name: "Welcome Email", tags: [], brand: null, subscription: null, content: { version: "2022-01-01", elements: [{ type: "channel", channel: "email", ele
• Put Journey Template Content — Replace the elemental content of a journey-scoped notification template. Overwrites all elements. The template stays a draft; making it live is a separate step this tool cannot perform.
• Put Journey Template Locale — Set locale-specific content overrides for a journey-scoped notification template. Each element override must reference an existing element by its id. The template stays a draft; making it live is a separate step this tool cannot perform.
• List Journeys — List journey templates in the workspace, returning the journey IDs and version state of each. Optionally filter by version (published or draft).
• List Journey Templates — List notification templates scoped to a journey. Journey-scoped templates can only be used by send nodes within the same journey. Call this to discover template IDs before wiring send nodes in replace_journey.
• Get Journey Template — Get a journey-scoped notification template by notification ID. Pass version=draft to retrieve the working draft (required before the template has been published). Defaults to published.

Showing the first 25 tools — full list and schemas: Directory API.