Back to guide
Organizations
Group API keys under a team, firm, or client-specific container
Organizations group one user’s API keys under named containers. They do not grant access to another member’s journal. They are useful when the same account powers multiple integrations or when a team wants a clean namespace.
- Sections
- 5
- Reading time
- 1 min
- Opens in app
- Manage orgs
What an organization is
An organization is a lightweight container with a name, slug, owner, and members. It exists to keep developer assets organized without changing the rest of the app model.
Why it exists
Organizations make it possible to create keys for yourself or for an external team/workspace without mixing every integration into one list.
How it relates to API keys
When you create a key in Settings → Developer, the Owner field lets you keep it personal or group it under one of your organizations. The key list shows each key's organization, and Replace key keeps it when you rotate an expiring key.
Where to manage them
Add organizations in the Organizations section of the API keys tab. Each one shows its slug, your role, and how many active keys it groups. Organizations are labels only: a key under one still reads just your own account. Use an OAuth app when other people should connect their own accounts.
Current scope
This first version is focused on key ownership and management. It does not change the trading data model itself.
Org docs
Where organization ownership is explained.