Transfer a repository

Move a repository to another workspace, keeping its name.

POST/repos/{owner}/{name}/transfer

You must own both workspaces, and the destination must not already have a repository of that name; a free destination takes a private repository only if its private storage has room. Everything moves with it: git data, issues, pull requests, comments, labels, workflow runs, deployments, its project, and its own secrets, variables and webhooks. Its old address keeps working: web pages, git remotes and API calls redirect to the new one until a repository is made at the old address. Usage from now on is charged to the new workspace.

The repository at its new address. Refused with 409 when the destination already has a repository of that name, 403 unless you own both workspaces, and 402 when a free destination has no room for a private repository. The old address redirects. See Transferring a repository.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: transfer_repo, 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.

Body parameters

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

Name	Type	Required	Description
`to`	string	Yes	The slug of the workspace to move it to, e.g. “flagon-io”. You must own it.

Example request

curl -X POST https://api.g1t.sh/repos/flagon-io/hello/transfer \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "flagon-io"
  }'

Example response

A successful request answers 200 with:

{
  "id": "rep_01m3m5q6p0e2qaw6mmjahk0qrr",
  "namespace": "flagon-io",
  "name": "hello",
  "description": "A tiny service that says hello.",
  "is_private": false,
  "owner_id": "usr_01kkntcg1eeb98j62xjm7eh09p",
  "default_branch": "main",
  "fork_of": null,
  "protected": true,
  "created_at": "2026-09-28T14:11:52.640Z",
  "website": "https://hello.g1t.page",
  "archived_at": null
}

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.
402	`payment_required`	The workspace cannot start this work: it needs the g1t plan or a card check, or it is at a limit. See usage and billing.
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.