DigiUsher DocumentationConnecting an OpenAI Platform organization
Connect your OpenAI Platform organization to DigiUsher with an Admin API key to track cost and token usage per API key, project, and model.
Overview
To onboard your OpenAI Platform organization to DigiUsher, you create an Admin API key in the OpenAI Platform dashboard and provide it to DigiUsher. This document describes exactly what access is requested, why it is needed, and what credential to provide.
A paid OpenAI Platform account is required
Free-tier and trial accounts do not support Admin API key creation. You need an active paid OpenAI Platform account. In addition, only members holding the Organization Owner role can create Admin API keys — Member and project-level roles cannot.
Summary of Access Required
| Component | Details |
|---|---|
| Identity | Admin API key (prefix sk-admin) — programmatic access only |
| Access level | Read-only — organization-level cost and usage data |
| Data | Daily cost and token usage data |
| Scope | Your entire OpenAI organization (the key is inherently org-scoped; no separate org identifier is needed) |
| Capability | What It Provides |
|---|---|
| Per-user cost attribution | Spend attributed to each API key owner (by email for human users, by service account name for automated keys) |
| Model breakdown | Cost and token usage per model |
| Token usage | Input, output, cached-input, input-audio, and output-audio token counts (completions only) |
| Credit rows | Negative-value rows (e.g. refunds) are captured as credits |
DigiUsher cannot send requests, consume tokens, or create, modify, or delete anything in your OpenAI organization.
Token counts are available for completions only
Token counts are only available for the Completions API. Other product lines — Embeddings, Images, Audio, Assistants API, and Evals — appear in cost data but have no token counts; ConsumedQuantity is null for those rows.
OpenAI projects appear as cost groupings within your data, not as separate data sources. All spend rolls up to a single DigiUsher connection.
Prerequisites
Information to Gather
| Item | How to Find | DigiUsher Field |
|---|---|---|
| Admin API Key | OpenAI Platform dashboard → Settings → Organization → Admin Keys → Create new admin key (shown once at creation — store securely) | api_key |
Roles Required by the Person Performing Setup
| Role / Permission | Why |
|---|---|
| Organization Owner on the OpenAI Platform organization | Only Organization Owners can create Admin API keys. |
Network & Email Access (For Regulated Environments)
If your organization restricts outbound internet access or email domains, ensure the following are in place before starting:
- Domain allowlist: Add
*.digiusher.comto your network/firewall allowlist so that users in your organization can access the DigiUsher platform from their browsers. - Email allowlist: Add
digiusher.comas an approved sender domain in your email security gateway. DigiUsher sends onboarding confirmations, alerts, and reports from@digiusher.comaddresses.
Setup
Confirm Account & Owner Role
The Admin API requires a paid OpenAI Platform account and the Organization Owner role.
- Sign in to the OpenAI Platform dashboard with an account that holds the Organization Owner role.
- Confirm your account is on an active paid plan. Free-tier and trial accounts cannot create Admin API keys.
- Confirm your role is Organization Owner. If it is not, ask an existing owner to either grant you the role or perform the next step on your behalf.
Don't see Admin Keys under Settings?
If Admin Keys is not visible under Settings → Organization, your account does not hold the Organization Owner role. Ask an existing owner to create the key or grant you the role.
Create an Admin API Key
Create a dedicated Admin API key for DigiUsher with the required scope.
- In the OpenAI Platform dashboard, open Settings → Organization → Admin Keys.
- Click Create new admin key and give it a recognizable name, for example
digiusher-cost-reader. - In the scope picker, explicitly select
api.usage.read. Do not rely on an "All permissions" option — there is a known OpenAI platform issue where creating a key with "All" did not includeapi.usage.read. Always select it explicitly. - Copy the generated key value. It starts with
sk-admin-.
Save your credential
The Admin API key is shown only once at creation and cannot be retrieved again. Copy and store it securely — you will enter it into DigiUsher in the next section.
Note Your Key
Confirm the key you copied:
- Starts with
sk-admin-(notsk-proj-orsk-) - Was created with
api.usage.readexplicitly selected in the scope picker
No separate Organization ID is needed — the Admin key is inherently scoped to your organization.
Connect in DigiUsher
After completing the steps above, enter the following into DigiUsher to complete the connection:
| Field | Where to Find |
|---|---|
| Connection Name | Any label you prefer, for example OpenAI Production |
| Admin API Key | The sk-admin-… key from Step 2 |
When you connect, DigiUsher validates the key and begins importing your organization's cost and usage data. The first sync backfills approximately 31 days anchored to the start of the current month. After that, DigiUsher ingests new data daily.
OpenAI usage data is restated as it finalizes, so the most recent 1–2 days may be incomplete.
Verification Checklist
- Active paid OpenAI Platform account
- You hold the Organization Owner role
- Admin API key created at Settings → Organization → Admin Keys with
api.usage.readscope explicitly selected - Key starts with
sk-admin-and was saved securely - Connection details entered in DigiUsher
-
*.digiusher.comallowlisted in your network/firewall (if applicable) -
digiusher.comallowlisted as an approved sender domain in your email security gateway (if applicable)
Security
What DigiUsher CAN Access (Read-Only)
- Org-level cost data grouped by API key, line item, project, and date
- Completions token usage per API key, model, and batch flag
- Project list and API key metadata (key name, owner email or service account name, project membership)
What DigiUsher CANNOT Do
- Send completions requests or consume tokens
- Create, modify, or delete API keys, projects, users, or org settings
- Access prompt content, completion text, conversation history, or fine-tuning data
- View or modify billing settings, payment methods, spending limits, or rate limits
- Make purchases or any changes to your account
The Admin API key is stored encrypted at rest and is never returned in DigiUsher API responses.
Monitoring
Review Admin Keys in your OpenAI Platform settings to confirm which keys exist and when they were last used. Remove any keys you no longer recognize.
Credential Rotation
- In the OpenAI Platform dashboard, create a new Admin API key with
api.usage.readexplicitly selected. - Update the credential in DigiUsher immediately.
- Delete the old key from the OpenAI Platform dashboard.
Avoid ingestion gaps
Always create the new key and update it in DigiUsher before deleting the old one to avoid an interruption in data ingestion.
Revocation
Delete the Admin API key in your OpenAI Platform settings. This immediately invalidates the key and stops all access. DigiUsher will no longer be able to ingest cost data until a new key is provided.
Troubleshooting
Invalid key or 403 on validation
Confirm the key starts with sk-admin-. Project keys (sk-proj-) and legacy user keys (sk-) are rejected — only an Admin API key works. Re-create the key in the OpenAI Platform dashboard and re-enter it in DigiUsher.
Missing scopes / 403 after a valid key
The key was created without api.usage.read explicitly selected. Revoke the key and create a new one, this time selecting api.usage.read explicitly in the scope picker.
Organization Owner role required
If Admin Keys is not visible under Settings → Organization, your account does not hold the Organization Owner role. Ask an existing owner to create the key or grant you the role.
No cost data / data lower than expected
Usage is restated as it finalizes; the most recent 1–2 days may be incomplete. DigiUsher re-fetches the current month daily so data fills in automatically as OpenAI processes usage.
Token counts missing for some line items
Token counts are available for completions only. Embeddings, Images, Audio, Assistants API, and Evals appear in cost data but show no token usage.
Need Help?
If you encounter any issues not covered above, contact DigiUsher support at support@digiusher.com and the team will help you get set up.