Need Paid X (Twitter) API?

[halogen857]

Hi, nice library.

Do we need to use X API, and if so does it have to be paid version?

Based on this doc, the free X API just gives 1 requests / 15 mins which means we can't get data from all the sources in one run:

When I run npm run start I continuously get:

Error: Failed to fetch tweets for OpenAIDevs: Too Many Requests

Also, why not use a library to scrape tweets instead of using X API? This way there would be no limits

[ericciarla]

Good point. Can you recommend any library alternatives?On Jan 3, 2025, at 21:06, halogen857 ***@***.***> wrote: Hi, nice library. Do we need paid X API? Based on this doc, the free X API just gives 1 requests / 15 mins which means we can't get data from all the sources in one run: api.png (view on web) When I run npm run start I continuously get: Error: Failed to fetch tweets for OpenAIDevs: Too Many Requests Also, why not use a library to scrape tweets instead of using X API? This way there would be no limits —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[halogen857]

@ericciarla Hm, for Typescript maybe https://github.com/the-convocation/twitter-scraper could work

For Python this one but your library is written in Typescript: https://github.com/mahrtayyab/tweety

Do you think you could integrate this versus X API anytime soon into your library?

[ericciarla]

Might be cool, but I am going to stick with the X API for now. Feel free to try it out yourself!

[skhotdotcom]

I think it would be ideal to point out in the readme that 1. all the api's are required for the app to run successfully (currently the documentation makes them appear "optional", and 2. that using X API will likely require paid API access to run the app successfully.

This is an interesting project - reminds me of something I did years ago for fun with drag queens from RuPaul's Drag Race 😅. I wanted to try it out but the paid API was a barrier and I would have avoided the time investment if I had known that upfront.

Cheers!

[halogen857]

@skhotdotcom is correct. Would've saved time.

Also the X API is extremely expensive. To use this tool with many sources, it'll price nearly everyone out. Which is a shame, because just by scraping it'll let everyone use it practically free.

Though one workaround with X API might be: create an X list > add all accounts to list > pull tweets from list

@ericciarla

[ericciarla]

@skhotdotcom @halogen857 - great points. Currently I am on the X API pro plan which is expensive but worth it in my opinion. I made a PR which makes X and Firecrawl API keys both optional. I recommend using Firecrawl for a more cost effective trend monitor for blogs and websites!

Also I am open to merging an alternative to the X API if someone in the community wants to create it. Cheers!

[ericciarla]

@skhotdotcom @halogen857 - great points. Currently I am on the X API pro plan which is expensive but worth it in my opinion. I made a PR which makes X and Firecrawl API keys both optional. I recommend using Firecrawl for a more cost effective trend monitor for blogs and websites!

Also I am open to merging an alternative to the X API if someone in the community wants to create it. Cheers!

[halogen857]

Ok will check out new changes. As for merging alternative, not sure can help much with coding, just know that scraping could be beneficial.

Thanks for library.