---
next_cursor: eyJzY29yZSI6MCwic2VxIjoxMTA5LCJzaW5jZSI6bnVsbCwidG9vbCI6InN0cmlwZS1jbGkiLCJ2IjoxfQ
has_more: true
next: https://sincecutoff.com/v1/changes.md?tool=stripe-cli&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxMTA5LCJzaW5jZSI6bnVsbCwidG9vbCI6InN0cmlwZS1jbGkiLCJ2IjoxfQ
items: 10
---
# sincecutoff.com changes: stripe-cli

## stripe-cli plugin install supports an unauthenticated path (stripe-cli, 2026-03-12)
Published 2026-10-16
- slug: stripe-cli-plugin-install-supports-an-unauthenticated-path-53fabf4e1e7b
- score: 0.95

How to use it:

When the plugin is eligible for unauthenticated installation and you are logged out, run `stripe plugin install <plugin>`; logged-in installs use the authenticated path. Plugins subject to incremental rollout still require authentication.

Examples:

```
stripe plugin install <plugin>
```

- why_it_matters: When not logged in, install a plugin that is eligible for the unauthenticated path.
- before: Log in before installing a plugin.
- sources: <https://github.com/stripe/stripe-cli/releases/tag/v1.37.3>, <https://github.com/stripe/stripe-cli/pull/1458>
- gotchas: "Version: v1.37.3"; "<plugin> (required): Plugin name to install."; "Prerequisite: Use a Stripe CLI version that includes this change (v1.37.3 or later)."; "Prerequisite: Be logged out for the unauthenticated path; incrementally rolled out plugins still require login."; "Plugins subject to incremental rollout continue to require the authenticated path."

## stripe login list and login switch manage multiple profiles (stripe-cli, 2026-03-21)
Published 2026-10-16
- slug: stripe-login-list-and-login-switch-manage-multiple-profiles-b86dc19f852e
- score: 0.98

How to use it:

When testing against multiple logged-in Stripe accounts, run `stripe login list` to list saved accounts and identify the active one, then switch with `stripe login switch <account_name>`. The `[default]` profile remains active; switching backs it up under its display name, copies the target into `[default]`, and removes the target key.

Examples:

```
stripe login list
```

```
stripe login switch <account_name>
```

- why_it_matters: When maintaining or testing code against multiple logged-in Stripe accounts, inspect the saved profiles and switch the active account.
- sources: <https://github.com/stripe/stripe-cli/releases/tag/v1.38.0>, <https://github.com/stripe/stripe-cli/pull/1433>, <https://github.com/stripe/stripe-cli/blob/v1.38.0/pkg/cmd/login.go>
- gotchas: "Version: v1.38.0"; "account_name (required): The account to switch to; exactly one positional argument is required."; "The `[default]` profile is always active."; "When switching, the current `[default]` profile is backed up using its display name as the key, the target profile is copied to `[default]`, and the old target key is removed."

## stripe login adds --non-interactive and --complete flags (stripe-cli, 2026-03-26)
Published 2026-10-16
- slug: stripe-login-adds-non-interactive-and-complete-flags-35ef1c0cdf76
- score: 0.90

How to use it:

When logging in from an unattended coding workflow, run `stripe login --non-interactive` to start the flow, then `stripe login --complete <url>` to complete it. The v1.39.0 release note confirms these flags were added; their detailed behavior is not documented on the official pages found.

- why_it_matters: Log in to Stripe from a coding workflow using the new non-interactive or completion options.
- sources: <https://github.com/stripe/stripe-cli/releases/tag/v1.39.0>
- gotchas: "Version: v1.39.0"

## stripe trigger adds Issuing transaction events (stripe-cli, 2026-03-26)
Published 2026-10-16
- slug: stripe-trigger-adds-issuing-transaction-events-fc740fc4ecaa
- score: 0.95

How to use it:

When testing Issuing transaction handlers, run `stripe trigger` with one of the three documented event names. The CLI trigger reference gives the event argument form; the v1.39.0 release note identifies the three added events and their effects.

Examples:

```
stripe trigger issuing_transaction.created
```

```
stripe trigger issuing_transaction.updated
```

```
stripe trigger issuing_transaction.purchase_details_receipt_updated
```

