GitHub v3 REST API (GHEC)
Browse all Github APIs✓ Official Vendor SpecDeveloper ToolsSource Controlbearer1176 EndpointsREST
For Agents
Manage repositories, issues, pull requests, Actions runs, security alerts, and enterprise admin tasks across GitHub Enterprise Cloud organisations.
Use for: Open a pull request from a feature branch into main, List all open issues assigned to me across the org, Trigger a GitHub Actions workflow run on the default branch, Find all repositories with open code-scanning alerts of severity high
Not supported: Does not handle GitHub Server (self-hosted appliance) admin endpoints, the GraphQL v4 API, or chat-style Copilot APIs — use for GitHub Enterprise Cloud REST operations only.
The GitHub v3 REST API for GitHub Enterprise Cloud (GHEC) exposes the full developer-platform surface — repositories, issues, pull requests, Actions workflows, code scanning, Dependabot, billing, and enterprise-level admin operations. Agents can manage source control, drive CI/CD, audit security alerts, and administer organisations and enterprise accounts. Authentication is a Bearer token (personal access token, GitHub App installation token, or fine-grained token) and the spec covers more than 1,000 endpoints across 70+ tag groups.
Install Jentic One Beta
Connect the GitHub v3 REST API (GHEC) to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GitHub v3 REST API (GHEC), 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.
1
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 | sh2
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 instanceJentic 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 GitHub v3 REST API (GHEC) API.
Open, comment on, and close issues and pull requests across repositories
Trigger and inspect GitHub Actions workflow runs and read job logs
List and resolve code-scanning, secret-scanning, and Dependabot alerts
Administer organisations, teams, and seats across a GHEC enterprise
Pull audit logs and SAML SSO state for compliance reporting
Manage repository contents — create commits, branches, releases, and tags
Read billing and usage data for Actions, Packages, and shared storage
Use Cases
Patterns agents use GitHub v3 REST API (GHEC) API for, with concrete tasks.
★ Pull Request Automation
Automate pull request workflows — opening, requesting reviewers, applying labels, and merging when checks pass. POST /repos/{owner}/{repo}/pulls creates the PR; POST /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers adds reviewers; PUT /repos/{owner}/{repo}/pulls/{pull_number}/merge completes the merge once required checks succeed.
Open a pull request from feature/x into main with title 'Refactor auth' and request review from team @platform
Security Alert Triage
Triage code-scanning, secret-scanning, and Dependabot alerts across an enterprise. List alerts via GET /enterprises/{enterprise}/code-scanning/alerts and GET /enterprises/{enterprise}/secret-scanning/alerts, then dismiss or resolve each via the per-alert PATCH endpoints with a reason and comment for audit.
List all open code-scanning alerts at severity=high across the enterprise and return repository, rule_id, and html_url for each
CI/CD Workflow Orchestration
Drive GitHub Actions from outside the platform — dispatch a workflow on demand, poll its run status, and pull job logs for failure analysis. POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches starts a run; GET /repos/{owner}/{repo}/actions/runs/{run_id} reports its conclusion.
Dispatch the workflow deploy.yml on branch main with input env=staging, then poll runs until conclusion is success or failure
Enterprise Audit and Compliance
Pull audit logs and SSO state for SOC 2 and ISO 27001 evidence. GET /enterprises/{enterprise}/audit-log paginates events across organisations, and GET /enterprises/{enterprise}/consumed-licenses produces the seat-level inventory that compliance reviewers expect, fully driven from API calls.
Paginate the enterprise audit log over the last 24 hours and return action, actor, and created_at for every event of type repo.access
AI Agent Code Operations
Use Jentic to let an AI agent execute concrete code-platform actions. The agent issues an intent like 'open a pull request', Jentic resolves the matching GitHub operation, executes it with the Bearer token held in the vault, and returns the new PR URL the agent can post back to chat.
Through Jentic, create a pull request from branch fix/typo into main with title 'Fix typo in README' and return the html_url
Key Endpoints
1176 endpoints — the github v3 rest api for github enterprise cloud (ghec) exposes the full developer-platform surface — repositories, issues, pull requests, actions workflows, code scanning, dependabot, billing, and enterprise-level admin operations.
METHOD
PATH
DESCRIPTION
POST
/repos/{owner}/{repo}/pulls
Create a pull request
POST
/repos/{owner}/{repo}/issues
Open an issue
POST
/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches
Dispatch a workflow run
GET
/enterprises/{enterprise}/audit-log
Get the enterprise audit log
GET
/repos/{owner}/{repo}/code-scanning/alerts
List code-scanning alerts
GET
/repos/{owner}/{repo}/dependabot/alerts
List Dependabot alerts
PUT
/repos/{owner}/{repo}/pulls/{pull_number}/merge
Merge a pull request
GET
/search/code
Search code across repositories
POST
/repos/{owner}/{repo}/pulls
Create a pull request
POST
/repos/{owner}/{repo}/issues
Open an issue
POST
/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches
Dispatch a workflow run
GET
/enterprises/{enterprise}/audit-log
Get the enterprise audit log
GET
/repos/{owner}/{repo}/code-scanning/alerts
List code-scanning alerts
GET
/repos/{owner}/{repo}/dependabot/alerts
List Dependabot alerts
PUT
/repos/{owner}/{repo}/pulls/{pull_number}/merge
Merge a pull request
GET
/search/code
Search code across repositories
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
GHEC Bearer tokens (PATs, fine-grained, or App installation tokens) are stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution token — the raw token never enters the prompt or transcript, and rotations are centralised.
Intent-based discovery
Agents search by intent (e.g. 'create a pull request') and Jentic returns the matching GitHub operation with its request body schema, so the agent picks the right one of more than 1,000 endpoints without browsing the docs.
Time to first call
Direct GHEC integration: 1-2 weeks to wire up token rotation, pagination, rate-limit backoff, and webhook handling. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using GitHub v3 REST API (GHEC) API through Jentic.
What authentication does the GitHub GHEC API use?
GHEC accepts Bearer tokens — personal access tokens, fine-grained tokens, or GitHub App installation tokens — passed as Authorization: Bearer <token>. Through Jentic the token is held in the encrypted MAXsystem vault, so the agent gets a scoped execution token and the raw secret never enters the prompt context.
Can I open a pull request with the GitHub GHEC API?
Yes. POST /repos/{owner}/{repo}/pulls creates a pull request from head into base with a title and body, then POST /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers adds reviewers and PUT /repos/{owner}/{repo}/pulls/{pull_number}/merge completes the merge once checks pass.
What are the rate limits for the GitHub GHEC API?
Authenticated REST requests are capped at 5,000 per hour per user, 15,000 per hour for GitHub Apps installed on enterprise organisations, and the search endpoints have a separate 30-per-minute cap. Exceeding the cap returns HTTP 403 with X-RateLimit-Reset; back off until the window resets.
How do I trigger a GitHub Actions workflow through Jentic?
Search Jentic for 'trigger a github actions workflow', load POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches, and execute with ref set to the branch and inputs to the workflow input map. Poll GET /repos/{owner}/{repo}/actions/runs to read the resulting run conclusion.
Does the GHEC API expose enterprise-level audit and billing?
Yes. GET /enterprises/{enterprise}/audit-log paginates every audit event across the enterprise's organisations, and the /enterprises/{enterprise}/settings/billing/* endpoints expose Actions, Packages, and storage usage. Both require a token granted enterprise admin scope.
Can I read code-scanning and Dependabot alerts via the API?
Yes. GET /repos/{owner}/{repo}/code-scanning/alerts lists CodeQL findings and GET /repos/{owner}/{repo}/dependabot/alerts lists vulnerable-dependency findings. Filter by state=open and severity=high to drive a triage queue, and PATCH the per-alert endpoint to dismiss with a documented reason.
How is the GHEC API different from github.com REST API?
GHEC ships extra endpoints under /enterprises/{enterprise} for SAML SSO, consumed licences, and enterprise audit log streaming, plus stricter authentication options like SAML-bound tokens. The core resource endpoints (repos, issues, pulls, actions) are identical and share the api.github.com host.
GET STARTED