Example of Service Keys
If an Admin creates a service key for a data ingestion service that only needs access to Space A, the service key can be restricted to just that space—even if the Admin has access to multiple spaces. This follows the principle of least privilege for automated systems.Create a Service Key
- Go to Space Settings → API Key.
- Click Generate Service Key.
- Set the permissions for the service key. You can only assign permissions equal to or below your current access level.
- Name your service key to identify its purpose (e.g., “Production Data Pipeline” or “QA Environment”).
- Click Generate.
- Copy and save the key immediately. For security, the full key is shown only once during creation.
Key Differences from User Keys
- Persistence: Service keys remain active even if the creator leaves the organization
- Restricted Permissions: Can be configured with limited permissions for specific use cases
- Bot User Association: Each service key is tied to a bot user account rather than a human user
- Organizational Continuity: Designed for long-running services and automation
Where You Can Use It
The same service key authenticates every Arize client and workflow:pandaslogger- Dataset uploads & validations
- Experiments
- Exports
- GraphQL & REST endpoints
- Anything supported by the Arize SDK v7.40.1+
Who Can Create Service Keys
- Admins: Can create service keys with any permission level up to Admin access
- Members: Can create service keys with permissions up to Member access level
- Viewers: Cannot create service keys