Overview
The Fabraix API uses API keys to authenticate requests. You can view and manage your API keys in the Fabraix Dashboard.Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.
Authentication Method
All API requests must include your API key in thex-api-key header:
API Key Types
Fabraix provides different types of API keys for different use cases:Development Keys
For local development and testing. These keys have relaxed rate limits but should never be used in production.
Production Keys
For production deployments. These keys have higher rate limits and access to production features.
Restricted Keys
Keys with limited scope for specific operations. Perfect for client-side applications or third-party integrations.
Admin Keys
Full access keys for administrative operations. Use with extreme caution.
Managing API Keys
Creating a New API Key
- Navigate to the API Keys page in your dashboard
- Click “Create New Key”
- Select the key type and permissions
- Give your key a descriptive name
- Copy the key immediately - it won’t be shown again!
Rotating API Keys
We recommend rotating your API keys regularly:1
Create a New Key
Generate a new API key with the same permissions as the old one
2
Update Your Application
Deploy your application with the new API key
3
Verify Functionality
Ensure your application is working correctly with the new key
4
Revoke the Old Key
Delete the old API key from your dashboard
Revoking API Keys
To immediately revoke an API key:- Go to the API Keys page
- Find the key you want to revoke
- Click the “Delete” button
- Confirm the deletion
Revoking an API key is immediate and irreversible. Make sure you have updated your applications to use a different key before revoking.
Security Best Practices
Environment Variables
Never hardcode API keys in your source code. Use environment variables instead:Secret Management
For production environments, use a proper secret management system:- AWS: AWS Secrets Manager or Parameter Store
- Azure: Azure Key Vault
- Google Cloud: Secret Manager
- Kubernetes: Kubernetes Secrets
- HashiCorp: Vault
Client-Side Security
Never expose your secret API keys in client-side code. For browser-based applications, use:
- A backend proxy that adds the API key to requests
- Restricted keys with limited permissions
- Short-lived tokens generated by your backend
Rate Limiting
API keys are subject to rate limiting to ensure fair usage:| Key Type | Requests per Minute | Requests per Hour |
|---|---|---|
| Development | 60 | 1,000 |
| Production | 600 | 10,000 |
| Enterprise | Custom | Custom |
429 Too Many Requests response:
Error Responses
Authentication failures will return appropriate HTTP status codes:401 Unauthorized
Missing or invalid API key:403 Forbidden
Valid key but insufficient permissions:Need Help?
If you’re having trouble with authentication:- Verify your API key is correct and active in the dashboard
- Check that you’re using the correct header name:
x-api-key - Ensure your key has the necessary permissions for the operation
- Contact zach@fabraix.com if issues persist

