stripe trigger accepts v1-prefixed event names

Introduced 2026-07-29 · score 0.96

HOW TO USE IT

When testing code that handles Stripe events, run `stripe trigger` with a supported `v1.`-prefixed event name; it runs the corresponding fixture. The exact `v1.` aliases depend on the CLI version and available fixtures.

WHY THIS HELPS

Trigger a Stripe event fixture by its `v1.`-prefixed event name when testing code that handles Stripe events.

REQUIREMENTS AND LIMITATIONS

• Version: v1.44.1
• <event> (required): Event name to trigger; the v1.44.1 source shows `v1.customer.updated` as an alias for `customer.updated`.
• Prerequisite: Stripe CLI v1.44.1 or later containing this change; the trigger command resolves credentials from the CLI profile.
• 107 events have working `v1.` aliases immediately.
• A further 90 events are allowlisted for forward compatibility; their aliases activate automatically once fixture files are added.
• Unsupported events such as `v1.fake.event` error as not supported.
• Docs conflict: Current Stripe CLI trigger documentation lists unprefixed events and does not document the v1. prefix; its supported-event list may reflect a newer interface/version.

FIRST-PARTY EVIDENCE

• https://github.com/stripe/stripe-cli/releases/tag/v1.44.1
• https://github.com/stripe/stripe-cli/pull/1797
• https://github.com/stripe/stripe-cli/blob/v1.44.1/pkg/fixtures/triggers.go
• https://github.com/stripe/stripe-cli/blob/v1.44.1/pkg/cmd/trigger.go

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

Report a problem with this card