Transfer a workspace's ownership

Hand a workspace to another of its members: they become an owner and you a member, in one step.

POST/workspaces/{workspace}/transfer_ownership

A workspace can have several owners; to add one without stepping down, use update_member with role owner. Owners only, signed in as a person.

username becomes an owner and you a member, in one step. Recorded as workspace.ownership_transferred.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: workspace with action transfer_ownership, 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”.

Body parameters

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name	Type	Required	Description
`username`	string	Yes	The member’s username.

Example request

curl -X POST https://api.g1t.sh/workspaces/acme-labs/transfer_ownership \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "username": "grace"
  }'

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.