Providers / Sentry

Monitoring

Sentry API keys and credentials

What every Sentry credential a founder holds does, whether it expires, and what tends to break. Each fact links to Sentry's own docs.

Last checked 2026-11-06 · sentry.io

At a glance

CredentialExpiryPermissions
Sentry dashboard loginNot documented–
User auth token (Personal Tokens)Not documentedCan be scoped
Internal integration tokenDoesn't expireCan be scoped
Organization auth tokenNot documentedFull access only
DSN (Client Key)Not documentedFull access only

Each credential

Sentry dashboard login

Dashboard login. Session and 2FA policy not documented on the pages reviewed. Access depends on organization membership and roles.

Sentry docs

User auth token (Personal Tokens)

Created on the User settings / Personal Tokens page and assigned specific scopes. Bound to the creating user: docs advise against using them for CI because the token stops working if that user leaves the organization. Expiry not documented.

Sentry docs

Internal integration token

Created by creating an internal integration (also available for self-hosted Sentry). An org-wide token is issued on creation. Docs state tokens do not expire automatically and must be revoked manually. Up to 20 tokens per internal integration. Permissions are set on the integration; the exact scope mechanics are not detailed on the page reviewed.

Sentry docs

Organization auth token

Created under Settings > Developer Settings > Organization Tokens by any user, intended for CI such as source map uploads. Permissions are fixed and not customizable. Shown once right after creation; afterwards only the last few characters are visible. Only org owners and managers can revoke. Owners receive a security email on each new token. No expiry period or rotation process is documented.

Sentry docs

DSN (Client Key)

Routes SDK events to a project. Docs state DSNs are safe to keep public because they only allow submitting events. The secret part is optional and deprecated. DSNs can be rotated or revoked in the project's Client Keys (DSN) settings. No expiration is mentioned.

Sentry docs

What usually goes wrong

Renewals and billing

Plan subscription (monthly or annual on Team and Business) plus pay-as-you-go charges for overages on errors, logs, uptime and other products. Spend and usage API availability not confirmed on the pages reviewed.

What Sentry's docs don't say

We couldn't confirm these from official docs, so don't rely on them either way:

Rotating or replacing a Sentry key

The steps are the same for most providers: make the new key, deploy it everywhere the old one is used, check it works, then revoke the old one. Our guides walk through it:

Sources

Keep track of every Sentry key

StackHangar stores your Sentry keys in an encrypted vault, grouped by the product they belong to, warns you before they expire, and walks you through rotating them. We can't read your secrets.