io.github.trycourier/courier

Tools

• add_bulk_users

  Add users to an existing bulk job.

  shallow
• add_subscribers_to_list

  Append subscribers to a list without removing existing subscribers.

  shallow
• add_user_to_tenant

  Add a user to a tenant.

  shallow
• archive_journey

  Archive a journey. Archived journeys cannot be invoked but existing runs continue to completion.

  shallow
• archive_journey_template

  Archive a journey-scoped notification template. Archived templates cannot be sent.

  shallow
• archive_notification

  Archive a notification template by ID.

  shallow
• archive_preference_section

  Archive a preference section. The section must be empty: delete its topics first, otherwise the request fails with 409.

  shallow
• archive_preference_topic

  Archive a topic within a section.

  shallow
• archive_preview_device_set

  Archive a preview device set. Runs that used it keep their own copy of its devices. The Courier Recommended set cannot be archived.

  shallow
• archive_request

  Archive a send request and all its associated messages by request ID.

  shallow
• archive_routing_strategy

  Archive a routing strategy. The strategy must not have associated notification templates; unlink all templates before archiving.

  shallow
• bulk_add_user_tenants

  Add a user to multiple tenants at once. A custom profile can be supplied per tenant.

  shallow
• bulk_add_user_tokens

  Add multiple push/device tokens for a user in one request. Overwrites matching existing tokens.

  shallow
• bulk_replace_user_preferences

  Replace a user's complete set of preference overrides in one request. The topics in the body become the recipient's entire override set: listed topics are created or updated, and every existing override not included is reset to its topic default. An empty `topics` array clears all overrides. Validation-atomic (all-or-nothing).

  shallow
• bulk_subscribe_to_list

  Replace all subscribers on a list with the given recipients.

  shallow
• bulk_update_user_preferences

  Additively create or update a user's preferences for one or more topics in a single request. Only the topics in the body are touched; existing overrides for other topics are left untouched. Partial-success: valid topics are written and returned in `items`, unapplicable ones collected in `errors`.

  shallow
• cancel_automation

  Cancel a running automation by its cancelation_token. This invokes a second ad-hoc automation with a single cancel step. The token must match the cancelation_token set when the original automation was started. Note: spelling is "cancelation_token" (single "l").

  shallow
• cancel_broadcast_schedule

  Cancel a broadcast's scheduled send. The broadcast itself is kept.

  shallow
• cancel_journey

  Cancel journey runs. Supply EXACTLY ONE of cancelation_token (cancels every run associated with the token) or run_id (cancels a single run). Cancelation is idempotent: a run that already finished or was already canceled is left unchanged.

  shallow
• cancel_message

  Cancel a message that is currently being delivered. Returns the message details with updated status.

  shallow
• cancel_notification_submission

  Cancel a notification template submission.

  shallow
• courier_installation_guide

  Get the Courier SDK installation guide for a specific platform. For client-side SDKs (React, iOS, Android, Flutter, React Native), also generates a sample JWT.

  shallow
• create_brand

  Create a new brand. The API requires settings — omitting it returns a 400. If you do not have specific brand colors, omit settings and a safe default will be used automatically (black primary, white secondary). Example: { name: "Acme", settings: { colors: { primary: "#1a73e8", secondary: "#ffffff" } } }.

  shallow
• create_broadcast

  Create a broadcast: a one-off message to a list or audience on a single channel. It starts as a draft with no content; add content with put_broadcast_content, then send_broadcast or schedule_broadcast.

  shallow
• create_bulk_job

  Create a new bulk job for sending messages to multiple recipients. Workflow: create_bulk_job → add_bulk_users → run_bulk_job.

  shallow
• create_journey

  Create a new journey. Always created as a draft; making it live is a separate step this tool cannot perform. Send nodes are not allowed on create — create the shell with a trigger node, then call replace_journey to add send nodes after linking notification templates. Node ids are server-generated; do NOT include an id field. Example: { name: "Welcome Journey", nodes: [{ type: "trigger", trigger_type: "api-invoke" }], enabled: true }.

  shallow
• 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!" }] } } }.

  shallow
• create_list

  Create or update a list by list ID.

  shallow
• create_notification

  Create a V2 notification template. name is required. Provide content inline or set it immediately after creation via put_notification_content. To send with this template you must publish it first via publish_notification (or pass state: 'PUBLISHED' on create). 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: [] } } }.

  shallow
• create_or_merge_user

  Create a new user profile or merge supplied values into an existing profile (POST). Existing fields not included are preserved.

  shallow
• create_or_replace_user_push_token

  Create or replace a push/device token for a user.

  shallow
