GitHub v3 REST API (GHEC)

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.

Can I limit what my agent is allowed to do with the GitHub GHEC API?

Yes. Because you run Jentic One self-hosted, your own rules decide which GitHub operations and credentials the agent may use, and GHEC puts the owner and repo in the URL path (/repos/{owner}/{repo}/...), so a rule can pin the agent to a single repository where it opens pull requests and issues and nothing else. You choose the exact operations it may call, so destructive ones like merging a pull request (PUT /repos/{owner}/{repo}/pulls/{pull_number}/merge) or dispatching a workflow (POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches) are excluded unless you add them. The stored token is injected only at execution time for the operations you allowed, so the agent cannot reach enterprise audit or billing endpoints it was never granted.