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.
At a glance
| Credential | Expiry | Permissions |
|---|---|---|
| Sentry dashboard login | Not documented | – |
| User auth token (Personal Tokens) | Not documented | Can be scoped |
| Internal integration token | Doesn't expire | Can be scoped |
| Organization auth token | Not documented | Full access only |
| DSN (Client Key) | Not documented | Full access only |
Each credential
Sentry dashboard login
- Not documented
Dashboard login. Session and 2FA policy not documented on the pages reviewed. Access depends on organization membership and roles.
User auth token (Personal Tokens)
- Not documented
- Can be scoped
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.
Internal integration token
- Doesn't expire
- Can be scoped
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.
Organization auth token
- Not documented
- Full access only
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.
DSN (Client Key)
- Not documented
- Full access only
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.
What usually goes wrong
- User auth token tied to a departing team member stops working and breaks CI or integrations
- Organization auth token lost after its single display, forcing a new token and updating every CI pipeline
- Source map upload fails because a CI organization token has been revoked by an owner or manager
- Internal integration token never expires, so an old leaked token stays valid until someone revokes it manually
- DSN changed or rotated without updating a client app that has the old DSN compiled in
- Team or Business subscription lapses or pay-as-you-go spend limits are hit, causing events to be dropped
Renewals and billing
- Sentry Team or Business plan, billed monthly or yearly. Team is $29/mo monthly or $26/mo billed annually; Business is $89/mo monthly or $80/mo annually per the pricing page. Developer plan is free. Pay-as-you-go charges apply beyond included quotas (for example logs at $0.50/GB over 5GB).
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:
- Whether user auth tokens or organization auth tokens ever expire (none documented; not confirmed)
- Whether expiry or last-used data is readable via the API for any token type
- Exact scope names for user auth tokens and internal integrations
- Whether internal integrations have a client secret or webhook secret credential
- Whether the user auth token value is viewable after creation
- Dashboard login session lifetime and 2FA policy
- Whether a usage or spend API exists for billing data
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
- docs.sentry.io/account/auth-tokens/
- docs.sentry.io/api/auth/
- docs.sentry.io/organization/integrations/integration-platform/internal-integration/
- docs.sentry.io/product/sentry-basics/dsn-explainer/
- sentry.io/pricing/
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.