Skip to content
DocsGitHub

dsn

Find Sentry DSNs

List DSNs

Arguments:

Argument Description
<org/project> <org>/ (all projects), <org>/<project>, or <project> (search)

Options:

Option Description
-n, --limit <limit> Maximum number of DSNs to list (default: "25")
-f, --fresh Bypass cache, re-detect projects, and fetch fresh data
-c, --cursor <cursor> Navigate pages: "next", "prev", "first" (or raw cursor string)

All commands support --json for machine-readable output and --fields to select specific JSON fields.

Terminal window
# List client keys for detected projects, including monorepos
sentry dsn list
# List enabled and disabled DSNs for one project
sentry dsn list my-org/my-project
# List DSNs across all accessible projects in an organization
sentry dsn list my-org/
# Navigate between pages
sentry dsn list my-org/ --limit 10 -c next
sentry dsn list my-org/ --limit 10 -c prev
# Select public DSN fields as JSON
sentry dsn list my-org/my-project --json --fields name,dsn,isActive

Each entry shows the project, name, enabled status, creation date, and public DSN available in Sentry's Settings → Projects → Client Keys (DSN). A missing creation date is shown as — (null in JSON). Internal identifiers and private keys are not included in either output format.

Use org/ for the whole organization or org/project for a specific project. A bare name lists matching projects across accessible organizations; when no project matches but an organization does, it lists that organization's DSNs. Add the trailing slash to select an organization even when a project has the same name.

Omit the target to use the usual project config or DSN auto-detection, including multiple projects in a monorepo. --limit caps the total number of DSNs on the page, including organization-wide results. Both organization and project listings support -c next and -c prev. When there are more projects than the limit can display, increase --limit as suggested before continuing; no next cursor is offered that would skip keys.