node package manager


NodeJS wrapper for the GitHub API


A Node.js wrapper for GitHub API.

Install via npm

$ npm install github


Install via git clone

$ git clone
$ cd node-github
$ npm install

Client API:
GitHub API:

Create test auth file for running tests/examples.

$ > testAuth.json
    "token": "<TOKEN>"

Get all followers for user "defunkt":

var GitHubApi = require("github");
var github = new GitHubApi({
    // optional 
    debug: true,
    protocol: "https",
    host: "", // should be for GitHub 
    pathPrefix: "/api/v3", // for some GHEs; none for GitHub 
    headers: {
        "user-agent": "My-Cool-GitHub-App" // GitHub is happy with a unique user agent 
    Promise: require('bluebird'),
    followRedirects: false, // default: true; there's currently an issue with non-get redirects, so allow ability to disable follow-redirects 
    timeout: 5000
    // optional: 
    // headers: { 
    //     "cookie": "blahblah" 
    // }, 
    user: "defunkt"
}, function(err, res) {

There are a few pagination-related methods:

getNextPage(link, headers, callback)
getPreviousPage(link, headers, callback)
getFirstPage(link, headers, callback)
getLastPage(link, headers, callback)
NOTE: link is the response object or the contents of the Link header

See here and here for examples.

Most GitHub API calls don't require authentication. As a rule of thumb: If you can see the information by visiting the site without being logged in, you don't have to be authenticated to retrieve the same information through the API. Of course calls, which change data or read sensitive information have to be authenticated.

You need the GitHub user name and the API key for authentication. The API key can be found in the user's Account Settings.

// basic 
    type: "basic",
    username: USERNAME,
    password: PASSWORD
// OAuth2 
    type: "oauth",
    token: AUTH_TOKEN
// OAuth2 Key/Secret (to get a token) 
    type: "oauth",
    key: CLIENT_ID,
    secret: CLIENT_SECRET

Note: authenticate is synchronous because it only stores the credentials for the next request.

Once authenticated you can update a user field like so:

    location: "Argentina"
}, function(err) {

Create a new authorization for your application giving it access to the wanted scopes you need instead of relying on username / password and is the way to go if you have two-factor authentication on.

For example:

  1. Use github.authenticate() to auth with GitHub using your username / password
  2. Create an application token programmatically with the scopes you need and, if you use two-factor authentication send the X-GitHub-OTP header with the one-time-password you get on your token device.
    scopes: ["user", "public_repo", "repo", "repo:status", "gist"],
    note: "what this auth is for",
    note_url: "http://url-to-this-auth-app",
    headers: {
        "X-GitHub-OTP": "two-factor-code"
}, function(err, res) {
    if (res.token) {
        //save and use res.token as in the Oauth process above from now on 

Some endpoints are in a preview period and require a custom Accept header. See examples/getReactionsForIssue.js for an example. For updates on endpoints under preview, see

Relatedly, the Migrations api requires an Accept header value of application/vnd.github.wyandotte-preview+json.

When updating routes.json, you'll want to update/generate docs/tests:

$ node lib/generate.js

Dev note for updating apidoc for github pages:

$ npm install apidoc -g
$ apidoc -i doc/ -o apidoc/

Run all tests

$ npm test

Or run a specific test

$ npm test test/issuesTest.js

MIT license. See the LICENSE file for details.