(Node.js) Twitter - Application Only Authentication

Demonstrates how to get a Twitter OAuth2 token for application-only authentication.

This allows you to issue authenticated requests on behalf of the application itself (as opposed to on behalf of a specific user). You don’t have the context of an authenticated user and this means that any request to API for endpoints that require user context, such as posting Tweets, will not work. However, the set of endpoints that will still be available can have a higher rate limit.

Your app will be able to, for example:

• Pull user timelines;
• Access friends and followers of any account;
• Access lists resources;
• Search in Tweets;
• Retrieve any user information;

And it will not be able to:

• Post Tweets or other resources;
• Connect to Streaming endpoints;
• Search for users;
• Use any geo endpoint;
• Access Direct Messages or account credentials;

Install Chilkat for Node.js and Electron using npm at Chilkat npm packages for Node.js Chilkat npm packages for Electron on Windows, Linux, MacOSX, and ARM

var os = require('os');
if (os.platform() == 'win32') {  
    if (os.arch() == 'ia32') {
        var chilkat = require('@chilkat/ck-node21-win-ia32');
    } else {
        var chilkat = require('@chilkat/ck-node21-win64'); 
    }
} else if (os.platform() == 'linux') {
    if (os.arch() == 'arm') {
        var chilkat = require('@chilkat/ck-node21-arm');
    } else if (os.arch() == 'x86') {
        var chilkat = require('@chilkat/ck-node21-linux32');
    } else {
        var chilkat = require('@chilkat/ck-node21-linux64');
    }
} else if (os.platform() == 'darwin') {
    if (os.arch() == 'arm64') {
        var chilkat = require('@chilkat/ck-node21-mac-m1');
    } else {
        var chilkat = require('@chilkat/ck-node21-macosx');
    }
}

function chilkatExample() {

    // It requires the Chilkat API to have been previously unlocked.
    // See Global Unlock Sample for sample code.

    // Note: Define your Twitter apps at https://apps.twitter.com/

    // We're going to send an HTTPS POST that looks like this:

    // POST /oauth2/token HTTP/1.1
    // Host: api.twitter.com
    // User-Agent: My Twitter App v1.0.23
    // Authorization: Basic eHZ6MWV2RlM0d0VFUFRHRUZQSEJvZzpMOHFxOVBaeVJn
    //                      NmllS0dFS2hab2xHQzB2SldMdzhpRUo4OERSZHlPZw==
    // Content-Type: application/x-www-form-urlencoded;charset=UTF-8
    // Content-Length: 29
    // Accept-Encoding: gzip
    // 
    // grant_type=client_credentials

    // Update these values with your consumer key and secret (also known as API key and API secret).
    var consumerKey = "TWITTER_CONSUMER_KEY";
    var consumerSecret = "TWITTER_CONSUMER_SECRET";

    var http = new chilkat.Http();

    http.BasicAuth = true;
    http.Login = consumerKey;
    http.Password = consumerSecret;

    var req = new chilkat.HttpRequest();
    req.AddParam("grant_type","client_credentials");

    // resp: HttpResponse
    var resp = http.PostUrlEncoded("https://api.twitter.com/oauth2/token",req);
    if (http.LastMethodSuccess !== true) {
        console.log(http.LastErrorText);
        return;
    }

    console.log("Response Status Code: " + resp.StatusCode);

    if (resp.StatusCode !== 200) {
        console.log("Expected a 200 response status code for success.");
        console.log(resp.BodyStr);
        return;
    }

    // We should get a JSON response like this:

    // {
    //     "token_type":"bearer",
    //     "access_token":"..."
    // }

    var json = new chilkat.JsonObject();
    json.Load(resp.BodyStr);

    console.log("Access token = " + json.StringOf("access_token"));


}

chilkatExample();