Skip to content
CC Switch WikiUnofficial Community Wiki

Save keeps failing and asks for the API endpoint - cc-switch

Quick fix

Upgrade to cc-switch v3.11.0 or later. It natively supports AWS Bedrock and no longer requires an API endpoint or API Key.

Symptom

Section titled “Symptom”
Error output
保存一直提示报错，让我填写 api 端点。
English translation

Saving keeps showing an error and asks me to fill in the API endpoint.

Cause

Section titled “Cause”

In early cc-switch versions, adding a provider through custom configuration forced validation of required fields such as API endpoint and API Key. AWS Bedrock mode usually relies on AWS CLI credentials or environment variables such as CLAUDE_CODE_USE_BEDROCK and does not need a traditional API endpoint. This caused Bedrock configuration to fail save validation. The issue was fixed in v3.11.0 by adding native AWS Bedrock provider support.

Fix

Section titled “Fix”

  1. Upgrade cc-switch to v3.11.0 or later. v3.12.0 also adds Bedrock Request Optimizer.

  2. In cc-switch, select the native AWS Bedrock Provider. This mode supports AKSK authentication and does not require an API endpoint.

  3. If configuring manually, ensure the Claude Code configuration includes the environment variables required for Bedrock.

    // settings.json
    {
      "env": {
        "CLAUDE_CODE_USE_BEDROCK": 1,
        "AWS_REGION": "us-east-1"
      }
    }

Affected Versions

Section titled “Affected Versions”
Toolcc-switch
Version< v3.11.0
PlatformsUnknown

Source Issues

Section titled “Source Issues”

This page is distilled from 1 real issues

FAQ

Section titled “FAQ”
If Bedrock mode is detected, can other required fields be skipped?
Yes. In v3.11.0 and later, cc-switch natively supports the AWS Bedrock provider with AKSK authentication and no longer requires an API endpoint or API Key.
I entered a random endpoint, and now it says a custom access key is required. What should I do?
Old versions forced validation of all required fields. Upgrade to v3.11.0 or later and use the native AWS Bedrock provider configuration to skip these checks.
We use Bedrock Converse API behind Kong for compliance. Can custom provider support be added for Bedrock API?
Native Bedrock support is already available. For complex cases with custom proxies or custom authentication field names, the developers welcome PRs to add custom Bedrock API format support.
Section titled “Related problems”
ANTHROPIC_AUTH_TOKEN and ANTHROPIC_API_KEYOpen `~/.claude/settings.json`, delete the duplicate auth variable so only the one your provider needs remains, save, and restart Claude Code.4 issues merged401 Unauthorized: Incorrect API key providedAfter switching to OpenAI Official or turning the proxy off, clear the leftover third-party OPENAI_API_KEY from ~/.codex/auth.json and restart Codex.2 issues mergedClaude Code cannot call the model after configuration - CC SwitchConfirm cc-switch only rewrites config, then check the skip-first-install option, proxy and region restrictions, and upstream API compatibility.3 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.