Every client app has exactly one API key at a time — it's what your app's recording SDK uses to authenticate uploads (see
RecordingUploader in Configuration Reference). It behaves like a Sentry DSN: visible any time in the dashboard, not a one-time secret you have to store perfectly on first sight, and safe to regenerate if you suspect it's leaked.
Viewing a key#
Select an organization, and each client app under it shows its current API key inline.
Regenerating a key#
Click Regenerate key next to a client app. This immediately invalidates the old key — any app build still using it will start failing to upload — and shows the new one once, in the same banner used when a client app is first created.
Regenerating is immediate and has no grace period. Only do this if you're ready to roll the new key out to every build that uploads under this client app, or you'll lose uploads from anything still using the old one until it's updated.
What the key does and doesn't protect#
The API key proves an upload came from a legitimate integration of a specific client app. That's the only credential the SDK needs — which organization and client app a recording belongs to is derived entirely from the key server-side, never sent (or trusted) from the client — see Organizations & Client Apps.