Automate Gitea .

What Gitea . is

This documentation describes the Gitea API.

Things people automate with Gitea .

• Post new Gitea . issues and pull requests to SlackGitea . → Slack
• Post new Gitea . issues and pull requests to TelegramGitea . → Telegram
• Post new Gitea . issues and pull requests to Google ChatGitea . → Google Chat
• Create an Asana task for every new Gitea . issueGitea . → Asana
• Create a Jira task for every new Gitea . issueGitea . → Jira
• Create a Google Tasks task for every new Gitea . issueGitea . → Google Tasks

What HumDay can do in Gitea .

156 documented operations change something in Gitea .. The 44 most useful are listed here.

• POSTAdd email addresses/user/emails
• DELETEDelete email addresses/user/emails
• POSTcreates a new OAuth2 application/user/applications/oauth2
• POSTCreate an access token/users/{username}/tokens
• POSTCreate a public key/user/keys
• POSTCreate a repository/user/repos
• POSTCreate a GPG key/user/gpg_keys
• POSTCreate an issue. If using deadline only the date will be taken into account, and time of day ignored./repos/{owner}/{repo}/issues
• POSTCreate an organization/orgs
• DELETEDelete a comment/repos/{owner}/{repo}/issues/comments/{id}
• PATCHEdit a comment/repos/{owner}/{repo}/issues/comments/{id}
• POSTRender a markdown document as HTML/markdown
• POSTAdd a comment to an issue/repos/{owner}/{repo}/issues/{index}/comments
• PUTMark notification threads as read, pinned or unread/notifications
• POSTCreate a wiki page/repos/{owner}/{repo}/wiki/new
• POSTCreate a comment attachment/repos/{owner}/{repo}/issues/comments/{id}/assets
• PATCHUpdate user settings/user/settings
• DELETERemove a reaction from a comment of an issue/repos/{owner}/{repo}/issues/comments/{id}/reactions
• POSTAdd a reaction to a comment of an issue/repos/{owner}/{repo}/issues/comments/{id}/reactions
• POSTVerify a GPG key/user/gpg_key_verify
• POSTSend to the inbox/activitypub/user/{username}/inbox
• POSTCreate a new git tag in a repository/repos/{owner}/{repo}/tags
• POSTCreate a label/repos/{owner}/{repo}/labels
• POSTCreate a milestone/repos/{owner}/{repo}/milestones
• DELETEdelete an access token/users/{username}/tokens/{token}
• POSTAdd tracked time to a issue/repos/{owner}/{repo}/issues/{index}/times
• POSTCreate an issue attachment/repos/{owner}/{repo}/issues/{index}/assets
• POSTAdd a label to an issue/repos/{owner}/{repo}/issues/{index}/labels
• DELETEDelete a public key/user/keys/{id}
• POSTAdd a reaction to an issue/repos/{owner}/{repo}/issues/{index}/reactions
• POSTCreate a hook/orgs/{org}/hooks
• POSTCreate a repository in an organization/orgs/{org}/repos
• POSTCreate a team/orgs/{org}/teams
• POSTCreate a label for an organization/orgs/{org}/labels
• DELETERemove a GPG key/user/gpg_keys/{id}
• DELETEUnfollow a user/user/following/{username}
• PUTFollow a user/user/following/{username}
• PATCHMark notification thread as read by ID/notifications/threads/{id}
• DELETEDelete a comment attachment/repos/{owner}/{repo}/issues/comments/{id}/assets/{attachment_id}
• PATCHEdit a comment attachment/repos/{owner}/{repo}/issues/comments/{id}/assets/{attachment_id}
• POSTRender raw markdown as HTML/markdown/raw
• POSTMigrate a remote git repository/repos/migrate
• DELETEDelete an issue/repos/{owner}/{repo}/issues/{index}
• PATCHEdit an issue. If using deadline only the date will be taken into account, and time of day ignored./repos/{owner}/{repo}/issues/{index}

What HumDay can read from Gitea .

These are the operations a schedule or a trigger can watch.

