API Key Authentication
All requests to the Firemoon Studio API require authentication using an API key in theAuthorization header.
Getting Your API Key
- Contact us at contact@firemoon.studio
- Include your use case and expected usage volume
- Receive your API key via email
Keep your API key secure and never share it publicly.
Using Your API Key
Include the API key in theAuthorization header with the Bearer prefix:
Example Requests
cURL
JavaScript
Python
Security Best Practices
Environment Variables
Store your API key as an environment variable:Key Rotation
- Rotate API keys regularly (recommended: every 30-90 days)
- Use different keys for different environments (dev/staging/prod)
- Immediately revoke compromised keys
Monitoring
- Monitor API usage in your dashboard
- Set up alerts for unusual activity
- Log authentication failures
Test Keys
For development and testing, you can use these test API keys:| Key | Description | Rate Limit | Providers |
|---|---|---|---|
test_key_12345 | Full access test key | 60 req/min | All providers |
demo_key_67890 | Limited access key | 30 req/min | flux, ideogram only |
Test keys are for development only and should not be used in production.
Troubleshooting
401 Unauthorized
- Verify your API key is correct
- Check that you’re using the
Bearerprefix - Ensure the key hasn’t expired
403 Forbidden
- Confirm your key has access to the requested provider
- Check if you’ve exceeded rate limits
- Verify your account is in good standing