DigiUsher - Connecting a ChatGPT Enterprise or Edu account

Connect your ChatGPT Enterprise or Edu organization to DigiUsher with an Admin API key and Organization ID to track AI spend and usage across your organization.

Overview

To onboard your ChatGPT Enterprise or Edu organization to DigiUsher, you locate your Organization ID and create an Admin API key scoped to the compliance cost data endpoint, then provide both to DigiUsher. This document describes exactly what access is requested, why it is needed, and what credentials to provide.

This is not the same as connecting an OpenAI Platform account. ChatGPT Enterprise is managed at chatgpt.com; the OpenAI API Platform is at platform.openai.com. A Platform API key will not work here, and the two products use separate credential systems.

ChatGPT Enterprise or Edu subscription required

Free, Plus, and Pro plans do not expose the Admin API. Only members with the Owner role on the ChatGPT organization can create Admin API keys.

Summary of Access Required

Component	Details
Identity	ChatGPT Enterprise Admin API key — programmatic access only
Access level	Read-only — organization-level cost and usage data
Data	Daily cost and usage data per user, workspace, and model
Scope	A single ChatGPT organization (identified by Organization ID)

Capability	What It Provides
Usage cost	Spend attributed per user and per workspace
Model breakdown	Cost by GPT model
Credit rows	Negative-value rows captured as credits

DigiUsher cannot send messages, access conversation content, or modify anything in your ChatGPT organization.

The required scope must be selected explicitly

The scope chatgpt.enterprise.compliance_logs_platform.costs.read is not included in broad "All permissions" or "All scopes" grants when creating an Admin API key. It must be selected explicitly. Keys created with only "All" will not have access to cost data.

Prerequisites

Information to Gather

Item	How to Find	DigiUsher Field
Organization ID	Sign in to chatgpt.com → navigate to chatgpt.com/admin/settings → Workspace Details section → Organization ID field	`organization_id`
Admin API Key	See Setup below — created in the ChatGPT admin console under Credentials → Admin keys with explicit scope selection; may require a one-time provisioning step with OpenAI support	`api_key`

Roles Required by the Person Performing Setup

Role / Permission	Why
Owner on the ChatGPT Enterprise or Edu organization	Only 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.com to your network/firewall allowlist so that users in your organization can access the DigiUsher platform from their browsers.
Email allowlist: Add digiusher.com as an approved sender domain in your email security gateway. DigiUsher sends onboarding confirmations, alerts, and reports from @digiusher.com addresses.

Setup

Locate Your Organization ID

Sign in to chatgpt.com as an Owner of your Enterprise or Edu organization.
Navigate to chatgpt.com/admin/settings.
Under the Workspace Details section, copy the Organization ID value.

Keep this value handy — you will enter it in DigiUsher alongside your API key.

Create an Admin API Key with the Required Scope

ChatGPT Enterprise cost data is accessed via the Compliance Logs Platform API, which requires a specific scope that is not part of standard permission bundles. Admin keys are created in the ChatGPT admin console — not at platform.openai.com.

Sign in to chatgpt.com/admin as an Owner of your Enterprise or Edu organization.
Before creating a key, ensure Audit logging is enabled: on the Data controls page, open the Data retention tab and enable Audit logging.
Go to Credentials → Admin keys and click Create new Admin key.
In the scope selection screen, locate and explicitly select: chatgpt.enterprise.compliance_logs_platform.costs.read

To find it quickly, search for costs or compliance in the scope list.
Do not select "All permissions" or "All scopes" as a shortcut — this scope is intentionally excluded from those bundles and must be selected individually.
Give the key a recognizable name, for example digiusher-cost-reader.
Create the key and copy the value — it is shown only once.

Save your credential

The API key is shown only once at creation and cannot be retrieved again. Copy and store it securely before proceeding.

If the compliance cost scope is not visible in the scope picker

OpenAI may require a one-time enablement step for your organization before this scope appears. Contact OpenAI Enterprise support and ask them to enable the Compliance Logs Platform cost data scope (chatgpt.enterprise.compliance_logs_platform.costs.read) for your organization's Admin keys. Once enabled, return to this step and create the key.

Confirm What You Have

Before connecting DigiUsher, verify:

Organization ID — copied from chatgpt.com/admin/settings → Workspace Details.
Admin API key — created with chatgpt.enterprise.compliance_logs_platform.costs.read explicitly selected.
The key was not created with "All permissions" only.

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 `ChatGPT Enterprise`
Organization ID	From Step 1
Admin API Key	From Step 2

When you connect, DigiUsher validates the key and Organization ID, then begins importing cost and usage data. The first sync backfills approximately 31 days of data anchored to the start of the current month. After that, DigiUsher ingests new data daily. Usage data for the most recent 1–2 days may be restated as OpenAI finalizes it.

Verification Checklist

ChatGPT Enterprise or Edu subscription active
You hold the Owner role on the ChatGPT organization
Organization ID copied from chatgpt.com/admin/settings → Workspace Details
Admin API key created with chatgpt.enterprise.compliance_logs_platform.costs.read explicitly selected (not "All permissions")
API key saved securely
Organization ID and API key entered in DigiUsher
*.digiusher.com allowlisted in your network/firewall (if applicable)
digiusher.com allowlisted as an approved sender domain in your email security gateway (if applicable)

Security

What DigiUsher CAN Access (Read-Only)

Organization-level cost data grouped by user, workspace, model, and date
Usage quantities attributed to individuals and workspaces

What DigiUsher CANNOT Do

Send messages or access conversation history, prompts, or responses
Create, modify, or delete users, workspaces, or organization settings
Access uploaded files, system prompts, or any user-generated content
View or modify payment methods, seat counts, or plan settings
Make purchases or any changes to your account

The API key is stored encrypted at rest and is never returned in DigiUsher API responses.

Monitoring

Review Admin keys in the ChatGPT admin console under Credentials → Admin keys. Confirm which keys exist and when they were last used. Remove any keys you no longer recognize.

Credential Rotation

Create a new Admin API key in the ChatGPT admin console (Credentials → Admin keys) with the compliance cost scope explicitly selected.
Update the key in DigiUsher immediately.
Delete the old key.

Avoid ingestion gaps

Always create the new key and update DigiUsher before deleting the old one to avoid an interruption in data ingestion.

Revocation

Delete the Admin key in the ChatGPT admin console under Credentials → Admin keys. 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

403 / unauthorized after providing a valid key

The most common cause is a missing scope. Confirm the key was created with chatgpt.enterprise.compliance_logs_platform.costs.read explicitly selected — not just "All permissions." Revoke the key and create a new one, selecting the scope by name.

Compliance cost scope not visible in the scope picker

OpenAI may need to enable the Compliance Logs Platform for your organization. Contact OpenAI Enterprise support and request enablement of the chatgpt.enterprise.compliance_logs_platform.costs.read scope. Once confirmed, create the key and reconnect.

Wrong key type / 401 error

Confirm this is an Admin API key created in the ChatGPT admin console (Credentials → Admin keys) for your Enterprise organization — not a standard user API key or a project key from platform.openai.com. Admin keys begin with sk-admin-. The key should be explicitly scoped to the compliance cost endpoint.

Organization ID not recognized

Confirm the Organization ID was copied from Workspace Details at chatgpt.com/admin/settings. Do not use a workspace or project ID from other settings pages.

No cost data after connecting

Data may take up to 24 hours to appear after a new connection.
Usage for the current day appears after the next daily sync.
Confirm the Organization ID matches the Enterprise organization where usage is occurring.

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.

Connecting a ChatGPT Enterprise or Edu account

On this page