AgentConnect
Gitea

Replace the Gitea bot token

Runs the connect checks against the new token, requires the same numeric bot user, then switches the sealed value atomically and advances the credential epoch so daemon caches purge the old value (§4.3). Bindings degraded by a rejected token are re-converged; the old token is revoked by a human in Gitea.

POST
/v1/orgs/{orgId}/gitea/connections/{id}/token

Authorization

bearerAuth
AuthorizationBearer <token>

In: header

Path Parameters

orgId*string
id*string

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/orgs/string/gitea/connections/string/token" \  -H "Content-Type: application/json" \  -d '{    "token": "string"  }'
{  "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"}