Authentication
All API requests require authentication via a gck_* gateway config key.
API key format
Section titled “API key format”Keys start with the gck_ prefix:
gck_abc123def456...Get your key from the dashboard.
Sending the key
Section titled “Sending the key”Two header options (use either):
Authorization: Bearer gck_your_key_hereX-API-Key: gck_your_key_hereExample request
Section titled “Example request”curl -H "Authorization: Bearer gck_your_key" \ https://ingest.prism.optra-ai.com/v1/telemetry/statsValidation flow
Section titled “Validation flow”When your request arrives:
- Key is validated and matched to your account
- Your organization is resolved from the key
- Key must be active and not expired
- Request proceeds with the resolved org and developer context
Error responses
Section titled “Error responses”| Scenario | Status | Message |
|---|---|---|
| No key provided | 401 | Missing API key |
Non-gck_ prefix | 401 | Invalid API key format |
| Key not recognized | 401 | Invalid API key |
| Key inactive or expired | 401 | API key not active or expired |