Skip to main content
A token is a credential you create in the OpenOpen8 dashboard that authorizes API calls on your behalf. Every request to OpenOpen8 must include a valid token. You can create multiple tokens — for example, one per application or environment — and set independent quotas, expiry dates, and model restrictions on each.
Tokens are different from the API keys your admin enters when configuring channels. Channel API keys belong to your upstream provider accounts; tokens are issued by OpenOpen8 itself.

​
Create a token

1

Open the Tokens page

Log in to the OpenOpen8 dashboard and click Tokens in the sidebar.
2

Click Add Token

Click the Add Token button. A creation form opens.
3

Set a name

Enter a name that identifies what this token is for — for example, my-app-production or data-pipeline. Names are only visible inside the dashboard and don’t affect how the token works.
4

Configure quota

The Quota field sets the maximum number of credits this token can consume.
  • Set it to 0 to allow unlimited usage (the token draws from your account balance with no per-token cap).
  • Set a positive value to cap spending for this token. Once the quota is exhausted, requests with this token return an error until you top it up.
Use per-token quotas to prevent a single application from consuming all your credits if it encounters a bug or runaway loop.
5

Set an expiry date (optional)

Leave the expiry field blank for a token that never expires. Set a date if you want the token to stop working automatically — useful for contractor access, temporary integrations, or short-lived scripts.
6

Restrict to specific models (optional)

Leave the Allowed models field blank to permit all models available on your account. Enter a list of model names to restrict this token to only those models. Requests for any other model will be rejected.
7

Add an IP whitelist (optional)

Enter one or more IP addresses or CIDR ranges in the IP whitelist field. When set, requests from any IP not on the list are rejected. Leave it blank to allow requests from any IP.
8

Assign a group (optional)

Groups let your admin apply different pricing ratios or rate limits to sets of tokens. If your admin has configured groups, select the appropriate one here.
9

Save the token

Click Save. The dashboard displays the token value once. Copy it now — you cannot retrieve the full key again after closing the dialog.
Store your token in a secrets manager or environment variable. Do not commit it to source control.

​
Use a token in API requests

Pass your token in the Authorization header using the Bearer scheme: 
curl https://openopen8.ai/v1/chat/completions \
  -H "Authorization: Bearer sk-..." \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4o",
    "messages": [{"role": "user", "content": "Hello"}]
  }'
OpenOpen8 also accepts tokens in the Claude and Gemini header formats — see Authenticate requests to OpenOpen8 for details.

​
View token usage

The Logs page records every request made through your account. To filter by a specific token:
  1. Open Logs in the sidebar.
  2. Use the Token filter to select the token you want to inspect.
Each log entry shows the model used, token counts, credit cost, and timestamp.

​
Manage existing tokens

From the Tokens list you can:
  • Edit — Update the token’s name, quota, expiry, model restrictions, IP whitelist, or group at any time. Changes take effect immediately.
  • Disable / enable — Toggle a token’s status to temporarily block requests without deleting it.
  • Delete — Permanently remove a token. Any application using that token will immediately start receiving authentication errors.
Create a separate token for each application or service you connect to OpenOpen8. This makes it easy to track which application is consuming credits, and lets you revoke access to one without affecting the others.