The cloud.tfl.gov.uk domain stops working
TfL Trackernet feeds
Stopped working
On August 31, 2024, the cloud.tfl.gov.uk host was retired. Requests targeting this domain for TfL Trackernet feeds fail after this date.
What to use instead of these calls
Direct calls to the Trackernet feeds on the api.tfl.gov.uk host under the trackernet path, such as trackernet LineStatus, using a TfL API Portal subscription key. Moving requires more than updating the host, as a person must generate a new API Portal subscription key to sign the requests.
The new feeds are signed with a TfL API Portal subscription key that a person must create.
In TfL Trackernet feeds's words
The old cloud.tfl.gov.uk domain will be retired on Saturday 31 August.
Facts
- API
- TfL Trackernet feeds
cloud.tfl.gov.uk - Kind
- Endpoint removal
- Announced
- May 23, 2024
- Takes effect
- August 31, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against TfL Trackernet feeds's own pages
Questions
When does this change take effect?
Calls to these calls on TfL Trackernet feeds stopped working on August 31, 2024.
What happens to calls after August 31, 2024?
They have failed since August 31, 2024.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.