Mobile.twitter.com/{id}/status/{tweetid} not working


#1

Hello!

I’m running into an issue today with mobile.twitter.com/{id}/status{tweetid} urls. It redirects you to a “Sorry, that page doesn’t exist” message if you reference by id instead of username.

For instance this doesn’t work https://mobile.twitter.com/347155238/status/586479479263866880
But this does https://twitter.com/347155238/status/586479479263866880

Maybe something changed? I’ve tested it on multiple devices and browsers and it’s pretty consistent.

Any help would be appreciated!

Thanks,
Cam


#2

What specifically are you trying to retrieve, and where are you finding / generating these URLs?

If you are using the API, you should be hitting api.twitter.com with the GET statuses/show/:id endpoint. We don’t support the use of web scraping techniques and these are not guaranteed to work.


#3

Thanks for the reply Andy! I just realized I posted in the wrong forum, I meant to post this in the Streaming API forum–but it might not be relevant.

From the streaming API we are getting the user ID and the tweet ID and then we just use those to generate the link.

It doesn’t seem to be an issue if you use the username instead of the ID, but everything I read indicated it was probably best to use the ID since users frequently change their usernames.

Thanks,
Cam


#4

Aha! I understand now :smile:

Unfortunately the web endpoints are not supported from an API calling perspective, so if that method no longer works you’ll have to resolve the user ID to an @handle by calling the API to do so.

You could also use the oEmbed endpoint to just pass in the (unique and unchanging) Tweet ID to generate content for display.


#5

Ah, gotcha! I will definitely look into the oEmbed endpoint.

Thanks for your help Andy!


#6

Desktop has always worked for me no matter the username value e.g. https://twitter.com/x/status/586479479263866880 and it looks like mobile will as well. https://mobile.twitter.com/x/status/586479479263866880. It’s odd that having the userId causes a 404.


#7

I thought so too, that’s why I at least wanted to bring it to someone’s attention just in case it wasn’t intended.