• create_or_update_tenant

  Create or replace a tenant. Tenants represent organizations or groups that users belong to.

  shallow
• create_preference_section

  Create a preference section in your workspace. The section id is generated and returned. Add topics afterwards with create_preference_topic.

  shallow
• create_preference_topic

  Create a subscription preference topic inside a section. The topic id is generated and returned. Fails with 404 if the section does not exist.

  shallow
• create_preview_device_set

  Create a named, reusable set of preview devices.

  shallow
• create_preview_run

  Render a template's email on real email clients and capture screenshots. Pass exactly one of device_set_id or device_ids. Each run is billed to the workspace's previews add-on. The run starts PENDING, so poll get_preview_run for the results.

  shallow
• create_provider

  Create a new provider (integration) configuration. Once routing strategies or notification templates reference this config, credential or settings mistakes can affect live sends—confirm provider key and settings against list_provider_catalog before saving. The provider field must be a known Courier provider key.

  shallow
• create_routing_strategy

  Create a routing strategy defining how notifications are delivered across channels and providers.

  shallow
• delete_audience

  Delete an audience by its ID.

  shallow
• delete_brand

  Delete a brand by its ID.

  shallow
• delete_broadcast

  Delete a broadcast.

  shallow
• delete_list

  Delete a list by its ID.

  shallow
• delete_profile

  Delete a user profile permanently.

  shallow
• delete_provider

  Delete a provider configuration. Returns 409 if the provider is still referenced by routing or notifications.

  shallow
• delete_tenant

  Delete a tenant by its ID.

  shallow
• delete_tenant_preference

  Remove default notification preference for a topic from a tenant.

  shallow
• delete_tenant_template

  Delete a tenant notification template. Returns 204 on success, 404 if the template does not exist for this tenant.

  shallow
• delete_user_list_subscriptions

  Delete all list subscriptions for a user.

  shallow
• delete_user_preference_topic

  Delete a user's preference for a specific subscription topic, reverting it to the topic's default status.

  shallow
• delete_user_token

  Delete a specific push token for a user.

  shallow
• duplicate_broadcast

  Copy a broadcast into a new draft. The original is left unchanged.

  shallow
• generate_jwt_for_user

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

  shallow
• get_audience

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

  shallow
• get_audit_event

  Get a specific audit event by its ID.

  shallow
• get_brand

  Get a brand by its ID.

  shallow
• get_broadcast

  Get a broadcast by id, including its channel and send or schedule state.

  shallow
• get_broadcast_content

  Get a broadcast's Elemental content.

  shallow
• get_bulk_job

  Get the status of a bulk job.

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

  shallow
• get_journey_run

  Get one journey run by id: its journey, status, and timestamps.

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

  shallow
• get_journey_template_content

  Fetch the elemental content of a journey-scoped notification template. Pass version=draft for the working draft, or vN for a historical version. Defaults to published.

  shallow
• get_list

  Get a list by its ID.

  shallow
• get_list_subscribers

  Get all subscribers of a list.

  shallow
• get_message

  Get the full details and status of a single message by its ID.

  shallow
• get_message_content

  Get the rendered content (HTML, text, subject) of a previously sent message.

  shallow
• get_message_history

  Get the event history for a message, showing each step in the delivery pipeline (enqueued, sent, delivered, etc.).

  shallow
• get_notification

  Retrieve a notification template by ID. Optionally request draft, published, or a version such as v001.

  shallow
• get_notification_content

  Get the published content blocks of a notification template.

  shallow
• get_notification_draft_content

  Get the draft (unpublished) content blocks of a notification template.

  shallow
