Unable to instantiate TwitterClient without accessToken and accessTokenSecret about twitter-api-client HOT 1 CLOSED

Hi @dvorsky.
I'm sorry for the late response.

Yes, this is expected behavior.
You cannot instantiate the client without providing all sets of keys.

The first time you're instantiating the client (to obtain the tokens), you need to use the credentials provided when you create the app on the developer.twitter.com platform.

Now, after you instantiate with those, you can make a call to oauthRequestToken, to obtain the tokens.

const twitterClientAuthenticate = new TwitterClient({
  apiKey: process.env.TWITTER_KEY,
  apiSecret: process.env.TWITTER_SECRET,
  accessToken: process.env.TWITTER_ACCESS_TOKEN,
  accessTokenSecret: process.env.TWITTER_ACCESS_TOKEN_SECRET,
});

const tokens = await twitterClientAuthenticate.basics.oauthRequestToken({
  oauth_callback: 'https://call-back-url/callback',
});

Now, follow the authentication flow explained on the Twitter Documentation page.
Then instantiate a new client using the OAuth token and secret you obtained.

const twitterClient = new TwitterClient({
  apiKey: process.env.TWITTER_KEY,
  apiSecret: process.env.TWITTER_SECRET,
  accessToken: oauth_token, // <- the one you obtained,
  accessTokenSecret: oauth_token_secret // <- the one you obtained,
});

Now, you can use the second client instance client to do stuff with Twitter on the behalf of the authenticated user 😄

from twitter-api-client.