Overview
API keys are the primary method for authenticating with AudioPod AI’s APIs. This guide covers everything you need to know about creating, managing, and securing your API keys.Creating API Keys
Your First API Key
- Log into the AudioPod AI account
- Navigate to API Keys in the sidebar
- Click Create New API Key
- Provide a descriptive name for your key
- Copy the generated key immediately
API keys are only shown once during creation. Store them securely as you won’t
be able to see them again.
API Key Naming Best Practices
Use descriptive names that indicate the key’s purpose:production-web-appdevelopment-testingmobile-app-iosstaging-environmentdata-processing-pipeline
Managing API Keys
Viewing Your Keys
The API Keys dashboard shows:- Key name and creation date
- Last used timestamp
- Usage statistics
- Status (active/revoked)
Key Information
For each API key, you can see:- Name: Your custom description
- Created: When the key was generated
- Last Used: Most recent API call
- Requests: Total number of requests made
- Status: Active or revoked
Revoking API Keys
To revoke an API key:- Go to the API Keys page
- Find the key you want to revoke
- Click the Revoke button
- Confirm the action in the dialog
Revoking an API key immediately stops all requests using that key. Ensure you
update your applications before revoking keys used in production.
Security Best Practices
Environment-Specific Keys
Create separate API keys for each environment:Secure Storage
✅ Good Practices:- Store keys in environment variables
- Use secret management services (AWS Secrets Manager, HashiCorp Vault)
- Keep keys in secure configuration files (not in source code)
- Use CI/CD secret management
- Hardcoding keys in source code
- Committing keys to version control
- Storing keys in client-side JavaScript
- Sharing keys via email or chat
Environment Variables Example
- Python
- Node.js
- Docker
Key Rotation
Regular key rotation improves security:Rotation Process
- Create a new API key with a descriptive name
- Update your applications to use the new key
- Test thoroughly in staging environment
- Deploy to production
- Monitor for any issues
- Revoke the old key after confirming success
Recommended Rotation Schedule
- Development: Monthly or as needed
- Staging: Quarterly
- Production: Every 6 months
- Incident Response: Immediately if compromised
Zero-Downtime Rotation
For production systems, implement zero-downtime rotation:Monitoring and Usage
Usage Analytics
Track your API key usage in the dashboard:- Requests per day/week/month
- Credit consumption
- Error rates
- Response times
Setting Up Alerts
Configure alerts for:- Unusual usage patterns
- High error rates
- Credit threshold warnings
- Security events
API Key Metrics
Monitor these key metrics:- Request Volume: Track usage trends
- Error Rate: Identify authentication issues
- Geographic Usage: Detect unauthorized access
- Time Patterns: Unusual usage timing
Troubleshooting
Common Issues
401 Unauthorized
401 Unauthorized
403 Forbidden
403 Forbidden
Causes: - Account suspended - Feature not available in your plan - Rate
limit exceeded Solutions: - Check account status - Verify plan includes
the feature - Implement rate limiting in your code
Key Not Working
Key Not Working
Troubleshooting steps: 1. Verify the key wasn’t accidentally revoked 2.
Check for extra spaces or characters 3. Ensure you’re using the full key 4.
Test with a simple API call
Testing API Keys
Test your API key with a simple request:- cURL
- Python
Advanced Security
IP Whitelisting
For enterprise accounts, you can restrict API key usage to specific IP addresses:- Go to API Keys → Security Settings
- Click Configure IP Restrictions
- Add allowed IP addresses or CIDR ranges
- Save your configuration
Webhook Security
When using webhooks, secure them with:- HTTPS endpoints only
- Signature verification
- IP restrictions
- Rate limiting
Audit Logs
Enterprise accounts have access to detailed audit logs:- API key creation and revocation
- Usage patterns and anomalies
- Authentication failures
- Administrative actions
