#1

Hi there,

I am new to Twitter API. I have got the search up and running, but even though I am using full-archive search and have an academic twitter account, I cannot see historical Tweets.

I have used the start_time key of e.g. 2020-05-21T00:00:00.00Z and end_time of 2020-07-21T00:00:00.00Z but it still only shows me Tweets in the last 24 hours. I set the cap to 10 Tweets because I don’t want to use up my allowance on the wrong Tweets, which is why I think it is only going back over the past day. What am I doing wrong?

Also the Tweets are cut-off, so I cannot read them in their entity. How do I prevent them being shortened?

Thanks for your help,
A fellow Tweet developer

#2

Can you share a code example?

Based on what you are describing, there might be a chance that if you are using a third-party library or SDK, it does not currently support v2 and full-archive search.

#3

One idea that comes to my mind is that the cap can be a problem. Full Archive Search has rate limit of 1 request per second, so maybe you are making too many requests.
Here you can see more info about rate limits:

1 Like
#4

Hi Andy, thank you so much for responding.

I tried to share my GET URL, but it is not allowed in this response, so instead I am sharing a print screen:

GET full archive
GET full archive1802×1014 183 KB

The print screen shows my start time and end time: start_time=2020-05-21T00:00:00.00Z&end_time=2020-07-21T00:00:00.00Z

I am using postman with the template collection “Twitter API v2”. Within “Twitter API v2”, I am using “GET Full-archive search”.

I am using my bearer token for authorisation. I tried to use Auth 2.0 but the GET URL does not work, however it does when I use the bearer token option.

Please let me know your thoughts,

Melody

#5

Hi Luka,

Thanks for your suggestion. I am new to Twitter’s API and learning as I go along. I set the limit to 10 Tweets for the search because I didn’t want to use up my allocation. However, I was repeatedly searching to try out different combinations, so maybe that’s why it timed out. Is there a way to run test searches without using up your allocation?

#6

I don’t think there is. But the problem might not exactly the 10 Tweets as maximum_results, but the fact, that you can request these Tweets only once a second, and only 300 times per 15 minutes.
I didn’t use Postman, but you should see if you can somehow make only one request per second.

I’ve also read that it’s not a tool for downloading large amount of tweets. So maybe you should use some programming language for that.

Also, your monthly downloaded Tweet limit is 10 million, so maybe you don’t have to worry about it that much.

You can read more about limits and rates here:

You can also check how many more Tweets you can download in your dashboard. It should look something like this:

image
image1568×412 31.8 KB

1 Like
#7

That’s all sounds correct. You’re probably only getting Tweets from the past day since you’ve only asked for 10 results. What do you mean by the Tweets are getting cut off or shortened?

#8

Hi Andy, sorry for delay in replying I had to revise for my masters exams. A colleague has helped me to stop the Tweets getting shortened. However there is still the issue, that I cannot access historical Tweets. I looked on my account and it says that my app has violated Twitter’s rules. But I’m really not sure how and this was not intentional, my apologies. I have submitted a help ticket. Could this be why I can’t access historical Tweets? What is the fastest way to rectify this?

#9

I think it was maybe an automated thing that caught the app by mistake - other people on the forum have similar problems - maybe the best way is to request it to be unsuspended via Platform form

#10

Thanks I made a request yesterday. Do you know how long it takes to get it fixed?

#11

Hard to say unfortunately - could be a couple of weeks in the worst case.

#12

Oh gosh it could be a long time then. I have less than 2 months to complete my thesis and need the data. Do you know if there is anyway to expedite the request?

#13

No idea, sorry - i guess some twitter people read these forums, and you’ve already filled out the form, so i don’t know of any other avenue to try.

#14

Thanks for responding, I’ll just wait and see…