DOCUMENTATION
Keys & security
Key storage, revocation and permissions.
Lifecycle#
- Send keys only in Authorization: Bearer, never in URLs, cookies, queries, localStorage, repositories or public JS/mobile bundles.
- Keep secrets in a server-side secret manager. They are shown once; only an ID and prefix remain visible.
- On compromise, immediately revoke and replace the key. Rotation does not reset quota.
- Redact logs: Authorization, OAuth codes, verifiers, tokens and download tickets must not reach analytics.
Scopes and roles#
Developer rh_live_ keys are read-only and do not inherit an admin session. Writes and download-ticket issuance require a delegated rh_user_ token. Unpublished content does not become public.
Run requests in your client#
The documentation shows captured HTTP responses and copyable code. It never asks for keys, invokes the API or stores secrets. Run requests in your own client.