AgentConnect
Gitea

Bind a Gitea repository ahead of use

Optional: a repository is bound on first use when a trigger, an agent workspace or an additional-repository grant names it (§6), and this route binds one ahead of that. It re-fetches the repository by numeric id through the organization’s connection, requires the bot to hold admin on it (§4.4), acquires the deployment-global repository claim, creates the binding and runs the §6 saga: the managed webhook is installed when an enabled trigger wants ingress, tested, and the binding is ready — with the webhook_unverified warning when the relay never observed the test delivery. A repository that is already bound answers 409.

POST
/v1/orgs/{orgId}/gitea/repositories

Authorization

bearerAuth
AuthorizationBearer <token>

In: header

Path Parameters

orgId*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

application/json

curl -X POST "https://example.com/v1/orgs/string/gitea/repositories" \  -H "Content-Type: application/json" \  -d '{    "repoId": "string"  }'
{  "id": "string",  "connectionId": "string",  "repoId": "string",  "repoPath": "string",  "cloneUrl": "string",  "defaultBranch": "string",  "state": "provisioning",  "stateReason": "string",  "webhookState": "not_needed",  "lastVerifiedDeliveryAt": "string",  "createdAt": "string"}