Authentication

All API requests require authentication via an API key.

API key format

Two key prefixes are accepted — prism_ (current, native Prism keys) and gck_ (legacy keys, still accepted):

prism_abc123def456...
gck_abc123def456...

Both prefixes authenticate the same way. New keys use the prism_ prefix; existing gck_ keys keep working. Keys are created and issued by Prism from the Connect panel in the dashboard header.

Sending the key

Two header options (use either):

Authorization: Bearer prism_your_key_here

X-API-Key: prism_your_key_here

Example request

curl -H "Authorization: Bearer prism_your_key" \
  https://ingest.optra-prism.com/v1/telemetry/stats

Validation flow

When your request arrives:

1. Key is validated and matched to your account
2. Your organization is resolved from the key
3. Key must be active and not expired
4. Request proceeds with the resolved org and developer context

Error responses

Scenario	Status	Message
No key provided	401	Missing API key
Prefix other than prism_ / gck_	401	Invalid API key format
Key not recognized	401	Invalid API key
Key inactive or expired	401	Invalid API key

An inactive, revoked, or expired key is filtered out by the key lookup itself, so it is indistinguishable from an unrecognized key — both return Invalid API key.