Courier

Showing 25 of 144 from the live probe.

• 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.

• 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.

• List Preference Sections

  List the workspace's preference sections. Each section embeds its topics.

• 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. Example: { journey_id: "j-abc", channel: "email", notification: { name: "Welcome Email", tags: [], brand: null, subscription: null, content: { version: "2022-01-01", elements: [{ type: "text", content: "Hello!" }] } } }. The result carries a "verification" object confirming the new id is really presen

• 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.

• Get Audience

  Get an audience by its ID, including its filter definition.

• List Audience Members

  List all members of an audience.

• List Audiences

  List all audiences in the workspace.

• Update Audience

  Create or update an audience with a filter definition.

• Delete Audience

  Delete an audience by its ID.

• Get Audit Event

  Get a specific audit event by its ID.

• List Audit Events

  List audit events in the workspace. Useful for tracking API usage and changes.

• Generate Jwt For User

  Generate a JWT authentication token for a user. Used for client-side SDK auth (Inbox, Preferences, etc.).

• Invoke Automation Template

  Invoke an automation run from an existing automation template. template_id refers to an existing automation template in the workspace. Example: { template_id: "auto-onboarding", recipient: "user-123", data: { plan: "pro" } }.

• Invoke Ad Hoc Automation

  Invoke an ad-hoc automation with inline steps. Valid step actions: send, send-list, delay, cancel, update-profile, invoke, fetch-data. To cancel a previously started automation, use the cancel_automation tool instead.