You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if the current API allows for obtaining the departures from a specific stop through the API i.e. JSON, rather than the web interface?
I can see there's this path: https://bustimes.org/stops/9400ZZNOLCM2/departures within the JavaScript resources for the main website, but this is HTML formatted as a part that gets included in the main web interface overall and refreshes a div element.
Please do let me know if this is a problem or there's a different endpoint you'd prefer me to use. I don't realistically expect it to become heavily used.
Hi @jclgoodwin
Thanks for your work on bustimes.org!
I was wondering if the current API allows for obtaining the departures from a specific stop through the API i.e. JSON, rather than the web interface?
I can see there's this path: https://bustimes.org/stops/9400ZZNOLCM2/departures within the JavaScript resources for the main website, but this is HTML formatted as a part that gets included in the main web interface overall and refreshes a div element.
I can do this: https://bustimes.org/api/stops/9400ZZNOLCM2/, but adding the depatures path throws a 404 Not Found, so I'm not sure if it is intended to be used this way?
Thank you!
The text was updated successfully, but these errors were encountered: