Hello!
I got this email from NS the other day. I had to use google translate so the english is difficult to understand in parts.
Dear NS API user,
Thank you for your interest in the NS API. We have moved past six years to the API Portal where you have a subscription to the "Public-Travel-Information".
By some internal shifts when we were not yet in the picture, there still have to make a small change to customers.
If you want to continue to use the opportunity to ask for travel information to, the following changes should be made:Go to the API portal: https://apiportal.ns.nl/
Sign it with the account that you have previously created
Find the product "NsApp" and subscribe to this product
A new API key is created you need to use.
The endpoints change https://gateway.apiportal.ns.nl/public-reisinformatie/ to https://gateway.apiportal.ns.nl/reisinformatie-api all parameters in the URL unchanged.
Good to know is that the limits are reduced on the new endpoints.
This is because the NS API is intended for private customers and not for commercial purposes. Therefore, the prescribed limits will have to be sufficient.
The "NS.nl-Public-Price Information" api does retain the endpoint on which it runs. If you use this API here for you so do not change to take effect.
For questions about this API you can still contact nsr.api@ns.nl .
If you have questions in the remainder of the contents of the APIs contained in the product can NSapp posing to Mlab@ns.nl .
The team that developed the API receives direct all questions and can respond best to this.
All public information number endpoints will be removed January 31 from the API portal. So please before this date to switch to the new endpoints.
For questions about this migration, you can contact nsr.api@ns.nl
Sincerely,
Sandra Rensink
Product Owner Travel online
My understanding is that they will be migrating all endpoints over to the new API (...apiportal.ns.nl/reisinformatie-api/...) and deprecating the old one (...apiportal.ns.nl/public-reisinformatie/...) in January. Everything else should stay the same.
I've tested a few of the endpoints on the new api and query params, responses all appear to be the same.
So the strings need to updated from public-reisinformatie to reisinformatie-api.
Old:
New:
There is one issue. The new API requires a different API key. The old API Key will not work, it will return a 401 if used. This would be a breaking change for users so I guess it would be Major version increment.
So: 0.0.3 . => 1.0.0
What approach would you like to do?
Update the strings and do a major version bump with a note about the change in the README?
Or perhaps pass the domain string to use alongside the API key?
Or something else?
I've no problem putting up a PR if you want?
Hello!
I got this email from NS the other day. I had to use google translate so the english is difficult to understand in parts.
My understanding is that they will be migrating all endpoints over to the new API (
...apiportal.ns.nl/reisinformatie-api/...) and deprecating the old one (...apiportal.ns.nl/public-reisinformatie/...) in January. Everything else should stay the same.I've tested a few of the endpoints on the new api and query params, responses all appear to be the same.
So the strings need to updated from
public-reisinformatietoreisinformatie-api.Old:
New:
There is one issue. The new API requires a different API key. The old API Key will not work, it will return a 401 if used. This would be a breaking change for users so I guess it would be Major version increment.
So: 0.0.3 . => 1.0.0
What approach would you like to do?
Update the strings and do a major version bump with a note about the change in the README?
Or perhaps pass the domain string to use alongside the API key?
Or something else?
I've no problem putting up a PR if you want?