Pagure API

Name: Pagure API
Brand: Pagure API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsVersion ControlapiKey78 EndpointsREST

For Agents

Manage Pagure Git repositories, issues, pull requests, users, groups, webhooks, and project settings through a lightweight forge API.

Install Jentic One Beta

Connect the Pagure API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pagure 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Pagure API.

Create and configure Git projects with public/private visibility and namespace organization

Manage issues with custom fields, tags, milestones, assignees, and status transitions

Create, update, comment on, flag, and merge pull requests across forks and branches

GET STARTED

Start building with Pagure API

Explore with Jentic

View OpenAPI Document

Pagure is a lightweight Git-centered forge providing a REST API for managing Git repositories, issues, pull requests, tags, branches, users, groups, and projects. The API covers project creation and configuration, issue tracking with metadata and custom fields, pull request lifecycle (create, comment, merge, flag), release management via Git tags, user and group administration, webhook configuration, and repository settings including branch protection and notifications. Authentication uses API tokens obtained from Pagure user settings.

Use Cases

Patterns agents use Pagure API for, with concrete tasks.

★ Automated Issue Creation from External Systems

Integrate Pagure issue tracking with external monitoring, ticketing, or CI/CD systems by creating issues programmatically. POST /project/{namespace}/{repo}/new_issue accepts title, description, assignee, tags, milestone, and custom fields. This supports workflows like creating Pagure issues from GitHub Actions, incident response systems, or customer support platforms.

POST /{namespace}/{repo}/new_issue with title, issue_content, assignee, tags, milestone, and private flag.

Pull Request Review and Merge Workflow

Automate pull request workflows by querying open PRs, posting review comments, applying flags (CI status, linter results), and merging when criteria are met. GET /project/{namespace}/{repo}/pull-requests lists PRs, POST /project/{namespace}/{repo}/pull-request/{id}/comment adds review feedback, and POST /project/{namespace}/{repo}/pull-request/{id}/merge completes the merge. This supports code review bots and automated merge policies.

GET /{namespace}/{repo}/pull-requests?status=Open, then POST /{namespace}/{repo}/pull-request/{id}/merge when flags and reviews pass.

Repository Release Management

Manage Git tags and releases via the API by listing tags, creating new tags, and querying commits. GET /project/{namespace}/{repo}/git/tags returns all tags, and combined with commit endpoints, enables automated changelog generation, version bumping, and release note publishing. This supports CI/CD pipelines that tag releases based on semantic versioning rules.

GET /{namespace}/{repo}/git/tags to list versions, then use commit endpoints to generate changelog.

Project and User Activity Monitoring

Track project activity, user contributions, and repository statistics by querying users, projects, stars, forks, and watchers. GET /projects lists all projects with filters, GET /user/{username}/activity shows user contributions, and GET /project/{namespace}/{repo}/stargazers lists who starred a project. This supports analytics dashboards, contributor recognition, and community health metrics.

GET /user/{username}/activity?date={YYYY-MM-DD} for contributions, GET /projects?fork=false&short=true for project list.

AI Agent for Forge Operations

Let an AI agent manage Pagure forge tasks like creating issues from user reports, triaging PRs, tagging releases, adding collaborators to projects, and configuring webhooks. Through Jentic, the agent searches by intent (e.g., 'create a pagure issue'), loads the schema, and executes with the API token injected securely.

Use Jentic search 'create pagure issue' to find POST /{namespace}/{repo}/new_issue, load schema, execute with title and issue_content.

Key Endpoints

78 endpoints — pagure is a lightweight git-centered forge providing a rest api for managing git repositories, issues, pull requests, tags, branches, users, groups, and projects.

METHOD

PATH

DESCRIPTION

POST

/{namespace}/{repo}/new_issue

Create a new issue

GET

/{namespace}/{repo}/issues

List issues with filters

GET

/{namespace}/{repo}/pull-requests

List pull requests

POST

/{namespace}/{repo}/pull-request/{id}/merge

Merge a pull request

GET

/projects

List projects with filters

GET

/user/{username}/activity

Get user activity

POST

/{namespace}/{repo}/webhook/add

Add a webhook

POST

/{namespace}/{repo}/new_issue

Create a new issue

GET

/{namespace}/{repo}/issues

List issues with filters

GET

/{namespace}/{repo}/pull-requests

List pull requests

POST

/{namespace}/{repo}/pull-request/{id}/merge

Merge a pull request

GET

/projects

List projects with filters

Why Jentic?

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

Credential isolation

Pagure API tokens are stored encrypted in the Jentic vault and injected as the Authorization header at execution time. Raw tokens never appear in agent prompts, transcripts, or response payloads.

Intent-based discovery

Agents search by intent such as 'create a pagure issue' or 'merge a pagure pull request' and Jentic returns the matching endpoint with its schema and path parameters.

Time to first call

Direct Pagure integration: 1-2 days to model projects, issues, PRs, and webhooks. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

GitHub API

GitHub is a larger, feature-rich Git forge with extensive integrations, while Pagure is a lightweight, self-hostable alternative focused on simplicity.

Choose GitHub for ecosystem integrations and scale; choose Pagure for lightweight, self-hosted, open-source forge needs.

Alternative

GitLab API

GitLab provides a full DevOps platform with CI/CD built-in, while Pagure is a simpler Git forge focused on repositories, issues, and PRs.

Choose GitLab for integrated CI/CD and DevOps workflows; choose Pagure for lightweight forge needs without CI/CD complexity.

FAQs

Specific to using Pagure API through Jentic.

What authentication does the Pagure API use?

The Pagure API uses API key authentication via the Authorization header with format 'token <your-api-token>'. Tokens are obtained from Pagure user settings. Through Jentic, tokens are stored encrypted and injected at execution time.

Can I manage pull requests programmatically with the Pagure API?

Yes. The API supports listing PRs, creating PRs from branches, commenting, applying flags (CI status), and merging. This enables automated code review and merge workflows.

Does the Pagure API support issue tracking?

Yes. The API provides full CRUD for issues including custom fields, tags, milestones, assignees, status updates, and comments. This supports integration with external ticketing and monitoring systems.

How do I configure webhooks through the Pagure API?

Use POST /{namespace}/{repo}/webhook/add with the target URL and event types (push, pull request, issue). Webhooks enable real-time integration with CI/CD, chat, and notification systems.

Is the Pagure API free?

Pagure is open-source software (GPL-2.0) and the public instance at pagure.io is free to use for open-source projects. Self-hosted Pagure instances can be deployed with the same API surface.

Can I list all projects on a Pagure instance?

Yes. GET /projects returns a list of projects with optional filters for forks, short format, username, namespace, tags, and pattern matching. Pagination is supported via page and per_page parameters.