stripe sandboxes create, list, and delete management commands

Introduced 2026-10-16 · score 0.96

HOW TO USE IT

When managing Stripe sandboxes, use the active live account with `stripe sandboxes create`, `stripe sandboxes list`, and `stripe sandboxes delete`. Authorize a new sandbox with `stripe login` if prompted; confirm deletions with `--confirm` for non-interactive use.

WHY THIS HELPS

Manage Stripe sandboxes from the CLI using the active live account.

REQUIREMENTS AND LIMITATIONS

• Version: v1.54.0
• create [name]: Sandbox name; needed for non-interactive creation, otherwise an interactive run can prompt for it.
• --non-interactive: Print output without waiting for input; pair with a name to skip prompts.
• --create-blank: Create a blank sandbox instead of copying the active live account; requires `--country`.
• --country <code>: Two-letter country code for a blank sandbox; only valid with `--create-blank`.
• --email <address>: Email for anonymous claimable sandbox provisioning; mutually exclusive with `--from-git`.
• --from-git: Infer email and full name from git config for anonymous claimable sandbox provisioning; mutually exclusive with `--email`.
• --full-name <name>: Optional full name for anonymous sandbox provisioning; `--from-git` infers it from git config.
• list: Takes no arguments; output includes sandbox name, account ID, and access setting.
• delete <account_id> (required): Sandbox account ID from `stripe sandboxes list`; deletion is permanent.
• --confirm: Skip the deletion confirmation prompt; required for non-interactive deletion.
• Prerequisite: For managed creation and listing, log in and select an active live account. Listing requires an active live account.
• Prerequisite: Deletion requires an active live account that can manage the sandbox; use an account ID shown by `stripe sandboxes list`.
• Prerequisite: The source documents `stripe sandbox` as an alias for `stripe sandboxes`.
• Commands use the active live account and its OAuth-authorized sandboxes.
• Authorization is guided after creation.
• Destructive operations and legacy Test mode are guarded.
• `stripe sandbox` remains a compatibility alias.

FIRST-PARTY EVIDENCE

• https://github.com/stripe/stripe-cli/releases/tag/v1.54.0
• https://github.com/stripe/stripe-cli/pull/2106
• https://github.com/stripe/stripe-cli/blob/v1.54.0/pkg/cmd/sandbox.go

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

Report a problem with this card