Skip to main content

​
Usage

sentry team list [target]
List teams in an organization, with flexible targeting and cursor pagination.

​
Target Specification

sentry team list               # auto-detect from DSN or config
sentry team list <org>/        # list all teams in org (paginated)
sentry team list <org>/<proj>  # list teams in org (project context)
sentry team list <org>         # list teams in org

​
Flags

​
--limit
number
default:"100"
Maximum number of teams to retrieve per pageAlias: -n
​
--cursor
string
Pagination cursor. Use last to continue from the last page.Only applicable when using org-scoped listing (e.g., <org>/). The cursor is automatically saved between invocations.Alias: -c
​
--json
boolean
default:"false"
Output as JSON

​
Examples

​
List teams (auto-detect)

sentry team list

​
List teams in specific org (paginated)

sentry team list my-org/

​
List teams with project context

sentry team list my-org/my-project

​
Continue to next page

sentry team list my-org/ -c last

​
Show more teams per page

sentry team list my-org/ --limit 200

​
Output as JSON

sentry team list --json

​
Output

​
Human-readable format

Displays a table with:
  • ORG - Organization slug
  • SLUG - Team slug
  • NAME - Team display name
  • MEMBERS - Number of team members (right-aligned)

​
JSON format

Returns an array of team objects, each containing:
  • slug - Team slug identifier
  • name - Team display name
  • memberCount - Number of team members
  • orgSlug - Organization slug (when listing across orgs)
  • Additional fields from the Sentry API

​
Modes

The command supports different resolution modes:
  • Auto-detect: Uses DSN from source code or config
  • Org-all (<org>/): Lists all teams with cursor pagination
  • Explicit (<org>/<project>): Lists teams for the org (project provides context)
  • Project search (<project>): Finds project across all orgs, lists teams for that org

​
Notes

  • Cursor pagination is only available in org-scoped mode (<org>/)
  • When using project context, teams are listed for the project’s parent organization
  • The cursor is automatically persisted between invocations

Build docs developers (and LLMs) love

Get started for freeTalk to us