• GETList the authenticated user's email addresses/user/emails
• GETSearch for issues across the repositories that the user has access to/repos/issues/search
• GETList users's notification threads/notifications
• GETSearch for users/users/search
• GETList the users that the authenticated user is following/user/following
• GETList the given user's public keys/users/{username}/keys
• GETList a user's organizations/users/{username}/orgs
• GETList the repos owned by the given user/users/{username}/repos
• GETList the authenticated user's access tokens/users/{username}/tokens
• GETList the given user's GPG keys/users/{username}/gpg_keys
• GETList the given user's followers/users/{username}/followers
• GETList the users that the given user is following/users/{username}/following
• GETList the repositories watched by a user/users/{username}/subscriptions
• GETList all comments in a repository/repos/{owner}/{repo}/issues/comments
• GETList the authenticated user's public keys/user/keys
• GETList the current user's organizations/user/orgs
• GETList the repos that the authenticated user owns/user/repos
• GETList all the teams a user belongs to/user/teams
• GETList the current user's tracked times/user/times
• GETList the authenticated user's GPG keys/user/gpg_keys
• GETList the authenticated user's followers/user/followers
• GETGet list of all existing stopwatches/user/stopwatches
• GETCheck if unread notifications exist/notifications/new
• GETList repositories watched by the authenticated user/user/subscriptions
• GETGet a user/users/{username}
• GETList a repository's issues/repos/{owner}/{repo}/issues
• GETGet list of organizations/orgs
• GETList users's notification threads on a specific repo/repos/{owner}/{repo}/notifications
• GETGet the authenticated user/user
• GETList the authenticated user's oauth2 applications/user/applications/oauth2
• GETGet a comment/repos/{owner}/{repo}/issues/comments/{id}
• GETList all comments on an issue/repos/{owner}/{repo}/issues/{index}/comments
• GETList all comments and events on an issue/repos/{owner}/{repo}/issues/{index}/timeline
• GETGet a user's heatmap/users/{username}/heatmap
• GETThe repos that the given user has starred/users/{username}/starred
• GETSearch for repositories/repos/search
• GETThe repos that the authenticated user has starred/user/starred
• GETList comment's attachments/repos/{owner}/{repo}/issues/comments/{id}/assets
• GETsearch topics via keyword/topics/search
• GETGet user settings/user/settings
• GETGet a list of reactions from a comment of an issue/repos/{owner}/{repo}/issues/comments/{id}/reactions
• GETGet a Token to verify/user/gpg_key_token
• GETReturn all users that have write access and can be assigned to issues/repos/{owner}/{repo}/assignees
• GETCheck if the current user is watching a repo/repos/{owner}/{repo}/subscription
• GETCheck if one user is following another user/users/{username}/following/{target}
• GETList an issue's tracked times/repos/{owner}/{repo}/issues/{index}/times
• GETList issue's attachments/repos/{owner}/{repo}/issues/{index}/assets
• GETReturns the version of the Gitea application/version
• GETReturns the nodeinfo of the Gitea application/nodeinfo
• GETGet a public key/user/keys/{id}
• GETGet a list reactions of an issue/repos/{owner}/{repo}/issues/{index}/reactions
• GETList an organization's webhooks/orgs/{org}/hooks
• GETList an organization's repos/orgs/{org}/repos
• GETList an organization's teams/orgs/{org}/teams
• GETList a team's repos/teams/{id}/repos
• GETList an organization's labels/orgs/{org}/labels

How automating Gitea . works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Gitea . account.
4. Grant access, then go live. You approve the specific Gitea . operations it may use — and only those.

Popular Gitea . integrations

Connect Gitea . to the tools people pair it with most.

• Gitea . and OData for namespace microsoft.graphintegration
• Gitea . and Cloudflareintegration
• Gitea . and NetBoxintegration
• Gitea . and GitHubintegration
• Gitea . and Mistintegration
• Gitea . and Loket.nlintegration
• Gitea . and Atlassian The Jira Cloud platformintegration
• Gitea . and Magento B2Bintegration
• Gitea . and Stripeintegration
• Gitea . and Zuora Reference Billingintegration
• Gitea . and bunqintegration
• Gitea . and DocuSignintegration

Automate Gitea . with these

• OData for namespace microsoft.graph11412 operations
• GitHub811 operations
• Atlassian The Jira Cloud platform474 operations
• Gitlab358 operations
• JIRA 7.6.1324 operations
• Appcenter App Center Client323 operations
• Bitbucket292 operations
• Keycloak Admin281 operations
• Apple App Store Connect251 operations
• Files.com222 operations
• Vmware vRealize Network Insight Reference161 operations
• Visualstudio VSOnline152 operations

Categories

• Developer tools

Questions about Gitea . automation

Can HumDay connect to Gitea .?

Yes. HumDay reads Gitea .'s own published API description and derives the operations from it, so there is no hand-built connector to wait for. 321 operations are documented.

Do I need to write code to automate Gitea .?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Gitea . account.

What can HumDay do in Gitea .?

156 of the 321 documented operations change something in Gitea ., and 165 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Gitea . account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Gitea . is held behind that approval.

Where this came from

The operations above are read from a published API description for Gitea . at try.gitea.io/swagger.v1.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.