Remove a team member

Take someone out of a team.

DELETE/workspaces/{workspace}/teams/{team}/members/{username}

They lose the roles the team gave them on repositories, unless they have them otherwise. Owners of the workspace and the team’s maintainers; anyone may leave a team themselves. People only. Returns true.

Anyone may take themselves out of a team. Leaving the workspace takes a person out of all its teams.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: team with action remove_member, and the same inputs
Scope: An access token needs workspace:admin.

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s slug, e.g. “flagon-io”.
`team`	string	Yes	The team’s slug, as in its mention @workspace/slug, e.g. “backend”.
`username`	string	Yes	The person’s username.

Example request

curl -X DELETE https://api.g1t.sh/workspaces/flagon-io/teams/backend/members/ana \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

true

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.