Skip to content
CC Switch WikiUnofficial Community Wiki

invalid_authentication_error test failure - cc-switch

Quick fix

Upgrade cc-switch to fix failed {{apiKey}} parsing in custom usage query scripts, or temporarily hard-code the real API Key.

Symptom

Section titled “Symptom”
Error output
测试失败: HTTP 401 Unauthorized : {"error":{"message":"Invalid Authentication","type":"invalid_authentication_error"}}
English translation

Test failure: HTTP 401 Unauthorized : {"error":{"message":"Invalid Authentication","type":"invalid_authentication_error"}}

Cause

Section titled “Cause”

When configuring custom usage query scripts for providers such as Kimi in cc-switch, clicking “Test script” returns a 401 authentication error. In earlier versions, usage query script variable parsing is defective and cannot correctly recognize and replace template variables such as {{apiKey}} or {{baseUrl}}, causing an invalid Authorization Header to be sent to the official API. This issue affects only the test script path; the actual query path may work normally. The variable parsing logic was fixed in later versions, supporting multiple aliases and forms with spaces.

Fix

Section titled “Fix”

  1. Upgrade cc-switch to v3.15.0 or later, such as v3.16.0, to get the fixed variable parsing engine. It now supports common forms such as {{apiKey}}, {{ apiKey }}, and {{api_key}}.

  2. If you cannot upgrade yet, temporarily replace {{apiKey}} in the test script headers with the real API Key string for a hard-coded test.

    // test.js
    headers: {
      Authorization: 'Bearer {{apiKey}}',
      Authorization: 'Bearer sk-xxxxxxxxxxxxxxxxxxxxxxxx',
       'User-Agent': 'cc-switch/1.0',
    }

Affected Versions

Section titled “Affected Versions”
Toolcc-switch
Version< 3.15.0
PlatformsWindows

Source Issues

Section titled “Source Issues”

This page is distilled from 2 real issues

FAQ

Section titled “FAQ”
Why does replacing {{apiKey}} with the real Key make the test succeed?
Because earlier versions of cc-switch have a variable parsing bug in the “Test script” feature and cannot correctly replace template variables, the request returns 401 due to missing authentication. Hard-coding bypasses variable parsing.
Why does the test script fail, but the balance still displays normally on the home page?
The test script path and the actual query path behave inconsistently. Even if variable parsing fails in the test script, variable parsing on the actual query path may work normally, so the home page can fetch and refresh the balance.
Section titled “Related problems”
API Error: 401 authentication_errorCheck the API key field, Base URL, key type, and cc-switch version, so Claude Code actually reads a valid credential.7 issues mergedBash(...) Waiting... Claude CodeDowngrade Claude Code to v2.1.104 or v2.0.64 (admin required), or switch to a compatible provider such as Alibaba Cloud Bailian.1 issues merged"is not a model this version of Claude Code recognizes" - CC SwitchSet CLAUDE_CODE_MAX_CONTEXT_TOKENS or append [1m] to the model name to define the correct context window size.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.