Isolated test and live project keys
Hosted and proxy requests now select the intended project-key environment explicitly instead of relying on an ambiguous active key.
Mohith / 4 min read- Slots
- Test and live
- Placement
- Server only
- Raw secret
- Revealed once
What changed
Hosted configuration and proxy paths now carry an explicit environment through server-side key selection. Test and live credentials can coexist without allowing one active key to be substituted implicitly for the other.
Why the browser gets neither key
A project key authenticates one backend environment to the engine. It does not identify an end user or replace application authorization. Public browser configuration therefore exposes a client identifier, not either project API key.
Reveal and rotation behavior
Raw project key material is revealed once after generation or rotation. The dashboard then operates on bounded metadata such as environment, status, last use, usage, quota, and revocation state instead of displaying the secret again.
Availability
Separate test and live key slots are available for the implemented hosted and proxy paths. Teams must still store each value in a trusted server environment or secret manager and rotate or revoke it through the project lifecycle controls.