Organization API Keys
When working within an organization, you need to create organization-scoped API keys to attribute usage to the organization's account. Personal API keys always bill to your individual account, so you must create separate keys within the organization context.
Creating an Organization API Key
The process is the same as creating a personal API key, but you must first switch to your organization context:
- Switch to your organization context from the profile menu (see Organizations Overview)
- Navigate to the API keys page
- Click Create API Key
- Give your key a descriptive name and click Create
Name your organization keys descriptively (e.g., "prod-pipeline", "research-team") so you can easily identify them later.
The key you create will be scoped to the organization. Any API requests made with this key will:
- Bill to the organization's credit balance, not your personal balance
- Appear in the organization's usage logs — your usage (not the key itself) is visible to the organization for billing transparency
- Track your identity as the creator for attribution purposes
Using Organization API Keys with the OpenAI SDK
Organization API keys work identically to personal keys. Simply use them in your API client configuration as described in the getting started guide:
Key Differences from Personal API Keys
| Personal API Key | Organization API Key | |
|---|---|---|
| Billing | Charges your personal balance | Charges the organization's balance |
| Visibility | Only you can see your key and usage | Your key is private; usage is visible to the organization |
| Creation | Created in personal context | Created while in organization context |
| Attribution | Attributed to you | Attributed to the organization, with your identity tracked |
Each member creates their own organization API keys. This means usage is always traceable to the individual who made the request, even though billing goes to the organization.