Remove a member

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

Their roles on its repositories and their place in its teams go too; to keep them on a repository, add them back to it as an outside collaborator. Removing yourself is leaving (leave_workspace). Refused with 409 for the last owner. Owners only, signed in as a person.

Their roles on the workspace’s repositories and their place in its teams go with them. Your own username is leaving, as leave_workspace. 409 for the last owner. Recorded as member.removed.

• Authentication: Required. Send an access token as Authorization: Bearer.
• MCP tool: workspace 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”.
username	string	Yes	The member’s username.

Example request

curl -X DELETE https://api.g1t.sh/workspaces/acme-labs/members/grace \
  -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.