Skip to content

Account-owned Worker Editor token returns 401/10000 despite active verification #145

Open

Description

@ks1940sn-del

What versions & operating system are you using?

Wrangler 4.160.1
Ubuntu 24.04 (WSL2)
Windows 11

Please provide a link to a minimal reproduction

No public reproduction repository is available. The issue is reproducible using the Cloudflare API with an account-owned token scoped to a single Worker.

Describe the Bug

An account-owned API token scoped to Specified Workers → one existing Worker → Individual Workers Editor verifies as active, but Worker Settings and Deployments API requests return HTTP 401 / error 10000.

Environment:

  • Wrangler 4.160.1
  • Ubuntu 24.04 on WSL2 / Windows 11
  • Existing Worker created through the Cloudflare Dashboard
  • Account-owned Token scoped to one Worker, Individual Workers Editor
  • No account-wide Worker Admin permissions

Steps to reproduce:

  1. Create an existing Worker through the Cloudflare Dashboard.
  2. Create an account-owned API token with Specified Workers and Individual Workers Editor for that Worker.
  3. Verify the token with GET /accounts/{account_id}/tokens/verify.
  4. Use the same token to query the Worker's Settings and Deployments endpoints.

Actual results:

  • GET /accounts/{account_id}/tokens/verify → HTTP 200, active
  • GET /accounts/{account_id}/workers/scripts/{worker_name}/settings → HTTP 401, code 10000
  • GET /accounts/{account_id}/workers/scripts/{worker_name}/deployments → HTTP 401, code 10000

The saved token policy and Cloudflare account were verified in the Dashboard. The account IDs match.

Observed November 12, 2026, at 10:26 UTC.

Expected behavior:
Individual Workers Editor should allow the corresponding Settings and Deployments API operations, as documented by Cloudflare.

Related issues:

PR cloudflare/workers-sdk#16531 addresses unnecessary route/custom-domain metadata requests but does not establish a fix for these direct Settings/Deployments HTTP 401 errors.

Questions:

  1. Do these endpoints support account-owned Individual Workers Editor tokens?
  2. Is this an authorization regression or a restriction affecting dashboard-created Workers?
  3. Is there a supported least-privilege workaround without account-wide permissions?

No Worker code, Secrets, Durable Object migrations, or deployment changes were made. No credentials, account IDs, or private paths are included.

Please provide any relevant error logs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions