Hydratate users


#1

Hi all,

404:The URI requested is invalid or the resource requested, such as a user, does not exist.
{“errors”:[{“message”:“Sorry, that page does not exist”,“code”:34}]}

Once upon a time I received this error on my Twitter4j application.
I have discovered that this error comes from this api request

https://api.twitter.com/1/users/lookup.json?user_id=972187081%2C973610586%2C973686600%2C973769540%2C974159412%2C975763344%2C972201480%2C965921642%2C973979197%2C973797720%2C973989205%2C974109734%2C965846516%2C973806296%2C973945645%2C973697120%2C974010590%2C975182011%2C974175098%2C965837683%2C972237780%2C973839092%2C973937911%2C975020228%2C975170952%2C347563748%2C973864818%2C973959990%2C962247559%2C964521996%2C973923132%2C974964872%2C965762533%2C971836513%2C143609460%2C962166480%2C972181050%2C973682329%2C960120877%2C973612868%2C973623852%2C973698948%2C975039692%2C261300579%2C973877599%2C972129368%2C221527372%2C973839296%2C973938486%2C971880776%2C356718813%2C973543566%2C973824122%2C140596967%2C972182318%2C962453478%2C972192445%2C974080291%2C965643378%2C966139122%2C973824217%2C974137280%2C974971218%2C971840162%2C972285236%2C974101346%2C974266063%2C964641235%2C63156303%2C962180580%2C966114830%2C973810596%2C223162620%2C924252853%2C962263255%2C965884020%2C966094435%2C973891434%2C974051569%2C965905158%2C974126444%2C973787442%2C973878762%2C962264084%2C972310039%2C973764564%2C973616612%2C636167373%2C965865216%2C972261067%2C974957688%2C975935664%2C973789352%2C973976214%2C973578715%2C973794734%2C962171652%2C962218393%2C971785244%2C973850312&include_entities=true

Looking at each user, it seems like they are all deleted.
Why isn’t twitter returning any message about which user is retrievable and which is not?
There is any way to determine which user id is deleted looking at the response of lookup.json?
Until now the only solution that comes in mind to me, not consuming rest api tokens, is to check each requested ids against the returned ids, but this look to me more like a quick fix than a complete solution.
Thanks in advance.


#2

This behavior will be improved in the future.