Proxy Account Format Converter

1. Sign in to your own ChatGPT account in a browser.
2. In the same browser, open chatgpt.com/api/auth/session.
3. Save the complete JSON shown on the page, or paste the complete response into this converter. Do not copy only one token field.

How to use it: paste the JSON into the import box, or save it as a .json or .txt file and upload it.

Expiry: Session tokens are time-limited. Sign in again and obtain a new session after the old one expires. Do not expose or share the Session Token.

How to obtain it: complete the provider OAuth login in CLIProxyAPI. Authentication JSON files are stored in ~/.cli-proxy-api by default; the actual location is controlled by auth-dir in its configuration.

How to use it: place a single-account CPA JSON file in CLIProxyAPI's configured authentication directory, or import it through the CLIProxyAPI management center. Use the target application's OAuth login when possible instead of manually assembling tokens.

How to obtain it: in the Sub2API admin console, open Account Management and choose Export Data. The exported file normally contains exported_at, proxies, and accounts.

How to use it: open Account Management → Import Data and upload the Sub2API JSON generated by this page. Back up existing accounts first, then check each account's platform, OAuth type, proxy, and priority after import.

How to obtain it: in Cockpit Tools, add a Codex account through OAuth or local import, then choose Cockpit Tools from the account export menu. Codex can also be imported from its current local ~/.codex/auth.json.

How to use it: go to Codex Accounts → Add Account → Token / JSON and paste or select the generated JSON. Use Codex Batch Import for multiple files. Back up the current Codex login file before switching accounts.

How to obtain it: a 9Router Codex account object can come from an existing 9Router backup or be generated from another supported account format on this page.

How to use it: open Providers → Codex → Bulk Add / Bulk Import. Paste a single object, an array of account objects, or an object wrapped in { accounts: [...] }. Each account needs an access token; refresh and ID tokens should be retained when available.

Important: do not restore a full 9Router database backup just to import account JSON. Database restore can replace existing settings and connections.

How to obtain it: sign in through the Codex CLI or IDE with ChatGPT or an API key. Codex may cache credentials in ~/.codex/auth.json or in the operating system's credential store.

How to use it: the safest option is to let Codex manage sign-in itself. If you must migrate a file, close Codex, back up the current file, then place the valid file at ~/.codex/auth.json with access restricted to your user.

See OpenAI's Codex login caching documentation. Never commit auth.json to Git or share it.

How to obtain it: create or edit a Codex Channel in AxonHub and use its Official OAuth flow. An existing Codex Auth JSON can also be used as the source for conversion.

How to use it: open Channels → create or edit Codex → Auth JSON, paste the JSON generated on this page, and apply it. For Claude, use the Claude Code official OAuth flow; do not import unrelated provider JSON as a Codex Channel.

How to obtain it: Codex Manager can export an account as JSON. You can also convert a Codex auth.json or a ChatGPT Session into its import format.

How to use it: open Account Management → Batch Import, then select multiple JSON files, recursively import a folder, or paste the generated content. A ChatGPT Session usually has no refresh token, so it cannot refresh after expiry; prefer credentials created by the official Codex OAuth flow for long-term use.