-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[twitter] 403 Forbidden
during pagination caused by expired guest token
#3445
Comments
Oh, I forgot to mention an important detail: I use long delays between downloads. I'll try reducing |
Not sure... |
The errors occurred around 3 hours after activating the guest token. I'm running |
I have successfully reproduced the issue:
Judging from the logs of the past download jobs, if there were any API calls in between, they would not have reset the timer. |
403 Forbidden
during pagination: guest token expired?403 Forbidden
during pagination caused by expired guest token
I recently noticed that sometimes a download job would terminate with a
403 Forbidden
error during pagination. I scraped around 10 large accounts (>3200 tweets) in the past few months and got 7 errors. Only one of them came from theUserTweetsAndReplies
endpoint, while the others were from thesearch
endpoint. What's interesting is that instead of the genericForbidden.
message, the former API endpoint reportedBad guest token
. Also, it's possible to manually "resume" the search by using the samemax_id
as the failed request, so I don't think it's because of the API's limits.The text was updated successfully, but these errors were encountered: