Select the premium package to see the pricing:

Total Requests PER MONTH --- PRICE PER MONTH

Up to 500 --- $149.00

Up to 1000 --- $289.00

Up to 2,500 --- $699.00

Up to 5,000 --- $1,299.00

Up to 10,000 --- $2,499.00

"I mean, it's one banana Michael. How much could it cost? 10 dollars?"

A request can have 500 tweets in it. Makes it slightly better but still overpriced

This has to be a joke. 10k requests / month @ $2.5k...

Surely a single small region would eat this up alone?

This is showing how much the advertising loss is squeezing all angles.

And there are enterprise packages where you can contact them to receive more info.

I don’t know what type of application would find it worth it to pay these kinds of ridiculous prices.

This is not the new API pricing, this is an existing API's pricing that has probably been the same for years.

This API launched in 2017 with what appears to be the same pricing structure:

> Pricing for these elevated tiers of the Search Tweets API starts at $149/month

https://blog.twitter.com/developer/en_us/topics/tools/2017/i...

Well, clearly not.

Quote from @TwitterDev:

"Starting February 9, we will no longer support free access to the Twitter API, both v2 and v1.1. A paid basic tier will be available instead"

Yes, they are adding fees to the currently free APIs, the OP is not the currently free API, it's a paid API that has been around since 2017 and has always been expensive. There has been no announcement of what the new cost structure will be because that would require Elon Musk to plan more than a few days ahead

Yea, Elon is screwed. He’s not recovering Twitter, at least not on any timescale that matters.

The first thing that stood our is that the table has a duplicate "Monthly Tweet cap" entry. Not enough people to review things before release?

This seems egregiously expensive for what you get. Who's the target demographic for this service? Does it really make sense in the appropriate industry?

Misleading title: This is only the API pricing for 30-day search, not the other products.

As other said, this probably hasn't changed in a while, but I haven't confirmed.

One major reason to provide an API for a website like Twitter is to reduce the load from sloppy scraping and other actions people are going to do either way. This seems like a mistake.

Is the strategy that he wants to force traffic to twitter.com, thus maximising ad revenue?

Anyone able to see how this has changed over time? I'm trying to look on archive.org, which claims to have snapshots going back to 2017, but the website is being super slow and throwing errors every time I try to actually view one: "Failed to fetch product data.\nUnknown error."

https://web.archive.org/web/20190614191714/https://developer...

This is Wrong. This is about the old v1.1 API not the new v2 API https://developer.twitter.com/en/docs/twitter-api/getting-st...