All Shasta Health API requests are authenticated with an API key passed in the Authorization header. This guide walks through generating a key, storing it securely, and using it in your requests.
Never commit API keys to source control. Use environment variables or a secrets manager instead.
Store the key in an environment variable such as SHASTA_HEALTH_API_KEY.
In production, use a secrets manager like AWS Secrets Manager, Google Secret Manager, HashiCorp Vault, or your platform’s built-in secrets (e.g. Vercel Environment Variables).
Restrict access to the key to only the services and team members that need it.
Rotate keys periodically and revoke any that are no longer in use.