sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

stripe listen unifies event selection and forwarding flags

Introduced 2026-09-17 · score 0.97

HOW TO USE IT

When forwarding Stripe webhook events locally, select event types with `--events` or all snapshot/thin events with `--all-snapshot` or `--all-thin`, then set a destination with `--forward-to` or `--forward-connect-to`. Use `--events-from` to choose account sources; a single endpoint cannot receive both snapshot and thin payload styles.

stripe listen --events <snapshot-event>,<thin-event> --forward-to localhost:3000/events
stripe listen --all-snapshot --forward-to localhost:3000/events
stripe listen --all-thin --events-from @accounts --forward-to localhost:3000/events

WHY THIS HELPS

Forward snapshot and thin events to a local endpoint with `stripe listen`.

BEFORE THIS CHANGE

Previously, thin event selection and forwarding used the parallel flags `--thin-events`, `--forward-thin-to`, and `--forward-thin-connect-to`.

REQUIREMENTS AND LIMITATIONS

  • Version: v1.51.0
  • --events <event>[,<event>...]: Comma-separated snapshot event names and/or thin event names (thin names such as `v1.billing.meter.no_meter_found`). Select this or an all-events flag when forwarding.
  • --all-snapshot: Subscribe to all snapshot events. Mutually exclusive with `--all-thin` and with selected events of the other payload style; one endpoint cannot receive both styles.
  • --all-thin: Subscribe to all thin events. Mutually exclusive with `--all-snapshot` and with selected events of the other payload style; one endpoint cannot receive both styles.
  • --forward-to <url>: URL to forward events to; required in practice to forward to a local endpoint.
  • --forward-connect-to <url>: URL for Connect events; defaults to `--forward-to`. Cannot be used with `--events-from @self`.
  • --events-from <value>: Account source: `@self` (your account only), `@accounts` (connected accounts only), or `all` (default). With `@accounts`, different values for `--forward-to` and `--forward-connect-to` are ambiguous.
  • --events '*': Unsupported because the wildcard is ambiguous with thin events. Use `--all-snapshot` or `--all-thin`.
  • --thin-events: Deprecated; use `--events` for selected snapshot/thin types or `--all-thin` for all thin events. Hidden from help.
  • --forward-thin-to: Deprecated; use `--forward-to` with selected thin events or `--all-thin`. Snapshot and thin events cannot share one destination. Hidden from help.
  • --forward-thin-connect-to: Deprecated; use `--events-from @accounts` with thin event selection and `--forward-to <url>`. Hidden from help.
  • Prerequisite: Forwarding requires an explicit event subscription: use `--events`, `--all-snapshot`, or `--all-thin`.
  • Deprecated thin-specific flags continue working with warnings and replacement guidance; they stay out of `--help`.
  • The former thin-specific flags are planned to be rejected in a later release after documentation is updated.
  • `--events '*'` became ambiguous once thin events existed.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card