API key setup

Create a DeepSeek API key for backend requests

gogogoapi API keys are designed for server-side DeepSeek calls, with dashboard key creation, revocation, prepaid credits, and request ledger history.

Key handling pattern

Create a key in the dashboard, store it in a server-side secret, and send it as an Authorization bearer token.

Authorization: Bearer $GOGOGOAPI_KEY

# Example endpoint
POST https://www.gogogoapi.com/api/v1/chat/deepseek

Dashboard key lifecycle

Create and revoke backend API keys as your app or agent runtime changes.

Bearer auth

Use the key in the Authorization header from trusted backend environments.

Balance protection

Requests are checked against prepaid API credits before execution.

Decision guide

Key safety checklist

Use this snapshot to decide whether the route matches your first production or smoke-test use case.

Store
Environment variable or secret manager

Never commit the key to source control.

Use
Backend only

Do not paste the key into public frontend code.

Rotate
Dashboard revoke and recreate

Revoke keys that are unused or possibly exposed.

FAQ

Questions before you test

Short answers for the questions developers usually ask before creating the first API key.

Is the API key the same as my wallet?

No. Sign-in and funding happen through the dashboard, while API keys are server-side credentials for model requests.

Can one key call future model routes?

The intended model is one backend key and one prepaid balance across supported routes as they become live.

What happens with insufficient credits?

Requests cannot proceed when the prepaid API credit balance is too low for the quoted request.

Ready to build

Sign in, buy credits, create an API key.

Use the dashboard to fund USD credits with USDT or USDC, create a backend key, and send your first China model API request.

Open dashboard