Take over administration of a GitLab project
Moves administration of a project whose administering account can no longer act to the caller's own connected GitLab account (§9.4). The Control Plane re-verifies the caller's CURRENT Maintainer-or-Owner membership live, through the caller's own connection, then re-runs the §10.2 convergence under the new account. Eligible in any binding state — including a cleanup_pending one, whose interrupted removal can then finish under the new account (§19.4); that state is only reassigned, never re-provisioned. A project whose administering account is still connected and is not degraded is refused. Every refusal carries a machine-readable code.
Authorization
bearerAuth In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/orgs/string/gitlab/projects/string/transfer"{ "id": "string", "projectId": "string", "projectPath": "string", "defaultBranch": "string", "state": "provisioning", "stateReason": "string", "installerConnectionId": "string", "accounts": [ { "agentId": "string", "username": "string", "displayName": "string", "userId": "string", "state": "provisioning", "stateReason": "string" } ], "webhookState": "not_needed", "credentialEpoch": "string", "createdAt": "string"}