Journey API returns status 300 (Multiple Choices) for some queries between exisitng NaptaIds. Here are several samples. Looks like some stations like new New Cross and Upminster are affected.
āUpminster stationā is actually THREE stations. The C2C line, the District Line and the London Overground line. The lines are not totally not connected: the Overground is connected to the rest of the rail network at Romford, and the District line isnāt connected to the National Rail network (mainly because the Underground uses third-rail DC current and the C2C line is overhead AC power, both with different signalling systems).
There most definitely is a WC1X, but you put me on the right track. The āfromā parts have incorrect inner post codes, so I guess I will handle this as an error.
Maybe 300 potentially isnāt the right status code to respond with though?
Itās not by decision! I personally find that TfL has the most logical and helpful error codes of all the public APIs I use. Ever tried voi https://api.voiapp.io/ ?
I personally find that all the Microsoft-based ā$typeā things in the TfL output somewhat redundant, but otherwise itās almost wholly consistent and logical.
WC1X 8AL has existed since 1980, a quick Google search revealed and appears to be a genuine area rather than a business-specific one. I suspect.that TfL has updated itās postcode list at least once since 1980!