- why_it_matters: Trigger an Issuing transaction event while testing code that handles those events.
- sources: <https://github.com/stripe/stripe-cli/releases/tag/v1.39.0>, <https://github.com/stripe/stripe-cli/pull/1465>, <https://github.com/stripe/stripe-cli/wiki/trigger-command>, <https://github.com/stripe/stripe-cli>
- gotchas: "Version: v1.39.0"; "<event> (required): Event name to trigger; the release adds `issuing_transaction.created`, `issuing_transaction.updated`, and `issuing_transaction.purchase_details_receipt_updated`."; "Prerequisite: Stripe CLI installed; the `stripe` command is available after installation."; "Prerequisite: No additional authentication prerequisite for these trigger events was found in the official pages read."; "The regular update endpoint only accepts `metadata`; `purchase_details` is included in the `create_force_capture` call at creation time."

## stripe-cli adds `stripe whoami` (stripe-cli, 2026-03-30)
Published 2026-10-16
- slug: stripe-cli-adds-stripe-whoami-7062dcde5b67
- score: 0.90

How to use it:

To check the Stripe account or identity used by the CLI while working in a repository, run `stripe whoami`.

Examples:

```
stripe whoami
```

- why_it_matters: Check which Stripe account or identity the CLI is using while working in a repository.
- sources: <https://github.com/stripe/stripe-cli/releases/tag/v1.40.0>
- gotchas: "Version: v1.40.0"

## stripe-cli dry-run flag for resource and raw HTTP commands (stripe-cli, 2026-03-30)
Published 2026-10-16
- slug: stripe-cli-dry-run-flag-for-resource-and-raw-http-commands-ab081a7fb20e
- score: 0.97

How to use it:

When using a Stripe resource or raw HTTP command, add `--dry-run` to preview its effects without committing changes, as stated in the v1.40.0 release note.

- why_it_matters: Preview a resource or raw HTTP command's effects without committing its changes.
- sources: <https://github.com/stripe/stripe-cli/releases/tag/v1.40.0>
- gotchas: "Version: v1.40.0"; "The flag applies to resource and raw HTTP commands."

## stripe-cli trigger fixtures add test clock and topup events (stripe-cli, 2026-04-15)
Published 2026-10-16
- slug: stripe-cli-trigger-fixtures-add-test-clock-and-topup-events-f79090727247
- score: 0.95

How to use it:

When developing or testing handlers for these events, run `stripe trigger <event>` with one of the six newly supported event names. This triggers a test webhook event using the Stripe CLI.

Examples:

```
stripe trigger test_helpers.test_clock.created
```

```
stripe trigger test_helpers.test_clock.advancing
```

```
stripe trigger test_helpers.test_clock.ready, stripe trigger test_helpers.test_clock.deleted, stripe trigger topup.created, or stripe trigger topup.succeeded
```

- why_it_matters: Trigger test clock or topup events while developing or testing code that handles them.
- sources: <https://github.com/stripe/stripe-cli/releases/tag/v1.40.6>, <https://github.com/stripe/stripe-cli/pull/1461>, <https://github.com/stripe/stripe-cli/wiki/trigger-command>
- gotchas: "Version: v1.40.6"; "<event> (required): Event name to trigger; use one of `test_helpers.test_clock.created`, `test_helpers.test_clock.advancing`, `test_helpers.test_clock.ready`, `test_helpers.test_clock.deleted`, `topup.created`, or `topup.succeeded`."

## stripe completion adds fish shell support (stripe-cli, 2026-04-15)
Published 2026-10-16
- slug: stripe-completion-adds-fish-shell-support-602aceae12b2
- score: 0.94

How to use it:

When using fish, run `stripe completion --shell fish` to generate `stripe.fish`; move it to `~/.config/fish/completions/stripe.fish` for fish to load it. Homebrew installs the generated completion file automatically.

Examples:

```
stripe completion --shell fish
```

```
mkdir -p ~/.config/fish/completions && mv stripe.fish ~/.config/fish/completions/stripe.fish
```

