Visit our API Documentation page to learn more:
API Keys
Generate and manage API keys to connect Hatz AI with external platforms and automation tools.
Overview
API keys provide programmatic access while maintaining your existing user permissions and security boundaries.
Who this is for
All Hatz AI users can generate API keys for their own account. The functionality available through the API is limited to what the user already has permission to access within the Hatz AI platform.
How API Keys Work
API keys authenticate your identity when making requests to Hatz AI from external systems. Important security principles:
Each API key is tied to a specific user account
The key inherits all permissions from that user account
Keys only provide access to resources and actions the user can already perform in the platform
Keys do not grant elevated permissions
Generating an API Key
Navigate to Workspace > API Keys
Enter API key name in the intended box
Click the Generate API Key button
Click Copy You will not be able to see this key again. Keep it safe!
Expected Results
Successfully generated API keys can authenticate requests to Hatz AI services
Requests made with the key will execute with the same permissions as if you were logged into the platform directly
Apps available through API calls match what appears in your "My Automations" section
Security Best Practices
Store API keys securely and never share them publicly
Use descriptive names when generating keys to track their purpose
Revoke keys that are no longer in use
Do not commit API keys to public code repositories
Treat API keys like passwords
Removing an API Key
Navigate to Workspace > API Keys
Click the trash icon on the intended key
Click "Yes, delete" - This action cannot be undone.
My API key isn't working
Confirm the key was copied correctly without extra spaces
Check that your user account has permission to perform the requested action
Verify the external platform is configured correctly
Limitations
API keys provide access only to features and data the user already has permission to access in the platform
Keys do not bypass role-based access controls or organizational restrictions
Some features may not be available through API access (for example, Community Automations and Private Automations are not currently accessible via Zapier integration)
Non-admin users may not have the ability to generate API keys depending on organizational settings
API keys are scoped to individual user accounts and cannot be shared across users


