This article describes how to quickly get started with the GitHub REST API using GitHub CLI, JavaScript, or curl
. For a more detailed guide, see "Getting started with the REST API."
GitHub CLI is the easiest way to use the GitHub REST API from the command line.
Note: The following example is intended for GitHub.com. If you'd prefer to try the example using GitHub Enterprise Server, you must replace octocat/Spoon-Knife
with a repository on your instance. Alternatively, rerun the gh auth login
command to authenticate to GitHub.com instead of your instance.
-
Install GitHub CLI if you haven't installed it yet. For installation instructions, see the GitHub CLI repository.
-
Use the auth login
subcommand to authenticate to GitHub CLI. For more information, see the GitHub CLI auth login
documentation.
gh auth login
-
Use the api
subcommand to make your API request. For more information, see the GitHub CLI api
documentation.
gh api repos/octocat/Spoon-Knife/issues
You can also use GitHub CLI in your GitHub Actions workflows. For more information, see "Using GitHub CLI in workflows."
Instead of using the gh auth login
command, pass an access token as an environment variable called GH_TOKEN
. GitHub recommends that you use the built-in GITHUB_TOKEN
instead of creating a token. If this is not possible, store your token as a secret and replace GITHUB_TOKEN
in the example below with the name of your secret. For more information about GITHUB_TOKEN
, see "Automatic token authentication." For more information about secrets, see "Encrypted secrets."
Note: The following example workflows are intended for GitHub.com. If you'd prefer to try the examples using GitHub Enterprise Server, you must replace octocat/Spoon-Knife
with a repository on GitHub Enterprise Server.
on:
workflow_dispatch:
jobs:
use_api:
runs-on: ubuntu-latest
permissions:
issues: read
steps:
- env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
gh api repos/octocat/Spoon-Knife/issues
If you are authenticating with a GitHub App, you can create an installation access token within your workflow:
-
Store your GitHub App's ID as a secret. In the following example, replace APP_ID
with the name of the secret. You can find your app ID on the settings page for your app or through the API. For more information, see "GitHub Apps" in the REST API documentation. For more information about secrets, see "Encrypted secrets."
-
Generate a private key for your app. Store the contents of the resulting file as a secret. (Store the entire contents of the file, including -----BEGIN RSA PRIVATE KEY-----
and -----END RSA PRIVATE KEY-----
.) In the following example, replace APP_PEM
with the name of the secret. For more information, see "Managing private keys for GitHub Apps."
-
Add a step to generate a token, and use that token instead of GITHUB_TOKEN
. Note that this token will expire after 60 minutes. For example:
on:
workflow_dispatch:
jobs:
track_pr:
runs-on: ubuntu-latest
steps:
- name: Generate token
id: generate_token
uses: tibdex/github-app-token@c2055a00597a80f713b78b1650e8d3418f4d9a65
with:
app_id: ${{ secrets.APP_ID }}
private_key: ${{ secrets.APP_PEM }}
- name: Use API
env:
GH_TOKEN: ${{ steps.generate_token.outputs.token }}
run: |
gh api repos/octocat/Spoon-Knife/issues
You can use Octokit.js to interact with the GitHub REST API in your JavaScript scripts. For more information, see "Scripting with the REST API and JavaScript."
Note: The following example is intended for GitHub.com. If you'd prefer to try the example using GitHub Enterprise Server, you must replace octocat/Spoon-Knife
with a repository on your instance. Alternatively, you can create a new Octokit
instance without specifying baseURL
.
-
Create an access token. For example, create a personal access token or a GitHub App user access token. For more information, see "Creating a personal access token" or "Identifying and authorizing users for GitHub Apps."
Warning: Treat your access token like a password.
To keep your token secure, you can store your token as a secret and run your script through GitHub Actions. For more information, see the "Using Octokit.js in GitHub Actions" section.
If these options are not possible, consider using another service such as the 1Password CLI to store your token securely.
-
Install octokit
. For example, npm install octokit
. For other ways to install or load octokit
, see the Octokit.js README.
-
Import octokit
in your script. For example, import { Octokit } from "octokit";
. For other ways to import octokit
, see the Octokit.js README.
-
Create an instance of Octokit
with your token. Replace YOUR-TOKEN
with your token.
const octokit = new Octokit({
auth: 'YOUR-TOKEN'
});
-
Use octokit.request
to execute your request. Send the HTTP method and path as the first argument. Specify any path, query, and body parameters in an object as the second argument. For example, in the following request the HTTP method is GET
, the path is /repos/{owner}/{repo}/issues
, and the parameters are owner: "octocat"
and repo: "Spoon-Knife"
.
await octokit.request("GET /repos/{owner}/{repo}/issues", {
owner: "octocat",
repo: "Spoon-Knife",
});
You can also execute your JavaScript scripts in your GitHub Actions workflows. For more information, see "Workflow syntax for GitHub Actions."
GitHub recommends that you use the built-in GITHUB_TOKEN
instead of creating a token. If this is not possible, store your token as a secret and replace GITHUB_TOKEN
in the example below with the name of your secret. For more information about GITHUB_TOKEN
, see "Automatic token authentication." For more information about secrets, see "Encrypted secrets."
Note: The following example is intended for GitHub.com. If you'd prefer to try the example using GitHub Enterprise Server, you must replace octocat/Spoon-Knife
with a repository on your instance. Alternatively, you can create a new Octokit
instance without specifying baseURL
.
The following example workflow:
- Checks out the repository content
- Sets up Node.js
- Installs
octokit
- Stores the value of
GITHUB_TOKEN
as an environment variable called TOKEN
and runs .github/actions-scripts/use-the-api.mjs
, which can access that environment variable as process.env.TOKEN
Example workflow:
on:
workflow_dispatch:
jobs:
use_api_via_script:
runs-on: ubuntu-latest
permissions:
issues: read
steps:
- name: Check out repo content
uses: actions/checkout@v2
- name: Setup Node
uses: actions/setup-node@v2
with:
node-version: '16.17.0'
cache: npm
- name: Install dependencies
run: npm install octokit
- name: Run script
run: |
node .github/actions-scripts/use-the-api.mjs
env:
TOKEN: ${{ secrets.GITHUB_TOKEN }}
Example JavaScript script, with the file path .github/actions-scripts/use-the-api.mjs
:
import { Octokit } from "octokit"
const octokit = new Octokit({
auth: process.env.TOKEN
});
try {
const result = await octokit.request("GET /repos/{owner}/{repo}/issues", {
owner: "octocat",
repo: "Spoon-Knife",
});
const titleAndAuthor = result.data.map(issue => {title: issue.title, authorID: issue.user.id})
console.log(titleAndAuthor)
} catch (error) {
console.log(`Error! Status: ${error.status}. Message: ${error.response.data.message}`)
}
If you are authenticating with a GitHub App, you can create an installation access token within your workflow:
-
Store your GitHub App's ID as a secret. In the following example, replace APP_ID
with the name of the secret. You can find your app ID on the settings page for your app or through the App API. For more information, see "GitHub Apps." For more information about secrets, see "Encrypted secrets."
-
Generate a private key for your app. Store the contents of the resulting file as a secret. (Store the entire contents of the file, including -----BEGIN RSA PRIVATE KEY-----
and -----END RSA PRIVATE KEY-----
.) In the following example, replace APP_PEM
with the name of the secret. For more information, see "Managing private keys for GitHub Apps."
-
Add a step to generate a token, and use that token instead of GITHUB_TOKEN
. Note that this token will expire after 60 minutes. For example:
on:
workflow_dispatch:
jobs:
use_api_via_script:
runs-on: ubuntu-latest
steps:
- name: Check out repo content
uses: actions/checkout@v2
- name: Setup Node
uses: actions/setup-node@v2
with:
node-version: '16.17.0'
cache: npm
- name: Install dependencies
run: npm install octokit
- name: Generate token
id: generate_token
uses: tibdex/github-app-token@c2055a00597a80f713b78b1650e8d3418f4d9a65
with:
app_id: ${{ secrets.APP_ID }}
private_key: ${{ secrets.APP_PEM }}
- name: Run script
run: |
node .github/actions-scripts/use-the-api.mjs
env:
TOKEN: ${{ steps.generate_token.outputs.token }}
Notes:
- The following example is intended for GitHub.com. If you'd prefer to try the example using GitHub Enterprise Server, you must replace
https://api.github.com
with http(s)://HOSTNAME/api/v3
, and replace HOSTNAME
with the hostname for your GitHub Enterprise Server instance. You must also replace octocat/Spoon-Knife
with a repository on GitHub Enterprise Server.
- If you want to make API requests from the command line, GitHub recommends that you use GitHub CLI, which simplifies authentication and requests. For more information about getting started with the REST API using GitHub CLI, see the GitHub CLI version of this article.
-
Install curl
if it isn't already installed on your machine. To check if curl
is installed, execute curl --version
in the command line. If the output is information about the version of curl
, it is installed. If you get a message similar to command not found: curl
, you need to download and install curl
. For more information, see the curl project download page.
-
Create an access token. For example, create a personal access token or a GitHub App user access token. For more information, see "Creating a personal access token" or "Identifying and authorizing users for GitHub Apps."
Warning: Treat your access token like a password.
You can also use GitHub CLI instead of curl
. GitHub CLI will take care of authentication for you. For more information, see the GitHub CLI version of this page.
If these options are not possible, consider using another service such as the 1Password CLI to store your token securely.
-
Use the curl
command to make your request. Pass your token in an Authorization
header. Replace YOUR-TOKEN
with your token.
curl --request GET \
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
--header "Accept: application/vnd.github+json" \
--header "Authorization: Bearer YOUR-TOKEN"
Note: In most cases, you can use Authorization: Bearer
or Authorization: token
to pass a token. However, if you are passing a JSON web token (JWT), you must use Authorization: Bearer
.
You can also use curl
commands in your GitHub Actions workflows.
GitHub recommends that you use the built-in GITHUB_TOKEN
instead of creating a token. If this is not possible, store your token as a secret and replace GITHUB_TOKEN
in the example below with the name of your secret. For more information about GITHUB_TOKEN
, see "Automatic token authentication." For more information about secrets, see "Encrypted secrets."
Note: The following example workflows are intended for GitHub.com. If you'd prefer to try the examples using GitHub Enterprise Server, note the following differences.
- You must replace
https://api.github.com
with http(s)://HOSTNAME/api/v3
, and replace HOSTNAME
with the hostname for your GitHub Enterprise Server instance.
- You must replace
octocat/Spoon-Knife
with a repository on GitHub Enterprise Server.
on:
workflow_dispatch:
jobs:
use_api:
runs-on: ubuntu-latest
permissions:
issues: read
steps:
- env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
curl --request GET \
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
--header "Accept: application/vnd.github+json" \
--header "Authorization: Bearer $GH_TOKEN"
If you are authenticating with a GitHub App, you can create an installation access token within your workflow:
-
Store your GitHub App's ID as a secret. In the following example, replace APP_ID
with the name of the secret. You can find your app ID on the settings page for your app or through the App API. For more information, see "GitHub Apps." For more information about secrets, see "Encrypted secrets."
-
Generate a private key for your app. Store the contents of the resulting file as a secret. (Store the entire contents of the file, including -----BEGIN RSA PRIVATE KEY-----
and -----END RSA PRIVATE KEY-----
.) In the following example, replace APP_PEM
with the name of the secret. For more information, see "Managing private keys for GitHub Apps."
-
Add a step to generate a token, and use that token instead of GITHUB_TOKEN
. Note that this token will expire after 60 minutes. For example:
on:
workflow_dispatch:
jobs:
use_api:
runs-on: ubuntu-latest
steps:
- name: Generate token
id: generate_token
uses: tibdex/github-app-token@c2055a00597a80f713b78b1650e8d3418f4d9a65
with:
app_id: ${{ secrets.APP_ID }}
private_key: ${{ secrets.APP_PEM }}
- name: Use API
env:
GH_TOKEN: ${{ steps.generate_token.outputs.token }}
run: |
curl --request GET \
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
--header "Accept: application/vnd.github+json" \
--header "Authorization: Bearer $GH_TOKEN"
For a more detailed guide, see "Getting started with the REST API."