Hello Everyone 
,
I’m now working on a project that uses real-time data from many public transport operators to enhance the commuting experience in London. Even though I’ve looked into a couple of the existing APIs, such as TfL’s Unified API, I still have a few queries and ideas that I’m hoping this community can address.
Real-Time Disruptions Data: Although disruption data is accessible, I’ve found that it occasionally lacks the detail required to make wise decisions. Is it possible, for example, to get more precise information in real-time regarding particular disruption kinds or causes (such as signal failures, accidents)? 
This would significantly improve my application’s predictive power.
Crowding Data: While crowding information is currently available through the API, I’m wondering whether there are any plans to increase the data’s coverage or accuracy. Getting crowding levels for buses or DLR that are comparable to those for the London Tube is something that really interests me.
Use of API Rate Limits: Is there anyone who can talk about how they’ve managed API rate limits when growing an application? I’m thinking about developing a service that might be highly used, so I want to make sure everything runs smoothly and there are no obstacles in the way.
Future Plans: Will TfL be releasing any new data sources or API functionality in the near future? It would be beneficial to keep up with these advancements in order to plan for future project improvements.
https://techforum.tfl.gov.uk/t/missing-london-overground-timetable-info/salesforce-developer
Any advice, experiences, or insights would be very beneficial. In addition, if anyone knows of anyone working on related projects, we may collaborate!
Thank you 
in advance.