Skip to content
GetAPI
Dashboard
English
English简体中文繁體中文日本語한국어EspañolPortuguês (Brasil)FrançaisDeutschРусскийItalianoالعربيةTiếng Việt
Appearance
Notifications
Notifications
Loading…
Menu

GetAPI.ONE API quickstart: API key and first request

A complete path from account creation and model selection to a scoped API key, client configuration, and a working first connection.

Start here

To start using GetAPI.ONE, create an account, choose a model and its supported endpoint, then create an API key. Already have a key? Go straight to the Python or Node.js example below. Check current pricing before sending requests.

Before you start

  • Use the official https://www.getapi.one domain and an email inbox you can access for verification.
  • Decide whether you will connect Codex CLI, a compatible Codex target through CCSwitch, or your own API client.
  • Keep a private password manager or environment-variable store ready. Never paste a real key into a public issue, screenshot, or repository.

1. Create and open your account

  1. Open the registration page, choose a username, set an 8–20 character password, and enter your email.
  2. Request the email code, enter it, review and accept the linked User Agreement and Privacy Policy, then create the account.
  3. Sign in with the username or email and password. A successful sign-in opens the overview page.

2. Check balance, endpoint, and model

  1. Confirm the account has usable balance or an applicable package before sending a billable request.
  2. Open the model catalog. Choose a model that explicitly lists the endpoint your client uses; do not infer protocol support from the model name.
  3. Open Live pricing immediately before use. Check the current model, group, pricing mode, and billing unit because availability and prices can change.

3. Create a scoped API key

  1. Open API Keys and select Create API key. Give the key a name that identifies its client or project.
  2. Choose the required group, a specific expiry, and a quota appropriate for this integration. Expand advanced restrictions only when you understand the required access.
  3. Save the key and copy it from the key list into your private store. GetAPI.ONE keeps a manageable list entry, so you can copy the key again later.

4. Connect one client

Use only the path that matches your client. Codex custom-provider configuration uses the Responses wire API and the ONE base URL https://www.getapi.one/v1. A direct API program must use the specific declared endpoint instead of blindly appending paths.

5. Verify and continue

  • Success means the selected client receives a valid response and the GetAPI.ONE console records the request. A local syntax check alone is not a live-call success.
  • For 401, re-copy the ONE key and confirm it is enabled and paired with the ONE address. For 404, verify the exact endpoint or /v1 base expected by the client.
  • For model-not-found, choose a model exposed to the key group and compatible with the endpoint. For quota, rate, network, or upstream errors, preserve the timestamp and request identifier before troubleshooting.