API key types
All API requests require authentication using either:- Organization API Keys - Created by Organization Admins in Settings > API access
- Personal Access Tokens (PAT) - User-scoped tokens created in a user’s profile settings Note: If connecting to the MCP Server via OAuth, Omni will automatically create an MCP OAuth PAT for the authenticating user. See the MCP Server authentication documentation for more information.
| Organization API key | Personal Access Token (PAT) | MCP OAuth PAT | |
|---|---|---|---|
| What’s it for | Systems integrations, automated workflows, and API endpoints inaccessible to PATs | Individual user workflows using any PAT-compatible API endpoint | Connecting to the MCP Server via OAuth |
| Who can create | Organization Admins | Modeler+ users | Any user |
| Permissions | Organization Admin | Creating user’s permissions | Creating user’s permissions |
| Where to create | Settings > API access > Organization keys | Profile > Manage account > Generate token | Automatically created during the MCP OAuth flow |
| Where to view | Settings > API access > Organization keys | Settings > API access > Personal tokens | Not currently visible in the app |
Authorization header
Include your token in theAuthorization header as: Bearer YOUR_API_KEY:
Organization API keys
Organization Admin permissions are required to create and access organization API keys.
Creating Organization API keys
To create an API key:In the modal that displays, enter a descriptive name for the API key.Note: API keys will inherit the user attributes of the user who created the key. Enter something that distinguishes you as the creator, such as your initials, into the key’s Name field to make it easy to identify who created the key. This can be helpful when troubleshooting permission issues.
Revoking an Organization API key
Unlike disabling an API key, revoking permanently deletes the API key from your Omni instance.API key expiration
API keys do not expire, but they may be revoked by the user at any time. In the event that your API key is lost or compromised, delete the API key in your Omni instance and create a new one. API keys are tied to the current state of the user who created them. If the creator’s user attributes change or the user is revoked, the associated key will reflect that change.Personal Access Tokens (PAT)
Personal access tokens (PAT) allow individual users to use the Omni API with their own permissions, rather than using an Organization API key. A PAT is scoped to the user who creates it and will inheirit their in-app permissions.Inaccessible endpoints
PATs cannot be used for authentication with the following endpoints, as an Organization API key is required:- Document export
- Document import
- Create email only user
- Bulk create mail-only users
- All SCIM user & user group endpoints
Creating PATs
Enable Personal Tokens for your Omni instance
First, an Organization Admin has to enable the Settings > API access > Personal tokens setting. This allows users in the instance to create PATs.