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
The only response documented is the '200' code, but while testing I received two different types of error:
The first one happens when entering a non-existing station (like Retie). It returns a reasonable error, just like the connections API. However, this is not a response code mentioned in the liveboard docs.
The second one is a little strange; since getting a connection to Vienna (ex: Brussels → Vienna) works, but somehow the station is not recognized for the liveboard request. It returns the following:
I stumbled upon these by testing out the API, and would be interested in adding these response codes to the docs myself (if it is not too difficult).
The text was updated successfully, but these errors were encountered:
The first one is a normal case, and the 404 result should have been documented. The second case seems like there is an issue with the response from the internal API used to obtain the data. It looks like that internal API is listing stations without an id, which would need to be handled correctly by the iRail API
The only response documented is the '200' code, but while testing I received two different types of error:
The first one happens when entering a non-existing station (like Retie). It returns a reasonable error, just like the connections API. However, this is not a response code mentioned in the liveboard docs.
The second one is a little strange; since getting a connection to Vienna (ex: Brussels → Vienna) works, but somehow the station is not recognized for the liveboard request. It returns the following:
I stumbled upon these by testing out the API, and would be interested in adding these response codes to the docs myself (if it is not too difficult).
The text was updated successfully, but these errors were encountered: