Authentication
Authentication
All requests use API keys. Send your key in the Authorization header with the Bearer scheme.
Code
Headers you’ll receive
| Header | Description |
|---|---|
x-quikturn-key-id | API key identifier |
x-quikturn-client-id | Customer/tenant id |
x-quikturn-plan | Plan tier (free, launch, growth, enterprise) |
x-quikturn-plan-status | Plan status (e.g., active, trialing) |
x-quikturn-key-status | Key status (e.g., active, paused) |
x-quikturn-quota-remaining | Requests remaining (if provided) |
x-quikturn-quota-reset | Quota reset time (if provided) |
x-request-id | Correlation id for support/debugging |
Plan/status/quota headers appear only if they exist on your account.
Best practices
- Use separate keys per environment (dev/stage/prod).
- Rotate keys periodically and revoke compromised keys.
- Keep keys in environment variables or a secrets manager.
- Always use HTTPS and handle
401/404/429responses gracefully.
Last modified on