REST API endpoints for GitHub Apps

Use the REST API to interact with GitHub Apps

About GitHub Apps

If you are using your app with GitHub Actions and want to modify workflow files, you must authenticate on behalf of the user with an OAuth token that includes the workflow scope. The user must have admin or write permission to the repository that contains the workflow file. For more information, see Scopes for OAuth apps.

This page lists endpoints that you can access while authenticated as a GitHub App. For more information, see Authenticating as a GitHub App.

See REST API endpoints for GitHub App installations for a list of endpoints that require authentication as a GitHub App installation.

Note

Most endpoints use Authorization: Bearer <YOUR-TOKEN> and Accept: application/vnd.github+json headers, plus X-GitHub-Api-Version: 2026-03-10. Curl examples below omit these standard headers for brevity.

Get the authenticated app

GET /app

Returns the GitHub App associated with the authentication credentials used. To see how many app installations are associated with this GitHub App, see the installations_count in the response. For more details about your app's installations, see the "List installations for the authenticated app" endpoint.
You must use a JWT to access this endpoint.

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X GET \
  https://api.github.com/app

Response schema (Status: 200):

Create a GitHub App from a manifest

POST /app-manifests/{code}/conversions

Use this endpoint to complete the handshake necessary when implementing the GitHub App Manifest flow. When you create a GitHub App with the manifest flow, you receive a temporary code used to retrieve the GitHub App's id, pem (private key), and webhook_secret.

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X POST \
  https://api.github.com/app-manifests/CODE/conversions

Response schema (Status: 201):

List installation requests for the authenticated app

GET /app/installation-requests

Lists all the pending installation requests for the authenticated GitHub App.

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X GET \
  https://api.github.com/app/installation-requests

Response schema (Status: 200):

Array of Integration Installation Request:

List installations for the authenticated app

GET /app/installations

The permissions the installation has are included under the permissions key.
You must use a JWT to access this endpoint.

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X GET \
  https://api.github.com/app/installations

Response schema (Status: 200):

Array of Installation:

Get an installation for the authenticated app

GET /app/installations/{installation_id}

Enables an authenticated GitHub App to find an installation's information using the installation id.
You must use a JWT to access this endpoint.

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X GET \
  https://api.github.com/app/installations/1

Response schema (Status: 200):

Delete an installation for the authenticated app

DELETE /app/installations/{installation_id}

Uninstalls a GitHub App on a user, organization, or enterprise account. If you prefer to temporarily suspend an app's access to your account's resources, then we recommend the "Suspend an app installation" endpoint.
You must use a JWT to access this endpoint.

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X DELETE \
  https://api.github.com/app/installations/1

Response schema (Status: 202):

Create an installation access token for an app

POST /app/installations/{installation_id}/access_tokens

Creates an installation access token that enables a GitHub App to make authenticated API requests for the app's installation on an organization or individual account. Installation tokens expire one hour from the time you create them. Using an expired token produces a status code of 401 - Unauthorized, and requires creating a new installation token. By default the installation token has access to all repositories that the installation can access.
Note

Starting April 27, 2026, GitHub began a staged rollout of a stateless format (ghs_APPID_JWT) to all newly minted GitHub App installation tokens, making them more performant and improving the reliability of our API surface. If your application expects or relies on installation tokens being exactly 40 characters long, it may not handle this new token format correctly. You can now validate your apps and workflows using a temporary request header that lets you enable the token format on demand. For more information about the temporary header, see the GitHub blog.

Optionally, you can use the repositories or repository_ids body parameters to specify individual repositories that the installation access token can access. If you don't use repositories or repository_ids to grant access to specific repositories, the installation access token will have access to all repositories that the installation was granted access to. The installation access token cannot be granted access to repositories that the installation was not granted access to. Up to 500 repositories can be listed in this manner.
Optionally, use the permissions body parameter to specify the permissions that the installation access token should have. If permissions is not specified, the installation access token will have all of the permissions that were granted to the app. The installation access token cannot be granted permissions that the app was not granted.
You must use a JWT to access this endpoint.

Parameters

Headers

Path and query parameters

Body parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X POST \
  https://api.github.com/app/installations/1/access_tokens \
  -d '{
  "repositories": [
    "Hello-World"
  ],
  "permissions": {
    "issues": "write",
    "contents": "read"
  }
}'

Response schema (Status: 201):

Suspend an app installation

PUT /app/installations/{installation_id}/suspended

Suspends a GitHub App on a user, organization, or enterprise account, which blocks the app from accessing the account's resources. When a GitHub App is suspended, the app's access to the GitHub API or webhook events is blocked for that account.
You must use a JWT to access this endpoint.

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X PUT \
  https://api.github.com/app/installations/1/suspended

Response schema (Status: 204):

Unsuspend an app installation

DELETE /app/installations/{installation_id}/suspended

Removes a GitHub App installation suspension.
You must use a JWT to access this endpoint.

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X DELETE \
  https://api.github.com/app/installations/1/suspended

Response schema (Status: 204):

Create a scoped access token

POST /applications/{client_id}/token/scoped

Use a non-scoped user access token to create a repository-scoped and/or permission-scoped user access token. You can specify
which repositories the token can access and which permissions are granted to the
token.
Invalid tokens will return 404 NOT FOUND.

Note

This endpoint requires Basic authentication. Use the application's client_id as the username and the client_secret as the password. Do not send an Authorization: Bearer header with this request, because it replaces the Basic credentials.

Parameters

Headers

Path and query parameters

Body parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X POST \
  https://api.github.com/applications/Iv1.8a61f9b3a7aba766/token/scoped \
  -u "<YOUR_CLIENT_ID>:<YOUR_CLIENT_SECRET>" \
  -d '{
  "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a",
  "target": "octocat",
  "permissions": {
    "metadata": "read",
    "issues": "write",
    "contents": "read"
  }
}'

Response schema (Status: 200):

Get an app

GET /apps/{app_slug}

Note

The :app_slug is just the URL-friendly name of your GitHub App. You can find this on the settings page for your GitHub App (e.g., https://github.com/settings/apps/:app_slug).

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X GET \
  https://api.github.com/apps/APP_SLUG

Response schema (Status: 200):

Same response schema as Get the authenticated app.

Get an organization installation for the authenticated app

GET /orgs/{org}/installation

Enables an authenticated GitHub App to find the organization's installation information.
You must use a JWT to access this endpoint.

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X GET \
  https://api.github.com/orgs/ORG/installation

Response schema (Status: 200):

Same response schema as Get an installation for the authenticated app.

Get a repository installation for the authenticated app

GET /repos/{owner}/{repo}/installation

Enables an authenticated GitHub App to find the repository's installation information. The installation's account type will be either an organization or a user account, depending which account the repository belongs to.
You must use a JWT to access this endpoint.

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X GET \
  https://api.github.com/repos/OWNER/REPO/installation

Response schema (Status: 200):

Same response schema as Get an installation for the authenticated app.

Get a user installation for the authenticated app

GET /users/{username}/installation

Enables an authenticated GitHub App to find the user’s installation information.
You must use a JWT to access this endpoint.

Parameters

Headers

Path and query parameters

HTTP response status codes

Code examples

Example

Request:

curl -L \
  -X GET \
  https://api.github.com/users/USERNAME/installation

Response schema (Status: 200):

Same response schema as Get an installation for the authenticated app.