Which request address should Claude Code use?
In the verified CCSwitch flow, copy the current request address from the Get API key page and use it with the key from the same account. Do not infer it from another protocol example.
GET API · Developer integrations
This page describes only the CCSwitch flow verified in the existing UI: create a Get API key for Claude Code, add a Provider in the CCSwitch Claude area, paste the API key and request address currently shown in the console, enable it, and restart Claude Code completely. Because the Get API environment-variable contract for Claude Code has not been independently verified, this page does not invent commands or label the OpenAI chat Base URL as a Claude-specific endpoint.
Claude Code installation methods and system requirements can change. Select the current method for your system from the official installation page and use claude --version or the official diagnostic path to confirm installation. Get API does not host a copied installer.
The existing flow verifies selecting Claude in CCSwitch, adding a custom Provider, entering an API key and request address, and enabling it. Copy the request address from the current Get API key page rather than forcing another protocol address into Claude Code.
A running Claude Code client may retain old settings after a Provider change. Quit it completely, start it again, and send a simple message. On failure, separate 401, 404, unavailable model, and stale configuration.
The reference screenshots show the verified Chinese UI; field labels may move between CCSwitch versions.
Follow the current official Claude Code installation page and confirm that claude --version works. Do not download a third-party installer from this site.
Create a Get API key and choose a group currently identified for Claude Code in the console.

Open CCSwitch and switch to the Claude Provider area in the top tool selector.

Add a Provider, paste the Get API key into the API Key field, and paste the request address from the same key page into the request-address field.

Save the configuration, enable the Provider, and confirm that it is the active selection.

Quit Claude Code completely, reopen it, and send a simple message. The integration is complete only after a normal response arrives.
This command verifies only that the local CLI is available. It contains no Get API key and no unverified Provider environment variable.
claude --versionSeparate installation, authentication, routing, and cached-client state first.
| Symptom | Likely cause | Action | Success check |
|---|---|---|---|
| claude command is unavailable | Installation is incomplete or PATH is stale | Return to the current official instructions, finish installation, and reopen the terminal | claude --version runs |
| 401 | Incomplete or disabled key, or key pasted into the wrong field | Copy it again from secure storage and verify the CCSwitch API Key field | The first message no longer returns authentication failure |
| 404 or connection failure | Request address from another service, incomplete copy, or unsaved form | Copy the current request address again from the same Get API key page | The request reaches the intended service path |
| Model unavailable | The key group does not match the Claude Code target | Review the current key-group options and account access | The target Provider returns an available model response |
| Old Provider remains active | Target Provider is disabled or a Claude Code process is still running | Confirm enablement, quit every Claude Code process, and restart | The restarted client uses the new Provider |
In the verified CCSwitch flow, copy the current request address from the Get API key page and use it with the key from the same account. Do not infer it from another protocol example.
Never send the complete key. Share a redacted identifier, status, group, and steps instead; disable and rotate the key first if exposure is suspected.
The target Provider may not be enabled, or Claude Code may still be running. Save and enable it, quit every process, and then restart.
It makes no such claim yet. This guide covers only the verified CCSwitch configuration; an environment-variable contract requires independent verification.
Business inquiries: business@honeykid.cn