wrangler turnstile widget CRUD commands

Introduced 2026-07-09 · score 0.98

HOW TO USE IT

When configuring or maintaining a repository's Turnstile integration, use Wrangler's widget subcommands to create, list, inspect, update, or delete widgets. For machine-readable output, add `--json`; deleting with JSON also requires `--skip-confirmation` or `-y`.

wrangler turnstile widget create <name> --domain <domain> --mode managed

wrangler turnstile widget list --json
wrangler turnstile widget get <sitekey> --json
wrangler turnstile widget update <sitekey> --name "Renamed" --json
wrangler turnstile widget delete <sitekey> --json --skip-confirmation

WHY THIS HELPS

Manage Turnstile widgets from the CLI while configuring or maintaining a repository's Turnstile integration.

REQUIREMENTS AND LIMITATIONS

Version: 4.109.0
<name> (required): Widget name.
--domain <domain> (required): Accepted hostname; repeat the flag or provide comma-separated hostnames.
--mode <mode> (required): Widget mode; create example uses `managed`.
<sitekey> (required): Widget identifier for get, update, or delete.
--json: Request machine-readable output; supported by all five subcommands.
--skip-confirmation / -y (required): For delete with `--json`, bypass confirmation so output remains pipeable.
Prerequisite: Wrangler 4.109 or later is required for the existing-widget recovery flow.
Prerequisite: API token authentication uses `Account.Turnstile:Edit`.
`delete --json` requires `--skip-confirmation` or `-y` to keep output pipeable.
`--domain` accepts comma-separated values.
`list` and `update` redact the secret; `get` can retrieve it later.
Existing OAuth sessions need to run `wrangler login` again to obtain the `challenge-widgets.write` scope.
API token users need a token with the `Account.Turnstile:Edit` permission.

FIRST-PARTY EVIDENCE

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

Report a problem with this card

Tools change faster than your agent’s training data.

Changes

wrangler turnstile widget CRUD commands