Hi @jamesevans , thanks for the update… working now 
cheers
Neil
1 Like
Hi. I’m trying the new API and I’m getting timeouts very often. Also, it seems that this API is slower (6x times). Is that possible?
Example of request: https://api.tfl.gov.uk/trackernet/PredictionDetailed/N/BPS
1 Like
Hi! It is not currently possible to retrieve detailed data for Battersea Power Station and some other stations. This is an existing limitation with the old API. With the old API it would instantly return a 204 response, but with the new one it will timeout (not ideal, I know).
I’ve compiled a table of stations where you’ll see these kinds of timeouts (where status_code=204):
1 Like
~I see, thanks! My other concern is that this API is slower.~ UPDATE: is seems this was related to something else. Thanks!
Just signed up for the new API, but both the live version at api.tfl… and the preproduction version at api-preprod.tfl… seem to be showing data from 3 days ago, 14:57 on 2nd September. Am I doing something wrong or has the API just broken?
@Muzer
If you look at the "Issue with Data Feeds* thread you will see that TfL suffered a cyberattack which is messing up some data feeds, along with some internal systems.
Hi everyone!
We integrated the original TrackerNet API into a desktop application probably the best part of a decade ago. In that time, we seem to have lost our newsletter subscription, so the first we saw of this change was on the 31st when the old API was sunset and requests started to error. (Whoops!)
I note that the new API went live about 3 weeks before the old one was sunset. As we develop software used in the broadcast industry and, like other industries, we have much longer release cadences than other developers.
Although I appreciate this may have been outside of your control, we’d be grateful if you could consider a longer changeover period when sunsetting legacy API’s in the future, to allow more time for our customers to discover + install the update.