-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NMBS endpoint changed: Error 500 when querying connections #319
Comments
Example alternative: using the mobile API enpoint. We'd need to decipher it though.
|
A temporary implementation is in place. Following functions are not available at this moment:
Anyone who wants to help out debugging the new implementation is welcome to do so! |
FYI I wrote two mobile HAFAS API clients in JavaScript, so maybe the parsing logic is helpful to you. The client doesn't parse everything the API provides, but most of it, and has been running fine for the past 2 years. Specifically, look at the following files:
Let me know if I can assist you with HAFAS-mobile-API-related problems, as long as they're not specific to Belgian Rail. |
@derhuerst Thanks! I've looked around for a bit, and it seems really helpful (especially the implementations for vbb/db give me some more insights on how to use it)
Have you seen the search parameter |
According to traffic by the official NMBS app:
This should be enough to resolve all our issues with the new parser
|
I haven't, sorry. What you can do though is use e.g. mitmproxy to redirect traffic of the common apps through your machine and record all requests. By doing this, you can reverse-engineer the parameters. |
@derhuerst Just figured it out how to search on arrival time using fiddler :) Still wondering what that liveSearch parameter is, it's always included, always false, and doesn't seem to affect anything. I've set it to true atm for our application in the hopes that it will return fresher data or anything. |
…rect query to only show trains #319
…eywords for status, parse intermediate stops but don't include them in API output yet #319
Cause by HTML
The text was updated successfully, but these errors were encountered: