Skip to content
GetAPI
English
English简体中文繁體中文日本語한국어EspañolPortuguês (Brasil)FrançaisDeutschРусскийItalianoالعربية
Menu

GetAPI.ONE

Use the source-described CCSwitch workflow with GetAPI.ONE

A bounded desktop configuration guide for compatible Codex targets exposed by CCSwitch, with an explicit boundary around the official ChatGPT consumer app.

Compatibility boundary

The GetAPI source calls this workflow “Codex/ChatGPT” and instructs users to add an OpenAI-compatible provider through the third-party CCSwitch application. The official ChatGPT desktop page reviewed on 2026-09-07 documents installing the app and signing in with a ChatGPT account, but does not document an arbitrary third-party API-provider field.

Prerequisites

  • A compatible Codex client or integration target already identified in your current CCSwitch release.
  • CCSwitch obtained from its project release page and installed according to that project’s current instructions.
  • A private, scoped GetAPI.ONE key and a model that explicitly declares the Responses endpoint.
  • The ONE base URL https://www.getapi.one/v1. Do not mix it with another service’s key or URL.

1. Add the custom provider

  1. Open CCSwitch and select its Codex provider area.
  2. Select the add control, then choose Custom configuration. Scroll if the option is below the initial view.
  3. Name the provider GetAPI One and optionally enter https://www.getapi.one as its website.
  4. Paste the GetAPI.ONE key into the API Key field and https://www.getapi.one/v1 into the API request address field.
  5. Replace YOUR_RESPONSES_MODEL with an exact catalog model visible to the key group and explicitly marked for the Responses endpoint, then save.
FieldONE value
Provider nameGetAPI One
Website (if requested)https://www.getapi.one
API KeyYour private GetAPI.ONE key
API request addresshttps://www.getapi.one/v1
Default modelYOUR_RESPONSES_MODEL (replace it)
CCSwitch custom-provider form with blank API key and API request address fields highlighted
Existing local image inspected on 2026-09-07. It contains placeholders only; enter the ONE values from the table.

2. Enable, restart, and confirm the target

  1. Return to the provider list and enable GetAPI One.
  2. Fully quit and reopen the compatible target so it reloads provider configuration.
  3. Confirm the selected provider and model are GetAPI One and the exact catalog model you entered before sending anything.

3. Verify the connection

  1. Only after reviewing current pricing, send one minimal message you accept may be billed.
  2. Confirm the target receives a valid response.
  3. Confirm a corresponding request or usage record appears in the GetAPI.ONE console. No live model request was made while producing this guide.

Common failure branches

SymptomCheck
401 / UnauthorizedRe-copy the ONE key, confirm it is enabled, and pair it only with the ONE address.
404 / Not FoundKeep /v1 in the CCSwitch request address and check whether the target appended an incompatible path.
Model not foundUse the exact model name visible to the key group and marked for the required endpoint.
No change after enablingConfirm the right CCSwitch target/provider is enabled, fully restart the target, and inspect whether the installed version supports this workflow.
Timeout or no responseCheck balance, key quota/expiry, rate limit, network, gateway status, and upstream error details in that order.