Twitter Reverse Geocode - 404 Error 34



My app is suddenly failing to complete reverse geocode look-ups. It was working on Friday. I’ve also tried through and get the same problem - Error 34 (This resource doesn’t exist).

as an example, here is the address I am calling:


Has something changed to the API? or the Endpoint?


That’s weird - the endpoint itself is there (responds with an Error 3 if you don’t specify coordinates).

Similarly, the sample request listed in the documentation works OK.

Has that coordinate pair definitely worked in the past? (Google Maps puts it in the middle of the English Channel AFAICT?)


Cheers, It appears something else has corrupted all my coordinates. This was meant to be London.


ok, phew! I hope you can figure it out! :slight_smile: