Credentials
General guidance for obtaining, storing, rotating, and revoking API credentials.
Working scaffold: The credential creation screens, scopes, expiration rules, and revocation behavior must be confirmed for ONE.
Keep credentials out of client code
Store private credentials in a server-side environment variable or secret manager. Do not commit them to source control, embed them in a browser bundle, include them in screenshots, or log them with request data.
Use a placeholder name in examples until ONE's canonical credential name and configuration flow are confirmed:
PLATFORM_API_KEY=<secret value supplied through a secure channel>Apply least privilege
Use a credential with only the access required by the application. If the platform supports scopes, project restrictions, expiration, or IP restrictions, explain those controls and their limits here rather than implying they exist.
Rotation and revocation
Document how to create a replacement credential, deploy it without exposing the value, verify the new credential, and revoke the old one. Confirm expected propagation time and recovery behavior before publishing operational steps.
See the authentication reference for the eventual wire-level contract.