Cloudflare / Cloudflare

No longer able to use API token for auth — wrangler returns 'Failed to fetch auth token: 400 Bad Request'

Restore API token authentication in Cloudflare Wrangler CLI after it stopped working; user needs non-interactive auth for CI/CD pipelines. Includes evidence for Cloudflare troubleshooting demand.

Source-backed Last updated May 17, 2026 1 source Needs local verification

Category: Cloudflare
Error signature: wrangler whoami: Failed to fetch auth token: 400 Bad Request — 'You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN' — cannot use OAuth for CI/CD
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: May 17, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Cloudflare, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

wrangler whoami: Failed to fetch auth token: 400 Bad Request — 'You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN' — cannot use OAuth for CI/CD is a Cloudflare failure pattern reported for developers trying to restore api token authentication in cloudflare wrangler cli after it stopped working; user needs non-interactive auth for ci/cd pipelines.. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue cloudflare/workers-sdk#13744: wrangler whoami started returning 400 Bad Request even with active API tokens. User cannot fall back to OAuth due to automation requirements. Covers Account API Tokens, User API Tokens, Global API Key. Created 2026-04-29, 4 comments. Critical auth regression affecting deployments.

Common causes

GitHub issue cloudflare/workers-sdk#13744: wrangler whoami started returning 400 Bad Request even with active API tokens. User cannot fall back to OAuth due to automation requirements. Covers Account API Tokens, User API Tokens, Global API Key. Created 2026-04-29, 4 comments. Critical auth regression affecting deployments.

Quick fixes

Confirm the exact error signature matches wrangler whoami: Failed to fetch auth token: 400 Bad Request — 'You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN' — cannot use OAuth for CI/CD.
Check the Cloudflare account, local tool state, and provider configuration involved in the failing workflow.
Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match wrangler whoami: Failed to fetch auth token: 400 Bad Request — 'You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN' — cannot use OAuth for CI/CD exactly before applying the quick fix.
Compare the failing environment with Cloudflare versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does wrangler whoami: Failed to fetch auth token: 400 Bad Request — 'You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN' — cannot use OAuth for CI/CD mean in Cloudflare?

wrangler whoami: Failed to fetch auth token: 400 Bad Request — 'You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN' — cannot use OAuth for CI/CD indicates the workflow described by "No longer able to use API token for auth — wrangler returns 'Failed to fetch auth token: 400 Bad Request'" failed in a Cloudflare context. Start by confirming the exact signature and the component that emitted it.

What should I check first for wrangler whoami: Failed to fetch auth token: 400 Bad Request — 'You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN' — cannot use OAuth for CI/CD?

Check whether this cause matches your environment: GitHub issue cloudflare/workers-sdk#13744: wrangler whoami started returning 400 Bad Request even with active API tokens. User cannot fall back to OAuth due to automation requirements. Covers Account API Tokens, User API Tokens, Global API Key. Created 2026-04-29, 4 comments. Critical auth regression affecting deployments.

Is the wrangler whoami: Failed to fetch auth token: 400 Bad Request — 'You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN' — cannot use OAuth for CI/CD guidance source-backed?

The "No longer able to use API token for auth — wrangler returns 'Failed to fetch auth token: 400 Bad Request'" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for wrangler whoami: Failed to fetch auth token: 400 Bad Request — 'You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN' — cannot use OAuth for CI/CD?

For "No longer able to use API token for auth — wrangler returns 'Failed to fetch auth token: 400 Bad Request'", avoid applying "Verify the account session, API key, provider settings, and environment where the failing tool is running." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging wrangler whoami: Failed to fetch auth token: 400 Bad Request — 'You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN' — cannot use OAuth for CI/CD?

For "No longer able to use API token for auth — wrangler returns 'Failed to fetch auth token: 400 Bad Request'", collect the failing Cloudflare command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.