• get_notification_metrics

  Delivery funnel for ONE notification template over time: sent, delivered, opened, clicked, errors and undeliverable, per provider and channel, in time buckets. Choosing the window — supply EITHER `lookback` OR `start` and `end` together, NEVER both. Supplying both is rejected. For a relative window like 'the last week', `lookback` alone is the whole answer: do not also pin `start` and `end`. Default is the last 30 days by day. Fine granularities cover shorter windows: HOUR spans at most 7 days and DAY at most 90. How far back a workspace may look also depends on its plan; a request reaching further back is refused with a payment error, which means the plan does not cover that window, NOT that there is no data. A coarser granularity can reach further back than a fine one. Reading the numbers correctly: - The first four counters are NESTED, not separate groups. Every delivered message is also counted in sent, every opened one in delivered, every clicked one in opened. So sent >= delivered >= opened >= clicked always. Report rates (delivered/sent) or the counters themselves. Do NOT add them together — the total is meaningless. And sent minus delivered is NOT a failure count; it is only 'did not reach the delivered stage', for any reason. - errors and undeliverable are counted separately and OVERLAP the funnel: a message that failed on one provider and succeeded on a retry appears in both errors and sent. They are not a remainder and do not complete a total. - Every counter is a count of distinct MESSAGES, not of events. A message that errored three times counts once in errors. - A bucket's `data` array holds one entry per provider and channel. To get a bucket total, add up the entries in that array — that is the only sum that means anything here. Note that rows for Courier's own built-in email sender are excluded, so these entries can add up to less than the workspace's true volume. What the buckets mean: - A message is counted in the bucket it was ENQUEUED in, not when the event happened. An open today of a message sent last Tuesday is counted in last Tuesday's bucket. So a past bucket can still change: yesterday's `opened` may be higher when you ask again tomorrow. - Results are cached for up to an hour and the pipeline adds its own lag, so a message sent minutes ago is expected NOT to appear yet. Never tell a user a just-sent message is missing; say the data has not caught up. - Read the window off the response's `start` and `end`, not off what you asked for. The API widens the window to whole buckets and returns the boundaries it actually used. - Quiet buckets are returned with an empty `data` array, so the series has no gaps. - An unknown template id returns an all-empty series rather than an error, and messages sent without a template never appear here at all. An empty result is not proof a template is unused — check that the id is right before concluding anything from it. - Because of that, a NOT FOUND / 404 error is never about the template id. It means the metrics endpoint itself could not be reached, which is an infrastructure or configuration problem on Courier's side. Say that the metrics service is unreachable and that someone should be told; do NOT tell the user to check or correct their template id, which sends them to fix something that was never wrong.

  shallow
• get_preference_section

  Retrieve a preference section by id, including its topics.

  shallow
• get_preference_topic

  Retrieve a topic within a section. Returns 404 if the section or topic does not exist, or the topic belongs to a different section.

  shallow
• get_preview_device_set

  Get a preview device set by id.

  shallow
• get_preview_run

  Get a preview run with its per-device results and screenshot URLs. Poll until status is COMPLETED or FAILED. The URLs are short-lived and re-signed on every read, so fetch them rather than storing them.

  shallow
• get_provider

  Fetch a single provider configuration by ID.

  shallow
• get_routing_strategy

  Retrieve a routing strategy by ID. Returns the full entity including routing, channels, and providers.

  shallow
• get_tenant

  Get a tenant by its ID.

  shallow
• get_tenant_template

  Get a tenant notification template association by template ID.

  shallow
• get_tenant_template_version

  Get a specific version of a tenant notification template (e.g. latest, published, or v1).

  shallow
• get_translation

  Get a translation for a specific locale (e.g. "en_US", "fr_FR").

  shallow
• get_user_list_subscriptions

  Get all list subscriptions for a user.

  shallow
• get_user_preference_topic

  Get a user's preference for a specific subscription topic.

  shallow
• get_user_preferences

  Get a user's notification preferences (subscriptions, opt-outs, channel preferences).

  shallow
• get_user_profile_by_id

  Get a user profile by their ID. Returns profile data including email, phone, and custom properties.

  shallow
• get_user_push_token

  Get a specific push/device token for a user.

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

  shallow
• invoke_automation_template

  Invoke an automation run from an existing automation template. Call list_automations first to get the template_id. Example: { template_id: "auto-onboarding", recipient: "user-123", data: { plan: "pro" } }.

  shallow
• invoke_journey

  Invoke a journey run from a journey template. Call list_journeys first to find the template_id. Example: { template_id: "j-onboarding", user_id: "user-123", data: { plan: "pro" } }.

  shallow
• list_audience_members

  List all members of an audience.

  shallow
• list_audiences

  List all audiences in the workspace.

  shallow
• list_audit_events

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

  shallow
• list_automation_run_steps

  List the steps of an automation run in order, with what happened at each. Send steps carry a message_id to follow with get_message.

  shallow
• list_automation_runs

  List automation runs, newest first. Filter by automation template, status, or a created_at window to find a run that stalled or errored, then read its steps with list_automation_run_steps. Journey runs are listed by list_journey_runs instead.

  shallow
• list_automations

  List automation templates in the workspace. Always call this first to discover template_id values before calling invoke_automation_template. Optionally filter by version.

  shallow
• list_brands

  List all brands in the workspace.

  shallow
• list_broadcasts

  List broadcasts in the workspace.

  shallow
• list_bulk_users

  List the users in a bulk job.

  shallow