- why_it_matters: Generate shell completion for a fish development environment.
- sources: <https://github.com/stripe/stripe-cli/releases/tag/v1.40.6>, <https://github.com/stripe/stripe-cli/pull/1484>, <https://github.com/stripe/stripe-cli/blob/v1.40.6/pkg/cmd/completion.go>, <https://github.com/stripe/stripe-cli/blob/v1.40.6/.goreleaser/mac.yml>
- gotchas: "Version: v1.40.6"; "--shell <shell>: Select the shell; accepted values are `bash`, `zsh`, or `fish`. Omit for shell auto-detection."; "--write-to-stdout: Print the completion script to stdout instead of creating a file."; "Prerequisite: For automatic completion loading, place `stripe.fish` in `~/.config/fish/completions`; fish loads completions from that directory."; "Prerequisite: Homebrew’s macOS formula generates bash, zsh, and fish completions, then installs `stripe.fish` to fish completions."

## Stripe CLI docs browsing subcommand (stripe-cli, 2026-07-01)
Published 2026-10-16
- slug: stripe-cli-docs-browsing-subcommand-0d9ca1a995a4
- score: 0.92

How to use it:

When implementing or debugging Stripe repository code, use the CLI to find the relevant Stripe docs page or search by keyword, then read the result. The docs reference lists `stripe docs` and its `api` and `search` subcommands.

Examples:

```
stripe docs <docs-path>
```

```
stripe docs search "<keyword or phrase>"
```

```
stripe docs api <resource|event>
```

- why_it_matters: Find Stripe documentation relevant to implementing or debugging repository code from the CLI.
- before: Before this release, the `docs` subcommand had not yet been added.
- sources: <https://github.com/stripe/stripe-cli/releases/tag/v1.43.3>, <https://docs.stripe.com/cli>
- gotchas: "Version: v1.43.3"; "<path> (required): Path of a docs.stripe.com page, such as `/payments` or `/api/customers`."; "<query> (required): Keyword or phrase to search on docs.stripe.com."; "<method|resource|event> (required): API lookup identifier: a resource name, HTTP method and path, or event type."; "--no-pager: Write output to stdout instead of opening an interactive pager."; "--non-interactive: Write output to stdout without the interactive browser."; "Prerequisite: Install the Stripe CLI to use the `stripe` command."

## stripe reporting query-runs creates and retrieves ad hoc queries (stripe-cli, 2026-07-09)
Published 2026-10-16
- slug: stripe-reporting-query-runs-creates-and-retrieves-ad-hoc-queries-93f1e962926d
- score: 0.99

How to use it:

When running an ad hoc SQL query against Stripe data, create a query run with exactly one SQL source, then retrieve its ID to check status and access the result download URL.

Examples:

```
stripe reporting query-runs create --sql "<SQL>"
```

```
stripe reporting query-runs create --sql-file <path> [--compress-file] [--dry-run] [--live]
```

```
stripe reporting query-runs retrieve <id> [--live]
```

- why_it_matters: Run and inspect an ad hoc SQL query against Stripe data from the CLI.
- before: The CLI could retrieve Sigma scheduled queries through the older `/v1/sigma` endpoint, but could not start new or ad hoc queries.
- sources: <https://github.com/stripe/stripe-cli/releases/tag/v1.43.7>, <https://github.com/stripe/stripe-cli/pull/1737>, <https://github.com/stripe/stripe-cli/blob/v1.43.7/pkg/cmd/reporting.go>
- gotchas: "Version: v1.43.7"; "Availability: The API is in public preview."; "--sql (required): SQL query text; required unless --sql-file is set. Mutually exclusive with --sql-file."; "--sql-file <path> (required): Read SQL from a file; use `-` to read stdin. Required unless --sql is set; mutually exclusive with --sql."; "--compress-file: Compress the result file; sets `result_options.compress_file` to true."; "--dry-run: Preview the request without sending it."; "--live: Make a live request; default is test mode."; "<id> (required): ID of the query run to retrieve."; "result_options.compress_file: Boolean set to true by `--compress-file`; the source documents no alternative sub-keys or allowed values."; "Prerequisite: A Stripe API key must be available through the selected CLI profile; the command reads the profile's test or live API key."; "Prerequisite: The endpoint is a preview API; the CLI marks both commands as preview commands and sets the preview Stripe-Version header automatically."; "The request builder sets `Stripe-Version: 2026-06-24.preview` and JSON content-type automatically."; "Retrieve polls query status (`running` → `succeeded`/`failed`) and fetches the result download URL."

Next: https://sincecutoff.com/v1/changes.md?tool=stripe-cli&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxMTA5LCJzaW5jZSI6bnVsbCwidG9vbCI6InN0cmlwZS1jbGkiLCJ2IjoxfQ
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->