gitea-api

Automate Gitea REST API operations for repositories, issues, pull requests, and admin tasks.

4|2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill gitea-api-aidas-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitea-api
Source: https://github.com/Aidas-dev/k8s-agent-skills/tree/main/skills/gitea-api
Command: npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill gitea-api-aidas-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working with the Gitea REST API requires remembering endpoint paths, authentication methods, token scopes, and request formats. This Skill provides a complete reference for Gitea API v1.26 so you can automate repository, issue, PR, package, and admin operations with curl without consulting external docs. ## Core Features & Use Cases - Authentication Guidance: Covers token auth, Basic Auth, OAuth2 Bearer tokens, URL parameters, SSH signatures, and 2FA via the X-Gitea-OTP header. - Endpoint Reference: Documents key endpoints for users, repositories, issues, pull requests, organizations, packages, and admin operations like user and webhook management. - Ready-to-Use Examples: Provides curl commands for creating issues, listing filtered PRs, creating scoped API tokens, and deleting package versions. - Use Case: You need a CI pipeline to create a scoped API token, open an issue on a failed build, and clean up old package versions. This Skill gives you the exact endpoints, headers, and request bodies for each step. ## Quick Start Use the gitea-api skill to create a new issue in my repository and list all open pull requests using curl with token authentication.

Frequently Asked Questions about gitea-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate with the Gitea REST API?▼

Gitea API authentication supports token auth via the Authorization: token header, Basic Auth with username and password, OAuth2 Bearer tokens, and URL token parameters. Token auth in the header is the recommended method for scripts and automation.

How to create a Gitea API token with curl?▼

Create a Gitea API token by sending a POST request to /api/v1/users/{username}/tokens using Basic Auth with a JSON body containing the token name and scopes. Users with 2FA enabled must also include the X-Gitea-OTP header with their one-time code.

Does the Gitea API support fine-grained token scopes?▼

Yes, Gitea tokens support fine-grained scopes such as repo, write:repository, read:user, and read:organization, or the broad all scope. Scopes are specified as a JSON array when creating the token via the API or the web UI.

Why does deleting a Gitea package return 404?▼

A 404 on package deletion usually means the URL is missing one of the four required path segments: owner, package type, name, and version. Verify the full endpoint format /packages/{owner}/{type}/{name}/{version} before retrying.

Can I pass a Gitea token as a URL query parameter?▼

Yes, the ?token= query parameter works for simple scripts, but it is discouraged because tokens can appear in server logs and browser history. Use the Authorization header instead for any production or shared environment.