Gitea
Disconnect Gitea
Walks every managed repository’s removal path first (§6): each managed webhook is deleted by its recorded id and its claim released. A binding whose cleanup cannot complete — a rejected token, or a bot that lost admin — parks in cleanup_pending and keeps the connection row until a replacement token or a manual webhook removal clears it; only then is the row and its sealed token removed.
Authorization
bearerAuth AuthorizationBearer <token>
In: header
Path Parameters
orgId*string
id*string
Response Body
application/json
application/json
application/json
curl -X DELETE "https://example.com/v1/orgs/string/gitea/connections/string"{ "removed": true, "pendingRepositories": -9007199254740991, "connection": { "id": "string", "botUserId": "string", "botUsername": "string", "botDisplayName": "string", "state": "connected", "connectedBy": "string", "credentialEpoch": "string", "boundRepositories": -9007199254740991, "instanceUrl": "string", "instanceVersion": "string", "instanceVersionSupported": true, "instanceProduct": "gitea", "instanceVersionFloor": "string", "requiredScopes": [ "string" ], "lastVerifiedAt": "string", "createdAt": "string" }}