Remove a collaborator

DELETE/repos/{owner}/{name}/collaborators/{username}

Anyone may remove their own. An outside collaborator then has no access; a member keeps the workspace’s base permission (change it with set_base_permission, or remove them from the workspace). Needs the Admin role, unless it is your own. People only.

Takes away a direct role. Anyone may remove their own, to leave a repository. 404 when the person has no role of their own on it. A member keeps the workspace’s base permission. Sends the repo.collaborator_removed webhook event. See Access and roles.

• Authentication: Required. Send an access token as Authorization: Bearer.
• MCP tool: remove_collaborator, with the same inputs

Path parameters

Name	Type	Required	Description
owner	string	Yes	The workspace that owns the repository.
name	string	Yes	The repository’s name.
username	string	Yes	The person’s username.

Example request

curl -X DELETE https://api.g1t.sh/repos/flagon-io/hello/collaborators/ada \
  -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.