API Keys
Complete guide to managing API keys for the Nolano forecasting API
Managing API Keys
You can manage your API keys either through the Nolano API or directly from the dashboard.
Go to API Keys Dashboard
The dashboard provides an easy-to-use interface for all your API key management needs.
What are API Keys?
API keys are unique identifiers that authenticate your requests to the Nolano API. They act as both an identifier and a password, ensuring that only authorized users can access forecasting services and manage API resources.
Key Features
Secure by Design
SHA-256 Hashing
Keys are hashed before storage - original keys are never stored in plain text
Usage Tracking
Every API call is logged with detailed usage statistics and monitoring
Expiration Control
Set custom expiration dates or create keys that never expire
Instant Revocation
Immediately revoke compromised keys with audit trails
API Key Lifecycle
Permission System
Available Permissions
read
read
Grants access to:
- Forecast generation endpoints
- Data retrieval operations
- Usage statistics viewing
Use cases:
- Read-only applications
- Analytics dashboards
- Monitoring systems
write
write
Grants access to:
- All read permissions
- Data modification operations
- Forecast parameter updates
Use cases:
- Production applications
- Data processing pipelines
- Interactive forecasting tools
admin
admin
Grants access to:
- All read and write permissions
- API key management operations
- Account settings modification
Use cases:
- Administrative tools
- Key management systems
- Account management dashboards
delete
delete
Grants access to:
- All other permissions
- Data deletion operations
- Forecast history cleanup
Use cases:
- Data management tools
- Cleanup operations
- Administrative scripts
Permission Examples
Usage Monitoring
Key Metrics
Every API key tracks detailed usage information:
Usage Count
Total number of API requests made with this key
Last Used
Timestamp of the most recent API request
Status
Current status: active, expired, or revoked
Viewing Usage Statistics
Example Response:
Security Best Practices
Storage and Handling
Never expose API keys in client-side code: API keys should only be used in server-side applications where they can be kept secure.
Environment Variables: Store API keys in environment variables, not in your source code.
Regular Rotation
Implement a regular key rotation schedule:
- Production Keys: Rotate every 90 days
- Development Keys: Rotate every 30 days
- Emergency Rotation: Immediately if compromise suspected
Rate Limits by Key Type
Permission Level | Requests/Min | Requests/Hour | Requests/Day |
---|---|---|---|
Read Only | 50 | 500 | 10,000 |
Read/Write | 100 | 1,000 | 50,000 |
Admin | 200 | 2,000 | 100,000 |
Full Access | 500 | 5,000 | 250,000 |
Enterprise Plans: Custom rate limits and dedicated support available. Contact support@nolano.com for details.