Gitea | Operate As Docs

Connect your client's Gitea with a key they paste, and call its API through Operate As.

Website: gitea.com
Connects by: Pasting a Access token
Category: Developer tools
Services: 1
Tools: 533

Service	Key	Base URL
Gitea	`gitea`	`https://gitea.com/api/v1`

Connecting

Your client makes a Access token in their Gitea settings and pastes it on their link. Operate As tries it with Gitea before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "gitea"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "gitea"    ]  }]

Permissions

What the client reads	Permission it asks for
Use the Gitea key you paste, with only the access you gave that key	Chosen on the provider's screen

Tools

Install Gitea's typed package for your language:

pip install operate-as-gitea

pip install operate-as-gitea

Run gitea.accept_repo_transfer

curl -X POST https://api.operate.as/v1/actions/gitea.accept_repo_transfer \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "owner": "<owner>",
      "repo": "<repo>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/gitea.accept_repo_transfer \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "owner": "<owner>",      "repo": "<repo>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/gitea.accept_repo_transfer

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://gitea.com/api/v1. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../gitea/user" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../gitea/user" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in Gitea. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}