GetAPI support channels and safe reporting

Contact us through QQ or Telegram for help with your account, API connection or usage. Never share your API key or password.

Classify the issue

Account: registration, email verification, sign-in, or password recovery.
API key: creation, group, expiry, quota, status, copying, rotation, or suspected exposure.
Client configuration: Codex CLI, a compatible Codex target in CCSwitch, configuration not applying, or a version mismatch.
API request: method/path, authentication, model, endpoint compatibility, status, timeout, or upstream error.
Billing or usage record: current pricing mode, group/unit, request matching, or an unexpected record.
Policy: identify the exact published policy and clause; do not assume a community channel can change formal terms.

Prepare a reproducible report

State GetAPI.ONE as the service and name the guide step where the problem occurs.
Give the exact client and version, operating system, time and timezone, endpoint, model, and key name/group.
Include the HTTP status, complete non-secret error text, request identifier, and whether the console has a matching record.
Describe the smallest reproducible sequence and the checks already completed.
Attach only screenshots or logs that have been reviewed and masked.

Mask secrets before sharing

Remove complete API keys, passwords, email verification codes, cookies, authorization headers, and private configuration tokens.
Mask usernames, emails, account identifiers, balance, billing details, request content, and private project paths/code unless strictly required and shared privately.
If a key may have been exposed, disable or delete it first, rotate the client to a new scoped key, and verify the old key cannot be used.

For billing questions, preserve the request/usage record and the current Live pricing view rather than copying a stale price. For policy questions, link the exact published policy page and clause. This support guide does not reinterpret either.