twitter-api-client VS national-geographic-api

Maybe this?

const mokkappsTwitterId = 481186762; const searchQuery = 'mokkapps'; const searchResultCount = 100; const fetchRecentTweets = async secretValues => { // Configure Twitter API Client const twitterClient = new twitterApiClient.TwitterClient({ apiKey: secretValues.TWITTER_API_KEY, apiSecret: secretValues.TWITTER_API_KEY_SECRET, accessToken: secretValues.TWITTER_ACCESS_TOKEN, accessTokenSecret: secretValues.TWITTER_ACCESS_TOKEN_SECRET, }); // Trigger search endpoint: https://github.com/FeedHive/twitter-api-client/blob/main/REFERENCES.md#twitterclienttweetssearchparameters const searchResponse = await twitterClient.tweets.search({ q: searchQuery, count: searchResultCount, result_type: 'recent', }); // Access statuses from response const statuses = searchResponse.statuses; };

To be able to fetch the follower count from Twitter API I decided to use FeedHive’s Twitter Client. This library needs four secrets to be able to access Twitter API. We will store them in the AWS Secret Manager, my article “How to Use Environment Variables to Store Secrets in AWS Amplify Backend” will guide you through this process.

twitter api client

Although, that's not the full story. Because I did make a very primitive scheduler for personal use, back in August/September, and that's where I created the Open-Source project twitter-api-client which is a NodeJS client for interacting with the Twitter API. This client is now a core module of FeedHive.

In the first two parts of this tutorial, we went over how to create a Twitter bot that sends out tweets from the Today in History API and then created scheduled tasks that make sure these tweets are tweeted automatically at certain times of the day. We are using twitter-api-client to easily connect to the Twitter API. You can see the bot for this tutorial in live action on @HistoryBot7.

We're going to be using the twitter-api-client to interact with the Twitter API more seamlessly.

Google search https://github.com/crisboarna/national-geographic-api