• list_digest_instances

  List the digest instances for a schedule. Each instance represents the events accumulated for a single user against the schedule, useful for monitoring accumulation before a digest is released.

  shallow
• list_journey_run_steps

  List the steps of a journey run in order, with each node and what happened at it. This is how to see where a run stopped and why.

  shallow
• list_journey_runs

  List journey runs, newest first. Filter by journey, status, or a created_at window to find a run that stalled or errored, then read its steps with list_journey_run_steps.

  shallow
• list_journey_template_versions

  List published versions of a journey-scoped notification template, ordered most recent first.

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

  shallow
• list_journey_versions

  List published versions of a journey, ordered most recent first.

  shallow
• list_journeys

  List journey templates in the workspace. Call this first to discover journey IDs before calling invoke_journey, get_journey, or replace_journey. Optionally filter by version (published or draft).

  shallow
• list_lists

  Get all lists. Optionally filter by pattern (e.g. 'example.list.*').

  shallow
• list_messages

  List messages you've previously sent. Filter by status, recipient, notification, provider, tags, or tenant.

  shallow
• list_notification_checks

  List checks for a notification submission.

  shallow
• list_notification_versions

  List version history for a notification template.

  shallow
• list_notifications

  List notification templates. Optionally filter by cursor.

  shallow
• list_preference_logs

  List preference changes, newest first. Each entry is one change a user made to one subscription topic, with the value before it where there was one. Pass user_id to answer "when did this user opt out, and of what?"; omit it to read the whole environment. Page with paging.cursor while paging.more is true.

  shallow
• list_preference_sections

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

  shallow
• list_preference_topics

  List the topics in a preference section.

  shallow
• list_preview_device_sets

  List saved preview device sets. Every workspace has a read-only Courier Recommended set that runs can use without creating a set first.

  shallow
• list_preview_devices

  List the email clients a preview can render on. Each device has a pvd_ id, a display name, and fields to filter by: category, app, platform, os, os_version and theme. Use these ids in a device set or in create_preview_run.

  shallow
• list_preview_runs

  List a template's preview runs, newest first.

  shallow
• list_provider_catalog

  List available provider types from the catalog with their configuration schemas.

  shallow
• list_providers

  List configured provider integrations for the workspace.

  shallow
• list_routing_strategies

  List routing strategies in the workspace. Returns metadata only; use get for full details.

  shallow
• list_routing_strategy_notifications

  List notification templates associated with a routing strategy. Useful for checking linked templates before archiving.

  shallow
• list_tenant_templates

  List notification templates configured for a tenant.

  shallow
• list_tenant_users

  List users associated with a tenant.

  shallow
• list_tenants

  List all tenants in the workspace.

  shallow
• list_user_push_tokens

  List all push/device tokens for a user.

  shallow
• list_user_tenants

  List all tenants a user belongs to.

  shallow
• patch_profile

  Partially update a user profile via JSON Patch (RFC 6902). Use add/replace/remove operations on specific profile paths.

  shallow
• patch_user_token

  Apply a JSON Patch (RFC 6902) to a specific push token.

  shallow
• publish_journey

  Publish the current draft of a journey, making it live and invokable. Pass version to roll back to a prior published version instead of publishing the draft. Returns 404 if there is no draft to publish.

  shallow
• publish_journey_template

  Publish the current draft of a journey-scoped notification template. Optionally pass version to roll back to a prior version.

  shallow
• publish_notification

  Publish a notification template, making it available for sending. Must be called before send_message_template unless the template was created with state: 'PUBLISHED'. Publishes the current draft by default; pass version (e.g. 'v001') to publish a specific historical version. Returns 204 on success.

  shallow
• publish_preferences

  Publish the workspace's preferences page. Takes a snapshot of every section with its topics under a new published version, making the current state visible on the hosted preferences page.

  shallow
• publish_tenant_template

  Publish a version of a tenant notification template.

  shallow
• put_broadcast_content

  Replace a broadcast's content with an Elemental document. Saved as a draft unless state is PUBLISHED.

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

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

  shallow
• 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 plain text only" }] }].

  shallow
• put_notification_element

  Update a single element within a V2 notification template.

  shallow
• 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." }] }.

  shallow
• release_digest

  Release a digest schedule early — send what users have collected so far now instead of waiting for the scheduled time. A 204 is also returned when the schedule has no in-progress instances to release.

  shallow
• release_user_digest

  Release one recipient's held digest for a topic now, instead of waiting for its schedule. Use it to preview a digest, or to let a user flush their own, without releasing everyone else on the schedule. There is no release-everyone form of this call; use release_digest with a schedule id for that.

  shallow
