To ensure security and proper usage tracking, all requests to the Lokutor API must be authenticated using an API Key.
Managing API Keys
API keys are provided upon request. Please contact us at [email protected] to request access to our API. We’ll work with you to set up your account and provide the necessary credentials.
Requesting Access
- Send an email to [email protected] with your use case and requirements
- We’ll review your request and get back to you with next steps
- Once approved, you’ll receive your API key via email
Authentication Methods
For our WebSocket API, include your API key as a query parameter in the WebSocket URL.
WebSocket (JavaScript)
WebSocket (Python)
Environment Variable
const ws = new WebSocket(`wss://api.lokutor.com/ws?api_key=YOUR_API_KEY`);
import websocket
ws = websocket.WebSocketApp(
"wss://api.lokutor.com/ws?api_key=YOUR_API_KEY"
)
# Set it locally for testing
export LOKUTOR_API_KEY="your-api-key"
Secure Handling of Keys
Treat your API Keys like passwords. If a key is leaked, it can result in unauthorized charges or usage on your account.
- Never commit your API keys to version control (GitHub, GitLab, etc.).
- Use Environment Variables (
.env files) to store keys on your server.
- Contact us immediately at [email protected] if you suspect your key has been compromised.
- Rotate Keys regularly to minimize the impact of long-term exposure.
Multiple Environments
We recommend creating separate API keys for your Development, Staging, and Production environments. This allows you to monitor usage independently and revoke keys without affecting all your systems.
Rate Limiting
The Lokutor API enforces rate limits to ensure service stability.
| Plan | Limit (Req/min) |
|---|
| Free / Trial | 10 |
| Developer | 100 |
| Business | 500 |
| Enterprise | Custom |
429 Too Many Requests error.