All requests to the Klyra API require authentication using your API key. Your API key carries many privileges, so be sure to keep it secure. Don’t share your API key in publicly accessible areas such as GitHub, client-side code, or in your frontend applications.
You can generate API keys from the Klyra Dashboard. Each project can have multiple API keys with different permissions.
Log in to your Klyra Dashboard
Navigate to the Projects section
Select your project or create a new one
Go to API Keys in the project settings
Click “Generate New Key”
We recommend creating separate API keys for development and production environments. This makes key rotation and revocation easier in case of a security incident.
If an API key is compromised, you should immediately revoke it from the Klyra Dashboard:
Log in to your Klyra Dashboard
Navigate to your project settings
Find the compromised key and click “Revoke”
Generate a new key to replace the revoked one
Revoking a key immediately stops it from working. Ensure you’ve updated your application with a new key before revoking an active one to prevent service disruption.
For enterprise customers, Klyra offers Organization Access Keys that provide more granular permissions and can be restricted to specific actions or resources. Contact our support team to learn more about organization-level access controls.