Feeling bold?
Sentry's Docs BotAsk A Bot
Product
API
Changelog
Sandbox
Sign In

Delete an Organization Member from a Team

DELETE /api/0/organizations/{organization_slug}/members/{member_id}/teams/{team_id_or_slug}/

Delete an organization member from a team.

Note the permission scopes vary depending on the type of authorization token. The following table outlines the accepted scopes.

Org Auth Token
  • • org:write
  • • org:admin
  • • team:admin
User Auth Token
  • • org:read*
  • • org:write
  • • org:admin
  • • team:admin
  • • org:read + team:admin**

*org:read can only be used to remove yourself from the teams you are a member of.

**Team Admins must have both org:read and team:admin scopes in their user authorization token to delete members from their teams.

Path Parameters

organization_slug (string)
REQUIRED

The slug of the organization the resource belongs to.

member_id (string)
REQUIRED

The ID of the organization member to delete from the team

team_id_or_slug (string)
REQUIRED

The id or slug of the team the resource belongs to.

Scopes

<auth_token> requires one of the following scopes:
  • org:admin
  • org:read
  • org:write
  • team:admin
curl https://sentry.io/api/0/organizations/{organization_slug}/members/{member_id}/teams/{team_id_or_slug}/ \
 -H 'Authorization: Bearer <auth_token>' \
 -X DELETE
RESPONSESCHEMA
{
  "id": "4502349234123",
  "slug": "ancient-gabelers",
  "name": "Ancient Gabelers",
  "dateCreated": "2023-05-31T19:47:53.621181Z",
  "isMember": false,
  "teamRole": null,
  "flags": {
    "idp:provisioned": false
  },
  "access": [
    "alerts:read",
    "event:write",
    "project:read",
    "team:read",
    "member:read",
    "project:releases",
    "event:read",
    "org:read"
  ],
  "hasAccess": true,
  "isPending": false,
  "memberCount": 3,
  "avatar": {
    "avatarType": "letter_avatar",
    "avatarUuid": null
  }
}