Gogs API

Name: Gogs API
Brand: Gogs API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbasic, apiKey104 EndpointsREST

For Agents

Manage self-hosted Git repositories on Gogs: create issues, push releases, configure webhooks, and manage collaborators. Mirrors GitHub-style endpoints for easy adoption.

Connect the Gogs API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gogs API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Gogs API.

Search repositories or list user, organisation, and team repositories

Create, read, and migrate repositories including their branches and contents

Open, list, and comment on issues against a repository

Manage releases, tags, and webhooks for a repository

GET STARTED

Start building with Gogs API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Gogs API, keeping it validated and agent-ready. Gogs is a self-hosted, lightweight Git service written in Go that follows the GitHub REST API v3 conventions. Its API exposes repositories, branches, commits, contents, issues, releases, webhooks, collaborators, deploy keys, organisations, users, miscellaneous helpers, and administration endpoints. It is the standard interface for self-hosting teams that want a familiar GitHub-style integration surface without depending on a third-party SaaS.

Use Cases

Patterns agents use Gogs API for, with concrete tasks.

★ Self-Hosted Issue Tracking Automation

Engineering teams that run Gogs internally automate issue triage by calling /repos/{owner}/{repo}/issues to read open issues and POST to the same path to create new ones. This pattern mirrors the GitHub Issues API, so existing scripts and bots port over with minimal changes.

Open an issue on repo 'platform/infra' titled 'Investigate intermittent CI timeout' with the agent's debug log attached as a comment.

Repository Migration

When teams move from GitHub or another Git host to Gogs, /repos/migrate accepts a clone URL and credentials and pulls the full repository — including history — into Gogs. Pair it with /repos/{owner}/{repo}/hooks to recreate webhooks on the new host.

Migrate the repository at https://github.com/example/widgets into the Gogs organisation 'platform' and recreate the GitHub webhooks.

Release Automation

CI integrations create releases on Gogs by calling /repos/{owner}/{repo}/releases when a tag pipeline completes. Combined with /repos/{owner}/{repo}/branches and /repos/{owner}/{repo}/commits/{sha}, the integration can record the exact commit and branch each release was cut from.

Create a release v1.4.0 on repo 'platform/widgets' with notes assembled from the commits since the last release.

AI Agent Source Control

An AI coding agent uses Jentic to interact with a Gogs server: it lists repositories, opens issues for newly detected bugs, and writes back fix commits via the contents endpoints. Basic auth credentials and personal access tokens stay in the Jentic vault.

Search Jentic for 'create gogs issue', load the schema, and open a 'flaky test' issue on every repo where the nightly CI failed.

Key Endpoints

104 endpoints — jentic publishes the only available openapi specification for gogs api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/repos/search

Search repositories

GET

/repos/{owner}/{repo}

Get a repository

POST

/repos/migrate

Migrate an external repository into Gogs

GET

/repos/{owner}/{repo}/issues

List issues on a repository

POST

/repos/{owner}/{repo}/issues

Create an issue on a repository

GET

/repos/{owner}/{repo}/branches

List branches

GET

/repos/{owner}/{repo}/releases

List releases

GET

/repos/{owner}/{repo}/hooks

List webhooks for a repository

GET

/repos/search

Search repositories

GET

/repos/{owner}/{repo}

Get a repository

POST

/repos/migrate

Migrate an external repository into Gogs

GET

/repos/{owner}/{repo}/issues

List issues on a repository

POST

/repos/{owner}/{repo}/issues

Create an issue on a repository

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Gogs basic-auth credentials and personal access tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'create gogs issue') and Jentic returns matching Gogs operations with their input schemas, so the agent can call the right endpoint across 104 paths without browsing source-tree Markdown.

Time to first call

Direct Gogs integration: 1-2 days for auth, pagination, and per-server URL handling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Gogs API through Jentic.

Why is there no official OpenAPI spec for Gogs API?

Gogs documents its endpoints in source-tree Markdown files but does not ship a maintained OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call Gogs API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Gogs API use?

Gogs supports two schemes: HTTP basic authentication with username and password, and personal access tokens passed via the Authorization header. Through Jentic, both are stored encrypted in the vault and injected at execution time so the agent never sees the raw secret.

Can I create an issue with the Gogs API?

Yes. POST /repos/{owner}/{repo}/issues opens a new issue and POST /repos/{owner}/{repo}/issues/{index}/comments adds a comment. The shape mirrors the GitHub Issues API so existing tooling ports across with little change.

What are the rate limits for the Gogs API?

Gogs is self-hosted and the OpenAPI spec does not declare a numeric rate limit. The practical limit depends on the deployed server's capacity; back off on HTTP 429 responses if your administrator has fronted the server with a rate-limiting proxy.

How do I migrate a repository to Gogs through Jentic?

Run a Jentic search for 'migrate repo to gogs', load the schema for POST /repos/migrate, and execute it with the source clone URL and target organisation. Install with pip install jentic and chain search, load, and execute.

Does the Gogs API support webhooks?

Yes. /repos/{owner}/{repo}/hooks lists configured webhooks and POST to the same path adds a new one. /repos/{owner}/{repo}/hooks/{id} updates or removes a specific webhook so CI integrations can keep their delivery URLs current.

Gogs API

Connect the Gogs API to your agent

Capabilities

Start building with Gogs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs