Good Day Londoners,
Our application has been making use of the following API call which obtains journey information from Heathrow Terminals 1-2-3 to London Paddington
https://api.tfl.gov.uk/Journey/JourneyResults/1000105/to/1000174?mode=tflrail&app_id={api_id}&app_key={api_key}
As of 2019-11-25 at approximately 11am, the API call has seen an increase of intermittent “(500) Internal Server Errors”. To note, this is not a rate limit issue as it occurs on an unused API key too, well within the limit.
When data does return successfully from the API call, the information itself does not seem to be correct.
This is seen by noting the mode of the API request being tflrail and the mode of the results is returned as national-rail specifying Heathrow Express as the train used.
The intention of the API call is to get the TFL Rail journey as documented in the timetable
here > http://content.tfl.gov.uk/paddington-heathrow-19-may-14-december-2019.pdf
linked from > https://tfl.gov.uk/modes/tfl-rail/tfl-rail-timetables.
As I understand it, this TFL Rail track is part of the Elizabethan/Crossrail service which is not in full operation yet - but makes use of this part of the track for the time being.
Any help would be appreciated in identifying what might have changed in the API or operationally.