RettiwtError: NOT_FOUND Tweet Fetch
Closed this issue · 8 comments
When trying to obtain the data of a tweet it says that it does not exist even though it does, it has been tried with a lot of tweets but each one of the tested ones says that they do not exist, that only affects when obtaining information of a tweet, but it does not affect when obtaining the information of retweets of a tweet.
I am currently using an authenticated account
- Can you provide me with the ID of a tweet which throws this error?
- Does the same error occur when fetching the details of a tweet without logging in (i.e, not using an API_KEY)?
- https://x.com/jack/status/20 - 20
- https://x.com/Bybit_Official/status/1752950869300244564 - 1752950869300244564
- https://x.com/elonmusk/status/1821415290112209097 - 1821415290112209097
- Due to some issues I can't check that right now.
Strange, it's working as expected on my end. But, the endpoint has a history of causing this issue from time to time, since this endpoint is not exposed directly in the web-app (the web-app uses a different endpoint for fetching details of tweet and it's a wasteful one since it also fetches the replies of the tweets). As a fail-safe, I'll implement the same endpoint as the one used by the web-app.
Twitter detects that it is a bot
Probably this, since the particular endpoint is not even utilized by the Web-App. I'll be switching it to the same endpoint as the one used by Twitter.
the problem occurs in Railway but not in Bot-hosting.net
Something I've notices is that a lot endpoints work weird when hosted on services like Railway, Vercel, etc. AFAIK, cloud platforms like GCP work alright. It needs extensive testing though.
In the meantime, I'm switching over to alternative endpoints.
It may be possible that the tweet endpoint you use (Hidden)
Remember the debacle when Twitter/X forced people to login to see tweets, which broke the functionality of embedded tweets in websites? This (hidden) endpoint is that endpoint which was setup to make embedded tweets work. That's why it's blocked almost instantaneously if scraper activity is detected, since this endpoint is not meant for logged in users.