GetToken
Codex API pricing, delivery, and support

GetToken Docs

GetToken Documentation

Learn Codex step by step, from core concepts and installation to GetToken API access, tool configuration, and troubleshooting.

Troubleshooting

Troubleshooting

Check sign-in state, API Key, base_url, model catalog, and local config files first.

Updated
Last verified
Maintained by
GetToken Documentation Team

Not signed in

Your personal API Key is only visible after sign-in. Click View my API Key on this page or open:

text
https://gettoken.dev/console/api-keys

No API Key

Open the API Key page and create one. After creation, you can reveal, copy, test, or import it into CC Switch.

Wrong base_url

Recommended:

text
https://api.clawto.link

Standard:

text
https://api.gettoken.dev

Do not use:

text
https://gettoken.dev
https://gettoken.dev/console

GPT-5.6 is missing in Codex

macOS / Linux:

bash
GETTOKEN_CODEX_MODEL='gpt-5.6-sol' GETTOKEN_CODEX_SET_DEFAULT_MODEL='1' bash -c "$(curl -fsSL 'https://cdn.gettoken.dev/scripts/codex-fix-gpt55-catalog.sh')"

Windows PowerShell:

powershell
$env:GETTOKEN_CODEX_MODEL='gpt-5.6-sol'; $env:GETTOKEN_CODEX_SET_DEFAULT_MODEL='1'; irm 'https://cdn.gettoken.dev/scripts/codex-fix-gpt55-catalog.ps1' | iex

Connection failed

Check these in order:

  1. The API Key was copied fully.
  2. auth.json is valid JSON.
  3. config.toml is in ~/.codex/config.toml.
  4. base_url is https://api.clawto.link.
  5. Your account has available quota.
  6. Your network can reach the endpoint.

API Key leaked

Delete the old key immediately and create a new one. Do not wait for unusual usage to appear.