#1

Hi, I just subscribed to Twitter’s premium search API. My subscription allows for 100 requests per month. What is one request? If I query for one term, and there are 1 million results, and I page through the get all the results, is that one request, or is it multiple requests based on the number of pages?

Thank you.

#2

A request is a single REST call to the API. If you make a request and ask for 100 results, that’s 1 request.

#3

and I page through the get all the results

Another thing that is surprising sometimes, is that 1 premium call gives you 100 results, or 30 days worth of results, whichever is first (it’s 500 results in a paid plan). So you will always need multiple calls to the API

#4

Mixed emotions about paging being applied to the cap, but it is what it is, and my apps primarily use data push anyway. Hope you’re well, Igor

1 Like
#5

I’m surprised that paging applies to the result. The premium plan says you can get a max of 1.25 million tweets in a month, how can you even get that many tweets if you can only get max 500 per request and 100 requests per month?

I just need to pull a complete set of historical tweets for a list of accounts, that is why I got the subscription. I’m worried I won’t be able to do this with only 100 requests.

#6

I just need to pull a complete set of historical tweets for a list of accounts

You could get pretty far with GET statuses/user_timeline | Twitter Developer - that covers the last 3200 tweets which for many accounts is their entire history. The fullarchive search can then fill in the rest.

The way i read it is that 1.25 million is an upper bound if you keep upgrading and get the highest paid tier.

1 Like
#7

I’m already doing this. I already have 1.5 million tweets by using the free api with 3200 tweets. Some accounts have less than 3200 tweets but others have a crazy amount of tweets, and the 3200 limit only got me 1-2 months of tweets. So, I’m worried about not being able to get the complete history now even with a premium subscription. Not to mention it is kinda a pain in the behind to stitch together what I got from the free api with the the premium api, because every account has a different date now for their last tweet. But it’s ok, I will keep persevering.

1 Like
#8

as an update, I did use up my premium request quota, and it is not nearly enough. I did an estimate since I can get a status count through the free api, versus the number of statuses I already have. I still need to get about 4.6 million tweets. Or make nearly 10,000 requests. This is apparently more requests then the top most tier. Is there any way I can just pay for exactly what I need? I feel like the premium service is not exactly designed for my use case. I just need a dump of those tweets.

Thank you.

#9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.