Why Glade API keys are reveal-once
A practical key format that supports lookup, constant-time verification, scoped rotation, and safe logs.
Last updated August 14, 2026
A key has two jobs
The lookup prefix lets the service find a candidate record without scanning. The high-entropy secret proves possession. Glade API stores only a keyed HMAC digest and uses constant-time comparison after lookup.
Environment is visible
The test or live marker helps humans avoid accidental credential use. It is not an authorization decision by itself; the stored policy and organization entitlement remain authoritative.
Logs need prefixes, never secrets
Dashboard records can safely reference a short display prefix and key ID. Full credentials, authorization headers, raw IP addresses, and provider credentials are excluded from logs and analytics.
Questions about this page?
Use Support & Feedback from the dashboard so the request is associated with the correct organization without exposing a credential.
Open dashboard support