• remove_all_user_tenants

  Remove a user from all tenants.

  shallow
• remove_user_from_tenant

  Remove a user from a tenant.

  shallow
• rename_broadcast

  Rename a broadcast. Content and channel are unchanged.

  shallow
• replace_journey

  Replace (update) a journey draft. Full document replacement — include all nodes and properties in the body. The journey stays a draft; making the change live is a separate step this tool cannot perform. Send node template IDs must already be scoped to this journey.

  shallow
• replace_journey_template

  Replace the draft of a journey-scoped notification template. Full document replacement. Call publish_journey_template afterwards to make it live.

  shallow
• replace_notification

  Replace a notification template entirely (full document PUT).

  shallow
• replace_preference_section

  Replace a preference section. Full document replacement; missing optional fields are cleared. Topics attached to the section are unaffected.

  shallow
• replace_preference_topic

  Replace a topic within a section. Full document replacement; missing optional fields are cleared.

  shallow
• replace_preview_device_set

  Replace a preview device set's name and devices. This is a full replace, so send every device the set should keep. The Courier Recommended set cannot be changed.

  shallow
• replace_profile

  Fully replace a user profile (PUT). All existing data is overwritten; include every field you want to keep.

  shallow
• replace_routing_strategy

  Replace a routing strategy. Full document replacement; missing optional fields are cleared.

  shallow
• replace_tenant_template

  Create or replace a tenant notification template (draft unless published is true).

  shallow
• resend_message

  Resend a previously sent message. Loads the original send request and enqueues a brand-new send to the same recipient with the same content, producing a new messageId; the original message is unchanged. Rate limited per message (429 on rapid repeats).

  shallow
• restore_list

  Restore a previously deleted list.

  shallow
• run_bulk_job

  Run a bulk job, triggering delivery to all added users.

  shallow
• schedule_broadcast

  Schedule a broadcast to send later to a list or audience. Cancel with cancel_broadcast_schedule.

  shallow
• send_broadcast

  Send a broadcast now to every member of a list or audience. This delivers real messages.

  shallow
• send_message

  Send a message to a user using inline title and body content (no template). Optionally specify routing channels.

  shallow
• send_message_template

  Send a message to a user using a published notification template. The template must be published before sending — call publish_notification first if needed. Example: { user_id: "user-123", template: "nt_01abc123", data: { name: "Alex", resetUrl: "https://app.example.com/reset" } }.

  shallow
• send_message_to_list

  Send a message to all subscribers of a list using inline title and body content.

  shallow
• send_message_to_list_template

  Send a message to all subscribers of a list using a notification template.

  shallow
• subscribe_user_to_list

  Subscribe a user to a list. Creates the list if it doesn't exist.

  shallow
• subscribe_user_to_lists

  Subscribe a user to one or more lists. Creates lists that do not exist.

  shallow
• trace_message

  Trace delivery in one call. Give EXACTLY ONE of message_id (a single message) or trace_id (the metadata.trace_id set on a send, which can span several messages). Returns each matching message with its event history, which carries the status reason when a message is undeliverable. Set include_output to also return the rendered content each provider received.

  shallow
• track_inbound_event

  Track an inbound event that can trigger automations. Requires event name, messageId (for deduplication), and properties.

  shallow
• unsubscribe_user_from_list

  Unsubscribe a user from a list.

  shallow
• update_audience

  Create or update an audience with a filter definition.

  shallow
• update_brand

  Replace an existing brand with new values.

  shallow
• update_notification_checks

  Update check statuses for a notification submission.

  shallow
• update_provider

  Replace an existing provider configuration. Full replacement — retrieve current config with get_provider first; omitted optional fields are cleared. Changing API keys or settings affects live delivery if this integration is in use.

  shallow
• update_tenant_preference

  Set the default notification preference for a subscription topic on a tenant. This controls tenant-level defaults — it does NOT set per-user preferences (use the user preferences API for that). The topic_id must already exist as a subscription topic in the workspace; a 404 means the topic has not been created yet. Example: { tenant_id: "acme", topic_id: "marketing-updates", status: "OPTED_IN", has_custom_routing: true, custom_routing: ["email", "push"] }.

  shallow
• update_translation

  Create or update a translation for a specific locale.

  shallow
• update_user_preference_topic

  Update a user's preference for a specific subscription topic (opt in, opt out, or set channel preferences).

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/1accc076-a7b0-485c-81e1-3aefdab7b224/badge.svg)](https://vouch.tools/servers/1accc076-a7b0-485c-81e1-3aefdab7b224)