The 9292 Reisadvies API offers the opportunity to use 9292’s planner engine within a website or app to give travel information from address to address using all of the public transport options (including personal and rentable vehicles and on-demand transportation) in the Netherlands.
This documentation describes the features of the 9292 Reisadvies API and gives general information on how to use them. This information is an addition to the Swagger documentation we provide.
The 9292 Reisadvies API supports both XML (< v4)and JSON. Knowledge of Web API's and JSON are essential to be able to use this API.
Usage of the 9292 Reisadvies API is prohibited without the approval of 9292.
It is mandatory to show the 9292 Logo. 9292 will give approval on the location of the logo before you transfer to the production environment. This is done to safeguard the usage of the 9292 logo.
The logo can be found at the following URL:
Software version |
Documentation version |
Remarks |
11-05-2020 |
20-01-2020 |
|
24-09-2020 |
01-09-2020 |
|
08-12-2020 |
15-10-2020 |
|
22-03-2021 |
23-03-2021 |
|
26-04-2021 |
26-04-2021 |
|
28-06-2021 |
|
|
29-06-2021 v2.8.4 |
|
|
05-07-2021 v2.8.5 |
|
|
04-08-2021 v2.9.0 |
|
|
08-09-2021 v2.9.1 |
|
|
11-10-2021 v3.0.1 |
Added a new version (v3) which contains the following updates:
|
|
22-11-2021 v3.0.2 |
|
|
07-12-2021 v3.0.3 |
|
|
19-01-2022 v3.0.4 |
|
|
04-01-2023 |
Added a new version (v4) which contains the following updates:
|
The 9292 Reisadvies API is secured and can only be used when you have been given a Token or a so-called APIKey by 9292. This ‘Token’ exists of symbols and letters, which is provided through a license agreement. This license agreements allows our customers to make requests to our server.
This ‘Token’ should be kept secret and not shared with any other party. In case of misuse 9292 can deactivate your account.
You will receive a Token via e-mail from the 9292 Servicedesk. The Token is your identification code which gives you access to the acceptance environment of the 9292 Reisadvies API. Once you have completed your implementation and your service has been tested by 9292, you may switch to the production environment. The 9292 Servicedesk will send you a new Token for the production environment.
After transferring to the production environment, the acceptance environment will remain accessible for two weeks.
The Token must be included in the header of each request. Here is an example of a request header:
Header Key |
Value |
Authorization |
Token <MY_TOKEN> |
Accept |
Application/JSON |
Content-Type |
charset=utf-8 |
Please note:
The 9292 Travel Advice API only supports HTTPS requests.
Tokens are sent to identify a particular customer and thus the tapping of the HTTP stream can be abused. This can result in a higher count in the statistics and a higher invoice.
The 9292 Reisadvies API makes use of changing data (public transport timetables). This is why only data within the validity date range can be used. When an invalid date is used, the 9292 Reisadvies API will return an error message (400 BadRequest).
The validity can be requested using the Dataset endpoint.
The Dataset requests are not counted as billable requests.
The 9292 Reisadvies API offers an endpoint that indicates whether the API is available and if it is in a healthy-state. The API’s health-state can have the value “Healthy”, “Degraded”, and “Unhealthy”. The state is determined by the availability and proper functioning of the API’s sub-systems.
These requests are not counted as billable requests.
In order to request a location, you will have to call the Locations endpoint of the 9292 Reisadvies API. With a location request, you can get information about a station, place, address, stops or POIs (Point of Interests).
A location request returns 5 locations by default. The number of locations can be configured in the request to be any number between 1 and 10. These locations are sorted by type in the following manner: first locations will be the stations, then the bus/tram/metro stops, then street names, postal codes, etc.
The location request also supports the filtering of the locations based on one or more location types.
This Locations endpoint is NOT an autosuggest. However, it is possible to develop your own autosuggest based on this endpoint.
The request of a location is not counted as a billable request.
In order to request locations near a particular point, you will have to call the NearByLocations endpoint with latitude and longitude coordinates or a ‘locationId’. The 9292 Reisadvies API will then return a list of all locations within a 500 metre radius. This list of locations can consist of stations, stops or point of interests (POI).
The request returns 5 locations by default. The number of locations can be configured in the request to be any number between 1 and 10.
The location request also supports the filtering of the locations based on one or more location types.
The request of nearby locations is not counted as a billable request.
The Journeys endpoint is used to request a public transport travelling advice. The request returns 9 responses by default. These are advice around the requested time. The number of responses cannot be adjusted.
The FromId, ToId and ViaId must correspond to the ‘Id’ of the location retrieved from the Locations endpoint.
Attributes are data which is sent by a transport company (i.e., NS) that pertains to a (part of the) journey. The Attributes element is not shown in every advice, but only in those where the information is included by the public transport company.
The following table contains examples of possible attributes.
Attribute Id |
Attribute value |
Description/Remarks |
TWEE |
alleen 2e klas |
The ‘Only 2nd class travel’ Attribute only appears on a small number of trails, namely:
|
WCA |
Rolstoeltoegankelijk |
Is shown when the modality is accessible |
SPEC |
Speciaal ticket vereist |
Usually shown with Intercity Direct & International trains |
FINI |
fiets meenemen niet mogelijk |
Usually shown with Intercity Direct & International trains |
RESM |
Reserveren mogelijk |
Usually shown with Intercity Direct & International trains |
TSR |
Toeslag Schiphol - Rotterdam |
Usually shown with Intercity Direct & International trains |
Attributes can be found in the “Attributes” component of a travel advice. The Attributes component consists of zero or more LegAttributes. Here is an example of an Attributes component:
Example |
"attributes": [{ |
Each public transport travelling advice contains a “JourneyId” which is a unique value that can be used to identify a travelling advice.
Here is an example of a partial travel advice response containing a JourneyId:
Parameter |
Description (example) |
ShowJourneyId | true |
Here is an example of a partial travel advice response containing a JourneyId:
Example |
{ |
A travel advice can contains 3 types of suggestions for alternative travel options:
Here’s an example of a travel advice which contains all 3 types of suggestions:
Example |
{ … |
Disruption messages can be associated with a journey. These messages are sent by the transport company (i.e., NS) for a particular place, station, stop, service and/or for all trips done by an operator.
The disruption messages, if present, are shown in the Disruption element of a journey's leg.
The 9292 Reisadvies API supports four types of disruption messages:
Fares are shown in all responses. They can be found under FareInfo. The FareInfo consists of fares that represent the entire travelling advice (Journey). It is also possible to display fare information per Leg.
FareInfo consists of a "Complete" and a "Farelegs" component. When fares are not available, for example a travelling advice with a ferry, then the element "Complete" will contain the value 'false'. In that case it is not possible to give a total fare for the advice. For the parts where it is possible to give the information, it will be shown per part of the journey.
Below an example is given of a NS train fare:
Example |
"fareInfo": { |
The amount of price units of the train is shown under “PriceUnits” of the “FareLegs”.
Here is an example of a bus journey from a travelling advice from Leeuwarden to Harlingen with the following fare information:
Example |
"fareInfo": { |
“FareLegs” within 1 Journey can be added up in the following combinations:
The elements below can also be used. These add up all the elements and will show the full and reduction price:
Please note:
We would like to point out that the presenting of reduction prices in case of different modalities needs some explanation. Qualification for reduction in the train has other conditions than the qualification for reduction in bus/tram/metro.
It is possible that there is no fare information available, because there is no OV-chip card information present (i.e., ferry information). This is indicated in <Fares> as follows:
Example |
"fares": [{ |
To determine whether the OV-chipcard is valid on a Fareleg, the tariff calculator gives a field NoChipFare to the Planner. The planner gives this back to the client with the same name. This is a boolean-field. This value is true when the OV-chipcard is not valid and it is false when it can be used.
Example |
"fareInfo": { |
The following parameter is available for displaying fare information in a Leg:
Parameter |
Description (example) |
Fare | FareInfoAndLegs |
Fare information in the Leg comprises the following components:
Component |
Description/Remarks |
BaseFareEurocents | The base fare (boarding rate) |
FareEurocents | Fare without the base fare |
Class | Class type |
Reduced | Indicates if it is a reduced fare |
MultipleLegFare | Indicates if the fare is a total price for a combination of consecutive legs |
MultipleLegNotice | A note explaining that this fare represents a combination of consecutive legs |
The following is an example of fares in a Leg:
Example |
"legFares": [{ |
The “PlannedJourneys” endpoint enables the traveller to replan a travel advice they have received. The replanning is equivalent to refreshing the information (i.e., real-time data, occupancy data, disturbances, etc.) in the travel advice.
This endpoint has one parameter:
Parameter |
Description (example) |
JourneyId | The unique identifier for a travel advice |
Please note:
- The JourneyId can be used to retrieve its associated travel advice as long as the travel advice can be recreated by the 9292 planner. Meaning, JourneyId’s can expire.
- JourneyId’s from the previous version (v3) are supported in the new version
Request:
This item is a standard feature of the 9292 Reisadvies API. By assigning the ‘FirstMile’ and or ‘LastMile’ parameter with the values ‘PrivateBicycle’,‘PrivateElectricBicycle’ or ‘PrivateMoped’ you can provide the traveller with the appropriate public transport travel advice in which he or she can use their own bicycle, electric bicycle or moped to and from a bicycle transfer point located near a train station or a bus/metro/tram stop.
The 9292 Reisadvies API also supports the use of rental bicycles and mopeds. To use rental vehicles in the first mile or last mileassign the value ‘PublicBicycle’, ‘PublicElectricBicycle’ or ‘PublicMoped’ to the ‘FirstMile’ and/or ‘LastMile’ parameters.
When requesting rental vehicles it is required to also fill-in a rental location. This is done using the “PickUpLocation” parameter. This will return a transport travel advice with extra transition-legs to and from the requested rental location.
Here's an overview of the parameters needed to have bicycles and mopeds in a travel advice:
Parameter |
Description (example) |
FirstMile | The type of transportation to use in the first mile (e.g. “PublicBicycle”) |
LastMile | The type of transportation to use in the last mile (e.g. “PublicMoped”) |
FirstMileOptions.PickUpLocation | The desired rental location to be used |
Please note:
- The 9292 planner does not take into account the actual availability of the requested rentable vehicle type
- Not all departure or arrival locations will have the requested rental modality type.
- In order to provide the traveller with a better user experience there is the option to request all possible rental modality types for a specific location by using the 9292 Locations API. By combining this information with a travel request you can ensure that the traveller receives an appropriate travel advice
Request:
It is also possible to request the inclusion of a drop-off location in a travel advice. The optional drop-off parameter is as follows:
Parameter |
Description (example) |
FirstMileOptions.IncludeVehicleDropOff | Indicates if the travel advice must include a drop-off location for the rented vehicle |
The 9292 Reisadvies API will find an appropriate location to drop-off the rented vehicle. If a drop-off is requested for the first mile of a journey then the appointed drop-off location will be within 500 metres of the Public Transportation transfer point. And if a drop-off is requested for the last mile of a journey then the appointed drop-off will be within 500 metres of the traveller’s destination.
This will result in a transport travel advice with extra transition-legs to and from the requested drop-off location.
Please note:
- Some rental vehicles must be returned to a specific location and if the renter does not comply, the rental period will not close which will lead to higher rental charges than expected.
- If a mandatory drop-off location is not within 500 metres of a transfer point or the final destination the Reisadvies API will return an error stating that no journey with a drop-off could be found.
- Use the 9292 Locaties API to determine whether or not a specific rental vehicle must be returned to a specific location.
The standard business rules for planning a journey by bicycle are:
The standard business rules for planning a journey by scooter are:
The 9292 Reisadvies API provides the option to request a last mile rental (pick-up) location and/or a vehicle drop-off point for the rented vehicle by using the following three step process:
The "LastMilePlannedJourneys” endpoint uses the following parameters:
Parameter |
Description (example) |
JourneyId | The unique identifier for a travel advice |
PickUpLocation | The desired rental location to be used |
IncludeVehicleDropOff | Indicates if the travel advice must include a drop-off location for the rented vehicle |
The following is an example of a request followed by a partial response:
Request:
Example |
{ |
The 9292 Reisadvies API supports three types of on demand transport; the "HalteTaxi”, “WaterTaxi” and "HubTaxi”. The first two types are automatically included in the travel advice when appropriate and can also be excluded from the travel advice by filling the “ExcludedTravelModes” parameter with “OnDemand” or “WithSurcharge”. The “HubTaxi” is an on-demand transport that needs to be explicitly requested by specifying “PublicTaxi” in the “FirstMile” and/or “LastMile” parameters. The traveller is also required to make a reservation online or by telephone to request the taxi pick-up.
Please note:
- The “FirstMileOptions” and “LastMileOptions” parameters do not apply when requesting a “PublicTaxi”
- The 9292 Locaties API has a “OperatorDetails” endpoint that is to be used to obtain the required HubTaxi telephone number
The ‘minimize walking distance’ option allows you to provide the traveller with an appropriate travel advice in which the walking distance of the first mile and/or the last mile is minimized.
The following parameter is available to minimize the walking distance in the travel advice:
Parameter |
Description (example) |
FirstMileOptions.LessWalking |
true |
LastMileOptions.LessWalking |
true |
By using the option to customize the travel time and speed settings used by the 9292 ReisadviesAPI you can provide the traveller with an appropriate travel advice in which he/she can specify the desired travel time and speed for the first and last mile independently.
The following parameters are available for customizing the settings in a public transport travelling advice:
Parameter |
Description (example) |
FirstMileOptions.UserSpeed |
The first mile travel speed in km/h. When omitted the standard travel speed of the selected first mile modality will be used |
FirstMileOptions.UserMaxTravelTime |
Maximum travel time in minutes for the first mile |
LastMileOptions.UserSpeed |
The last mile travel speed in km/h. When omitted the standard travel speed of the selected last mile modality will be used |
LastMileOptions.UserMaxTravelTime |
Maximum travel time in minutes for the last mile |
The business rules for the travel speed settings are as follows:
The business rules for the travel time settings are:
If there are no valid travel options based on the specified maximum travel time, the 9292 Reisadvies API will search for alternatives that do not comply with the traveller’s travel time settings.
It is possible to strictly enforce the travel time settings by using the following parameter:
Parameter |
Description (example) |
StrictTravel |
true |
By using the option ‘Occupancy information’ you can provide the traveller with an appropriate travel advice including the occupancy per vehicle and you can give an occupancy forecast for the entire journey.
The following parameters are available to add the occupancy information to the travel advice:
Parameter |
Description (example) |
ShowOccupancy |
true |
The occupancy is indicated on a scale from 0-5 in accordance with the BISON specification “Concept interface occupancy”. The occupancy can be visualized with the corresponding color or the corresponding icon.
In the following table an example is given how 9292 translates the data in her own apps and website.
BISON occupancy value |
Enumeration |
Color |
9292 icon |
Remarks |
0 |
No information |
|
No information received or occupancy unknown |
|
1 |
Empty |
|
At the NS numbers 1 and 2 will be converted to 2 |
|
2 |
Many seats available |
|
At the NS <65% of the seats on the train are taken |
|
3 |
Few seats available |
|
At the NS >65% and <100% of the seats per train are taken |
|
4 |
Standing room only |
|
At the NS >100% of the seats on the train are taken |
|
5 |
Full |
|
Only relevant for real time data. |
The icons accommodate the visually impaired by making a clear distinction between the icons.
A travel advice from Waterlooplein in Amsterdam to Stadsschouwburg in Utrecht.
The whole journey will get the indicator BUSY because 1 leg has the indicator “BUSY”.
The indicator will be aggregated to the busiest stop of the journey.
You can provide the traveller with an appropriate travel advice in which each Leg contains a corresponding route.
Use the following parameter to add route information to each leg of a travel advice:
Parameter |
Description (example) |
Route |
true |
The route information can be found under the Route element of a Leg. The Route consist of 3 elements:
Here is an example of such a route information:
Example |
"route": { |
By using the ‘unimodal’ option you can provide the traveller with an appropriate travel advice consisting of a single journey by foot, (electric) bicycle or moped from the departure location to the arrival location. The travel mode used is defined by the FirstMile parameter.
Use the following additional parameters to receive a unimodal travel advice:
Parameter |
Description (example) |
Unimodal |
true |
FirstMile |
The type of transportation to use in the first mile (e.g. “PublicBicycle”) |
FirstMileOptions.PickUpLocation |
The desired rental location to be used |
The combination of the first mile and the total distance between the departure and arrival location need to comply with one of the following criteria:
First mile |
Route type |
Max distance between departure and arrival location |
Walking |
Walk route |
≤ 1,4 km (default settings) |
Bicycle |
Bicycle route |
≤ 6,9 km (default settings) |
Electric bicycle (25km/h) |
Bicycle route |
≤ 10 km (default settings) |
Electric bicycle (45km/h) | Bicycle route | ≤ 17,5 km (default settings) |
Moped (25km/h) |
Bicycle route |
≤ 10 km (default settings) |
Moped (45km/h) | Moped route | ≤ 17,5 km (default settings) |
If the above criteria is not met, the 9292 Reisadvies API will return an error message.
This is an optional feature that can be purchased and added to the 9292 Reisadvies API at your request.
The star values and star zones are used in the so-called ‘Sterabonnementen’ subscriptions. If this functionality is activated, the 9292 Reisadvies API will calculate which monthly ticket is required for the travelling advice. This monthly ticket is no longer used everywhere in the Netherlands, thus it is only given when this monthly ticket is applicable. This is demonstrated in the following example
In this example the requested travelling advice is from Station Koog Zaandijk to Station Krommenie Assendelft where the modality train is excluded:
Request:
When there are Star zones present in the travelling advice, the response is as follows:
Example |
"starZones": [ |
When there are no Star zones present, the following is returned:
Example |
"StarZones": [] |
The Star value can be both a numeric and an alphabetic value. There are seven possible values: 1 to 6 and ‘Netabonnement’. With a value greater than 6, the value Netabonnement will be displayed, as this value is valid in the entire country for city and region transport.
It is possible that for one journey more than 1 monthly ticket is required. In that case multiple elements <FareLeg> are shown, in which the first FareLeg the tariff information shows for the total journey. After this the <FareLeg> is shown per required monthly ticket. This is shown as follows in the <Fares>:
Example |
"fareInfo": { |
This optional component can be purchased and added to the 9292 Reisadvies API upon request.
By using the CO2 option in the public transport travel advice, your users can compare how much CO2 they save per public transport journey by travelling with Public Transport.
The calculation of CO2 is based on CO2 emissions per kilometre and Well-to-Wheel (WTW) = the emissions of both the pre-use phase and the direct emissions together.
The summaries are shown below for the different modes of transport.
The CO2 values listed below originate from the website co2emissiefactoren.nl and are the initiative of SKAO, Stimular, Connekt, Milieu Centraal and the central government and were created in collaboration with various stakeholders.
Private/Shared Transportation
Category |
CO2 emissions |
Bicycle | 0 |
Electric bicycle (25km/h) | 6 |
Electric bicycle (45km/h) | 6 |
Moped (25km/h) | 17 |
Moped (45km/h) | 32 |
Small Car |
180 |
Mid-class Car |
202 |
Large Car |
236 |
Public transport
Category |
CO2 emissions |
Tram |
0 |
Bus |
103 |
Metro |
0 |
Train |
2 |
Ferry |
115 |
Taxi |
202 |
Sources consulted:
A sample travel advice with CO2 from zip code 3221AL in Hellevoetsluis to zip code 3078PE in Rotterdam:
Request:
Response:
Example |
"cO2EmissionInfo": { |
An explanation of the most relevant elements of the response above:
Elements |
Description (example) |
JourneyDistance |
measured straight line distance of the journey in kilometres |
JourneyEmission |
total CO2 emissions based on public transport in kilograms |
JourneyByModality |
List of CO2 emission of particular modalities |
This is an extra feature that can be purchased and added to the 9292 Reisadvies API at your request.
By using the functionality ‘Realtime travelling advice’ you provide the traveller with an appropriate travelling advice including delays (train, bus, metro or tram). When there are changes in time, the journey can be rescheduled, and alternatives are offered by 9292.
The following parameters are added to the 9292 Reisadvies API to display real time in the travelling advice.
Properties |
Description (example) |
ArrivalRealTime |
Actual arrival time |
DepartureRealTime |
Actual departure time |
Call.RealtimeState |
None, Offset, Cancelled |
RealTimeInfo.Cancellations |
None of Cancellations |
RealTimeInfo.Delays |
None, InternalDelay |
RealTimeInfo.Detour |
Normal |
RealTimeInfo.LudMessage |
<Text>Dit is een alternatief reisadvies.</ Text> |
The example below shows how delays are indicated. In the example both the departure time and the arrival time have changed compared to the original time.
Original departure time and arrival time are:
Example |
"departureRealtime": "2022-11-05T11:32:00.0000000Z", |
In a travelling advice for every stop the real time departure and arrival time is indicated, as is also the case for stops in-between. In the example below the bus has left the bus stop "Claudius Prinsenlaan" in Breda earlier than originally planned. The bus should have departed at 10:05h but has left the stop at 10:02h.
Example |
"calls": [{ |
When a planned journey is cancelled, a cancelled message will be sent by the public transport company. This is shown in the example below.
The sprinter (train) from Amersfoort to Zwolle is cancelled. For every station/ stop of that journey, the RealtimeState shows Cancelled.
Thus, this travelling advice is cancelled. It is considered very important to present this information to the traveller and to give an explanation.
Request:
Example |
"realtimeInfo": { |
It can occur that a transfer connection cannot be realized. For example when there is a delay in the first part of the journey. The RealtimeInfo shows a FatalDelay, the remaining output does not change.
Thus, this travelling advice is cancelled. It is considered very important to present this information to the traveller and to give an explanation.
Example |
"realtimeInfo": { |
When a public transport travelling advice is cancelled, often an alternative travelling advice is offered. It is considered very important to present this information to the traveller.
For example the journey from Kampen Zuid to Amsterdam Bijlmer Arena (sprinter train) has been cancelled. There is an Intercity (train) from Kampen Zuid to Duivendrecht followed by a transfer with the Metro to Amsterdam Bijlmer Arena.
The most important change in the response is displayed in the example below:
Example |
"realtimeInfo": { |
When the NS inserts an extra journey, this is displayed in the 9292 Reisadvies API.
In the example below an extra journey is inserted between Harderwijk and Zwolle: an extra intercity (train) with journey number 29600.
This type of travelling advice is called ‘Alternatief reisadvies’ as is shown in the Ludmessage.
It can occur that there is no Platform or Platformchange information available, as is shown in the example below. This means that 9292 has not received this information or that this information has not been processed.
Example |
… |
When a journey has an extra stop, this will be displayed as followed in the 9292 Reisadvies API:
The 9292 Reisadvies API does not indicate which additional station/stop has been added. For these stations/stops the departure/arrival platform information might not be available.
The response of a journey with an extra stop is as follows:
Example |
"realtimeInfo": { |
This feature is optional and can be added to the 9292 Reisadvies API upon request.
By using the ‘OV Prijswijzer’ option, you will provide the traveller with appropriate subscription information for the train, bus, metro or tram of their travelling advice. The retrieval of this information is done using the ProductAdvice endpoint.
For more information about the ‘OV Prijswijzer’ we refer you to our website 9292.nl. There you will find the list of subscriptions used by the ‘OV Prijswijzer’.
The ProductAdvice endpoint requires the following parameters to show the Prijswijzer API advice for a travel advice.
Parameter |
Description (example) |
JourneyId |
A travel advice’s unique identifier |
TravellerAge |
Age (number between 4 and 100) |
TravellerFrequencyPeriod |
Period (number 1 or 2) 1=week, 2=month |
TravellerFrequency |
Number of days (number between 1 and 31, dependent on TravellerFrequencyPeriode) If TravellerFrequencyPeriod = 1, then TravellerFrequency must be between 1 and 7. If TravellerFrequencyPeriod = 2, then TravellerFrequency must be between 1 and 31. |
Here is an example of a valid request with the following information:
Field |
Parameter |
JourneyId |
station-alkmaar~station-utrecht-centraal~~0~C0nHlCAAB$$HmH040~~~B~9~129~~3600215~3627006~ |
Traveller's Age |
24 |
Number of days |
3 |
Period (week) |
1 |
Request:
https://<reisadvies-api-url>/v4/ProductAdvice?JourneyId=station-alkmaar~station-utrecht-centraal~~0~C0nHlCAAB$$HmH040~~~B~9~129~~
3600215~3627006~&TravellerAge=24&TravellerFrequency=3&TravellerFrequencyPeriod=1
In the example below, we show the XML & JSON of a ProductAdvice response.
Example |
{ |
This optional feature can be added to the 9292 Reisadvies API at your request.
By using the option ‘Planning an accessible journey & Stop Accessibility’ you provide the traveler with the appropriate travel advice suited for someone with a physical disability. In addition, all travel advice (whether or not planned with accessibility) are provided with information regarding a stop's accessibility.
The following parameters are available to get an accessible public transport travel advice.
Parameter |
Description (example) |
PlanWithAccessibility |
true |
The following attributes are added to the call element:
Possible values for these attributes:
Values |
Meaning |
Accessible |
Stop is accessible |
NotAccessible |
Stop is not accessible |
Unknown |
No information available |