Calculate Route

A circle with a center point and a radius (in meters). The radius must be a positive integer with the maximum value of 135000.
Note: If entryPoints are provided to the routeStop, then the radius is ignored.
Example: circle(52.37245,4.89406,10000)

A location or a circle.
Examples:

• 52.37245,4.89406
• circle(52.37245,4.89406,10000)

Comma-separated list of floats.
Example: 1.23,0

To be used in the POST data only.
Please refer to the Common Routing Parameters page.

The service version number.
Value: The current value is 1.

Locations through which the route is calculated. The following constraints apply:

• At least two locations must be provided.

• The first location in the sequence defines the origin and must be a location.

• The last location in the sequence defines the destination and must be a location.

• One or more optional intermediate generalizedLocations (known as waypoints in this context) may be provided:

  • The maximum allowed number of waypoints is 150.

  • A waypoint of type location results in an extra leg in the response, a waypoint of type circle does not.

  • Circle waypoints cannot be used when computeBestOrder is true.

Values: Colon-delimited generalizedLocations, with the constraints mentioned above.

Number of desired alternative routes to be calculated. The value provided:

• Must be an integer in the range 0-5.

• Using a value greater than 0 in conjunction with computeBestOrder set to true is not allowed.

• Fewer alternative routes may be returned if either fewer alternatives exist, or the requested number of alternatives is larger than the service can calculate.

Default value: 0
Maximum value: 5

When maxAlternatives is greater than 0, allows to specify the objective of computing alternative routes: finding routes that are significantly different than the reference route, or finding routes that are better than the reference route. Possible values are:

• anyRoute: returns alternative routes that are significantly different from the reference route.

• betterRoute: only returns alternative routes that are better than the reference route, according to the given planning criteria (set by routeType). If there is a road block on the reference route, then any alternative that does not contain any blockages will be considered a better route. The summary in the route response will contain information (see the planningReason parameter) about the reason for the better alternative.

Note: The betterRoute value can only be used when reconstructing a reference route. Default value: anyRoute
Other values: betterRoute

All alternative routes returned will follow the reference route (see the POST data parameters section) from the origin point of the calculateRoute request for at least this number of meters.

• Can only be used when reconstructing a route.

• The minDeviationDistance parameter cannot be used in conjunction with arriveAt.

All alternative routes returned will follow the reference route (see the POST data parameters section) from the origin point of the calculateRoute request for at least this number of seconds.

• Can only be used when reconstructing a route.

• The minDeviationTime parameter cannot be used in conjunction with arriveAt.

Largest index in the array of supportingPoints per route or in joined arrays of supportingPoints per leg (see the POST data parameters section) for which supportingPoints[supportingPointIndexOfOrigin] lies on or before the origin point.
The Routing API uses this index as a hint to disambiguate situations where the supportingPoints in the POST data are not planar, or where they come back close to the origin at a later point in the reconstructed route. In these cases, the supportingPointIndexOfOrigin can explicitly identify if the origin is meant to be on the later part of the route, or not.

• Can only be used when reconstructing a route.

• Cannot be used in conjunction with arriveAt.

Minimum value: 0
Maximum value: Size of supportingPoints array - 1.

Re-orders the route waypoints with a fast heuristic algorithm to reduce the overall route length. Note that based on the heuristic nature of the algorithm, optimality is not guaranteed. Yields best results when used in conjunction with routeType shortest.
Possible boolean values are:

• true: compute a better order, if possible

  • Not allowed to be used in conjunction with a maxAlternatives value greater than 0.

  • Not allowed to be used in conjunction with circle waypoints.

  The response will include the reordered waypoint indices in the field optimizedWaypoints.

• false: use the locations in the given order.

  • Not allowed to be used in conjunction with routeRepresentation=none.

Specifies the representation of the set of routes provided as a response.
Possible values are:

• polyline: includes routes in the response as polylines. The polylines are returned in the points fields in the response.

• encodedPolyline: includes routes in the response in the encoded polyline format. The encoded polylines are returned in the encodedPolyline fields and their precisions in the encodedPolylinePrecision fields in the response.

• summaryOnly: as per polyline, but excluding the points fields for the routes in the response.

• none: only includes the optimized waypoint indices but does not include the routes in the response. This parameter value can only be used in conjunction with computeBestOrder=true.

Default value: polyline
Other values:

• encodedPolyline
• summaryOnly
• none

Specifies whether to return additional travel times using different types of traffic information (none, historic, live) as well as the default best-estimate travel time.
Possible values are:

• none: do not compute additional travel times.

• all: compute travel times for all types of traffic information, specifying all results in the fields:

  • noTrafficTravelTimeInSeconds
  • historicTrafficTravelTimeInSeconds
  • liveTrafficIncidentsTravelTimeInSeconds

  being included in the summaries in the route response.

Default value: none
Other value: all

The directional heading of the vehicle, in degrees starting at true North and continuing in a clockwise direction.

• North is 0 degrees.
• East is 90 degrees.
• South is 180 degrees.
• West is 270 degrees.

Maximum value: 359
Other values: 0-359

Specifies which of the section types is reported in the route response. sectionType can be specified multiple times (e.g., ...&sectionType=tollRoad&sectionType=tollVignette&...).
Possible values are:

• carTrain: sections of the route that are car trains.

• ferry: sections of the route that are ferries.

• tunnel: sections of the route that are tunnels.

• motorway: sections of the route that are motorways.

• pedestrian: sections of the route that are only suited for pedestrians.

• tollRoad: sections of the route that require a toll to be paid.

• toll: sections of the route with the usage-based toll collection system (i.e., distance-based tolls, toll bridges and tunnels, weight-based tolls).

• tollVignette: sections of the route that require a toll vignette to be present.

• country: sections indicating which countries the route is in.

• travelMode: sections in relation to the request parameter travelMode.

• traffic: sections of the route that contain traffic information.

• carpool: sections of the route that require use of carpool (HOV/High Occupancy Vehicle) lanes.

• urban: sections of the route that are located within urban areas.

• unpaved: sections of the route that are unpaved.

• lowEmissionZone: sections of the route that are located within low-emission zones.

• roadShields: sections with road shield information. A road shield section contains:

  • roadShieldReferences: A list of references for the road shields (roadShieldReference). Please refer to the structure of a road shield reference object for further information.

  Notes: If this section type is requested, calculateRouteResponse contains the additional field roadShieldAtlasReference.
  Please refer to the notes about the road shield atlas for further information.
  The road shields are only available in these supported countries.

• speedLimit: Sections with legal speed limit information. maxSpeedLimitInKmh: The maximum legal speed limit in kilometers/hour. This can be time-dependent and/or vehicle-dependent.

  • Time can be set by either the departAt or arriveAt request parameter. In the case of a time-dependent speed limit, the section will contain the speed limit effective at the time the planned route would enter this section.

  • Vehicle information can be set by adjusting the travelMode and vehicle* request parameters.

  • Requesting legal speed limits is only valid if travelMode is adjusted to be a motorized vehicle ( car, truck, taxi, bus, van, or motorcycle).

• handsFreeDriving: Sections of the route applicable for hands-free driving.

  • Note: If this parameter is set, then the parameter handsFreeDrivingCapability must also be set.

  • Note: If this parameter is set, and the parameter prefer=handsFreeDriving is not set, the response may contain hands-free sections, but the route will not prefer stretches that allow hands-free driving.

Default value: travelMode
Other values:

• carTrain
• country
• ferry
• motorway
• pedestrian
• tollRoad
• toll
• tollVignette
• traffic
• tunnel
• carpool
• urban
• unpaved
• lowEmissionZone
• roadShields
• speedLimit
• handsFreeDriving

Include toll payment types in the toll section. If a toll section has different toll payment types in its subsections, this toll section splits into multiple toll sections with the toll payment types. Possible values:

• all Include toll payment types in the toll section.
• none Do not include toll payment types in the toll section.

The value all must be used together with sectionType=toll.

Default value: none

Specifies the hands-free driving capability of the vehicle. The available hands-free driving data is matched against handsFreeDrivingCapability in order to filter for the subset of data that applies to the specific capability of the vehicle.

• When this parameter is set, prefer=handsFreeDriving or sectionType=handsFreeDriving (or both) must be set.

• The value must match the regular expression '^[a-zA-Z0-9-:]{1,100}$'.

Specifies a list of margins in kilowatt-hours (kWh) for computing reachableRouteOffsets.

• Can only be used when all of constantSpeedConsumptionInkWhPerHundredkm, maxChargeInkWh, and currentChargeInkWh are specified.

• The items in the list must be in strictly decreasing order.
• The list is restricted to exactly one item.

Minimum value: 0
Maximum value: 0

Specifies the extended representation of the set of routes provided as a response. <extendedRouteRepresentation> can be specified multiple times (e.g., ...&extendedRouteRepresentation=distance&extendedRouteRepresentation=travelTime&extendedRouteRepresentation=consumption&... ). <extendedRouteRepresentation> can only be specified when contentType is json and routeRepresentation is polyline or encodedPolyline.
Possible values are:

• distance: Includes distances to route polyline points in the response.

• travelTime: Includes travel times to route polyline points in the response.

• consumption: Includes consumption values dependent on the vehicleEngineType to route polyline points in the response.

  • Can only be used when the vehicleEngineType is set to electric and the constantSpeedConsumptionInkWhPerHundredkm is specified.

• distance
• travelTime
• consumption

An array of point objects, to be used as input for route reconstruction.
supportingPoints and encodedPolyline are alternative representation formats and cannot be used simultaneously. See the Route geometry representation formats section for further information.

A string in the encoded polyline format, representing the array of points to be used as input for route reconstruction.
The precision used to encode the polyline must be set in the encodedPolylinePrecision field.
supportingPoints and encodedPolyline are alternative representation formats and cannot be used simultaneously. See the Route geometry representation formats section for further information.

The precision used to encode the polyline in the encodedPolyline field.
Must be 5 or 7.
Must be paired with encodedPolyline.

An array of pointWaypoint objects, to be used to represent waypoints when reconstructing a route.

• If specified, the array must not be empty.

• If specified, all location waypoints in the routePlanningLocations will be ignored.

Contains one waypointSourceType and one supportingPointIndex object.

Denotes the source of the waypoint. Possible values:

• USER_DEFINED: a waypoint that was explicitly defined by the user.

An index into the supportingPoints array that denotes the location of the waypoint on the reference route.

• Must be inside supportingPoints array boundaries.

An array of reassessmentParameterSet objects, to be used as input for route reassessment.

• Route reassessment provides information on how some properties of the route would be different with different input values (note that reassessment does not affect the shape of the route). For example, route reassessment can be used to quantify the impact of air conditioning use on total power consumption.

• If specified, the array must contain exactly one entry.

• A reassessmentParameterSet object is a set of parameters used together to reassess the planned route. Such an object must contain at least one parameter; currently the only supported parameter is auxiliaryPowerInkW.

An array of objects with the parameters for the computation of each leg. If the parameter is such that it is available for use in the query parameters, then its simultaneous use in the query parameters and in the POST data is prohibited, and such a request will be returned with an error.
If the legs field is present in the POST data, then the number of elements in the array must be equal to the number of waypoints + 1.
It is prohibited to use per leg parameters together with circle waypoints.
If there is no need to specify any parameters for some leg, then an empty object must be specified.
It may contain the following fields:

• routeType: specifies the type of optimization used when calculating the leg. For the details, please see the Common Routing Parameters page.
  Default value: fastest

• hilliness: specifies the degree of hilliness for a thrilling route. For the details, please see the Common Routing Parameters page.
  Default value: normal

• windingness: specifies the level of turns for a thrilling route. For the details, please see the Common Routing Parameters page.
  Default value: normal

• routeStop: an object of RouteStop type with additional parameters for the stop at the end of the current leg. It must be omitted if not needed.

• supportingPoints: An array of point objects, to be used as input for leg reconstruction.
  supportingPoints cannot be used for the entire route and per leg simultaneously.
  supportingPoints per leg cannot be used in conjunction with pointWaypoints.
  When using minDeviationTime, minDeviationDistance, or supportingPointIndexOfOrigin, all legs must have non-empty supporting points.
  A supportingPoints array must cover the whole leg, and the itinerary points (an origin, a destination, or a waypoint) must be located at (or very near to) the first and last points.
  supportingPoints must be omitted if not needed.
  When supportingPoints is specified, it must have at least 2 elements.
  supportingPoints and encodedPolyline are alternative representation formats and cannot be used simultaneously. See the Route geometry representation formats section for further information.

• encodedPolyline: A string in the encoded polyline format, representing the array of points to be used as input for leg reconstruction.
  The precision used to encode the polyline must be set in the encodedPolylinePrecision field.
  encodedPolyline must be omitted if not needed.
  supportingPoints and encodedPolyline are alternative representation formats and cannot be used simultaneously. See the Route geometry representation formats section for further information.

• encodedPolylinePrecision: The precision used to encode the polyline in the encodedPolyline field.
  Must be 5 or 7.
  Must be paired with encodedPolyline.
  Must be omitted if not needed.

For an example that uses the legs field, please see the POST curl command examples section.

Specifies the waiting time at route stops (including charging time). It must be 0 in the last leg (the destination).
Default value: 0

Specifies the entry points for the stop at the end of the current leg. The route to the stop is calculated based on these entry points. Entries with the same location are not allowed.

Latitude of the entry point. Required.

Longitude of the entry point. Required.

The request may return more than one route.
Each object has at least a summary field and a legs field. It may contain other fields depending on the request parameters.

The summary of a route, or of a route leg.
The summary object may be extended with new fields in the future; clients should ignore fields they do not recognize.

• Included if reassessmentParameterSets is specified.

• Each object in the array corresponds to the entry with the same index in reassessmentParameterSets (see the POST data parameters) and contains the results of a reassessment using the corresponding reassessmentParameterSet.

• The objects describe particular aspects of the route as a whole. Their values may differ from those reported in the route summary.

• If the reassessmentParameterSet contains auxiliaryPowerInkW, then the corresponding object may contain the following fields (see individual field descriptions for details):

  • batteryConsumptionInkWh
  • reachableRouteOffsets

• The objects in this array may be extended with new fields in the future; clients should ignore fields they do not recognize.

A description of a part of a route, comprised of an array of points.

• Contains the summary field and may contain the points, encodedPolyline, and encodedPolylinePrecision fields.

• Each additional waypoint provided in the request will result in an additional leg in the returned route.

Each object in the array is a location on the surface of the globe defined by its latitude and longitude fields.
points and encodedPolyline are alternative representation formats. See the Route geometry representation formats section for further information.

A string in the encoded polyline format, representing the array of points describing a part of a route.
The precision used to encode the polyline is set in the encodedPolylinePrecision field. The precision reflects the selected coordinatePrecision, i.e., the precision is 5 with default, and 7 with full.
points and encodedPolyline are alternative representation formats. See the Route geometry representation formats section for further information.

The precision used to encode the polyline in the encodedPolyline field.

This array is available inside routeobjects.

• Contains one or more section objects.

• The structure of section objects is given below.

Index of the first point (offset 0) in the route this section applies to (only included for a routeRepresentation polyline).

Index of the last point (offset 0) in the route this section applies to (only included for a routeRepresentation polyline).

A 3-character ISO 3166-1 alpha-3 country code.

Type of the incident.

• Can currently be JAM, ROAD_WORK, ROAD_CLOSURE, or OTHER.

• See the tec field for detailed information.

The effective speed of the incident in km/h, averaged over its entire length.

The magnitude of delay caused by the incident.
Possible values:

• 0: unknown

• 1: minor

• 2: moderate

• 3: major

• 4: undefined, used for road closures and other indefinite delays

These values correspond to the values of the response field magnitudeOfDelay

Details of the traffic event. It uses the definitions in the TPEG2-TEC standard. It can contain the effectCode and causes fields.
A selection of TPEG2-TEC causes can be found in the Terms and definitions of Safety related message sets.

The effect on the traffic flow. Contains a value in the tec001:EffectCode table, as defined in the TPEG2-TEC standard. Can be used to color-code traffic events according to severity.

Each object in the array describes one cause of the traffic event.

• It can contain mainCauseCode and subCauseCode fields.

• It can be used to define iconography and descriptions.

The main cause of the traffic event. Contains a value in the tec002:CauseCode table, as defined in the TPEG2-TEC standard.
A selection of TPEG2-TEC causes can be found in the Terms and definitions of Safety related message sets.

The sub-cause of the traffic event. Contains a value in the sub cause table defined by the mainCauseCode, as defined in the TPEG2-TEC standard.
A selection of TPEG2-TEC causes can be found in the Terms and definitions of Safety related message sets.

The estimated travel time in seconds. Note that even when traffic=false, travelTimeInSeconds still includes the delay due to traffic.

The delay in seconds compared to free-flow conditions according to real-time traffic information.

The portion of the route or leg, expressed in meters, that is affected by traffic events which cause the delay.

The estimated travel time in seconds calculated as if there are no delays on the route due to traffic conditions (e.g., congestion). Included if requested using the computeTravelTimeFor parameter.

The estimated travel time in seconds calculated using time-dependent historic traffic data. Included if requested using the computeTravelTimeFor parameter.

The estimated travel time in seconds calculated using real-time speed data. Included if requested using the computeTravelTimeFor parameter.

The distance (in meters) from the origin point of the calculateRoute request to the first point where this route forks off from the reference route.

• If the route is identical to the reference route, then this field is set to the length of the route.

• Included in all alternative (but not reference) route summary fields.

The travel time (in seconds) from the origin point of the calculateRoute request to the first point where this route forks off from the reference route.

• If the route is identical to the reference route, then this field is set to the estimated travel time of the route.

• Included in all alternative (but not reference) route summary fields.

The coordinates of the first point following the origin point of the calculateRoute request where this route forks off from the reference route.

• If the route is identical to the reference route, then this field is set to the coordinates of the last point on the route.

• Included in all alternative (but not reference) route summary fields.

The estimated fuel consumption in liters using the Combustion Consumption Model. Included if:

• The vehicleEngineType is set to combustion.

• The constantSpeedConsumptionInLitersPerHundredkm is specified.

• The value will be non-negative (i.e., positive).

The estimated electric energy consumption in kilowatt hours (kWh) using the Electric Consumption Model.

• Included if:

  • vehicleEngineType is set to electric.

  • constantSpeedConsumptionInkWhPerHundredkm is specified.

• The value of batteryConsumptionInkWh includes the recuperated electric energy and can therefore be negative (which indicates gaining energy).

• If both maxChargeInkWh and currentChargeInkWh are specified, recuperation will be capped to ensure that the battery charge level never exceeds maxChargeInkWh.

• If neither maxChargeInkWh nor currentChargeInkWh are specified, unconstrained recuperation is assumed in the consumption calculation.

This field is included if chargeMarginsInkWh is specified. It is not present in the leg summary field. Each object in the array corresponds to an entry in chargeMarginsInkWh, and describes the reachable point on the route with respect to the charge margin specified there. Effectively, the farthest the vehicle can go on the route on its current charge, without depleting the battery beyond the specified margin.

• Objects in the array contain the following fields:

  • chargeMarginInkWh: the charge margin this reachable point is calculated for.

  • point: location of the reachable point defined as a latitude longitude pair.

  • pointIndex: largest index in the polyline of the route for which points[pointIndex] lies on or before point.

  • routeOffsetInMeters: the distance from the start of the route to the reachable point.

• Note that:

  • If currentChargeInkWh is less than or equal to chargeMarginInkWh, routeOffsetInMeters is zero.

  • routeOffsetInMeters is at most lengthInMeters.

  • Charging stops are ignored in the computation so that e.g., live traffic is used as if driving past any charging station.

A description of an optimized sequence of waypoints. It shows the index from the user-provided waypoint sequence for the original and optimized list. For instance, a response:

1{
2  "optimizedWaypoints": [
3    {
4      "providedIndex": 0,
5      "optimizedIndex": 1
6    },
7    {
8      "providedIndex": 1,
9      "optimizedIndex": 2
10    },
11    {
12      "providedIndex": 2,
13      "optimizedIndex": 0
14    }
15  ]
16}

means that:

• The original sequence is [0, 1, 2].

• The optimized sequence is [1, 2, 0].

Since the index starts by 0 the original is "first, second, third", while the optimized is "second, third, first".

The estimated departure time for the route or leg. Specified as a dateTime.

The estimated arrival time for the route or leg. Specified as a dateTime.

Each object in the array represents an effective parameter or a data used when calling the Calculate Route API. Each object has fields key and value both containing a string describing the input and its value.

The original HTTP status code as listed in the response codes (note: included for content type jsonp only).

The reason for a better route proposal. Can currently be:

• Blockage in case the reference route contains road blockages. The returned value is implementation-defined in case both reasons for a better proposal are applicable to the same route.

• Better_Proposal in case the alternative type is better than the reference route, according to the given planning criteria (set by routeType).

This field is included in the response only if the route is requested with alternativeType=betterRoute. This field is not present in the leg summary field.

This field is included if extendedRouteRepresentation is used.

• It always contains entries for the first and the last point in the route.

• For any pair of consecutive entries in the progress array, progress for pointIndex values that are not explicitly present and are enclosed by said pair, can be linearly interpolated by summing up straight line distances of the leg points.

• The Haversine formula is precise enough to compute such distances.

A progress point object may contain the following members:

• pointIndex: index of the point (offset 0) in the route this object applies to.

• distanceInMeters: distance (in meters) from the start of the route to this point. This field is included if the extendedRouteRepresentation value distance is used.

• travelTimeInSeconds: travel time (in seconds) from the start of the route to this point. This field is included if the extendedRouteRepresentation value travelTime is used.

• batteryConsumptionInkWh: electric energy consumption (in kilowatt hours) from the start of the route to this point. This field is included if the extendedRouteRepresentation value consumption is used and the vehicleEngineType is set to electric. See also the batteryConsumptionInkWh in summary section.

The index of the waypoint at the end of the leg that corresponds to:

• The index of this waypoint in the list of waypoints from the routePlanningLocations base path parameter in the request (the first waypoint has an index equal to 0).

• The index of this waypoint in the pointWaypoints field when reconstructing a route.

This field is not provided if the end of the leg corresponds to the destination or to a new charging waypoint that is not present in the request.

Contains the value of pauseTimeInSeconds, if it was specified for the corresponding leg. This field is not present in the route summary field.

Identifies the entry point that was used for the route at the end of the leg.
This index corresponds to the position of this entry point in the list of entry points within the respective leg.
The first entry point has an index equal to 0. This field is only present if the leg had entryPoints in the request.

The base URL of the Road Shields service to fetch the road shield atlas and metadata resources.
Currently available resources are:

• sprite.png
• sprite.json

We recommend to cache the sprite atlas (sprite.png) and metadata (sprite.json) as it changes infrequently and is large compared to a typical road shield description.
Please refer to the Road Shield service for further information. The returned road shield references correspond to the asset names in the Road Shield service.

The speed in km/h for the hands-free section.

Contains the response section type.

• The COUNTRY sections span between country border crossings from the departure, or to the destination.

  • The section additionally contains countryCode.

  • If the route has disjointed parts in the same country, there will be several sections with the same countryCode.

  • If no country can be assigned to a part of the route, as for example in international waters, there may be no country section for this part.

• When requested using includeTollPaymentTypes, a TOLL section optionally contains tollPaymentTypes.

• A TOLL_VIGNETTE section additionally contains a countryCode since toll vignettes are often specific to a country.

• A TRAFFIC section may additionally contain any of the following: simpleCategory, effectiveSpeedInKmh, delayInSeconds, magnitudeOfDelay, tec.

• TRAVEL_MODE sections cover the whole route. Each section's travel mode is reported in travelMode .

• CARPOOL sections contain parts of the route that are only open to HOV (high-occupancy vehicles) at the time of traversal. Roads with at least one unrestricted lane are not part of a CARPOOL section.

• ROAD_SHIELDS sections contain an array of roadShieldReference objects. Please refer to the structure of a road shield reference object for further information.

• A HANDS_FREE_DRIVING section additionally contains the field: handsFreeDrivingSpeedInKmh.
  Note: If handsFreeDriving sections are requested, then handsFreeDrivingCapability must also be set.

This field is either set to the value given to the request parameter travelMode, if this travel mode is possible, or to other which indicates that the given mode of transport is not possible in this section. This field can only be used within sections of type TRAVEL_MODE.

The tollPaymentTypes array appears in toll sections if includeTollPaymentTypes=all. Each element of tollPaymentTypes represents a toll payment type. This field can only be used within sections of type TOLL.

Possible toll payment types are:

• CASH_COINS_AND_BILLS: Cash can be used including coins and bills.

• CASH_BILLS_ONLY: Cash can be used, but bills only, e.g., 10 euros.

• CASH_COINS_ONLY: Cash can be used, but coins only, e.g., 20 cents.

• CASH_EXACT_CHANGE: Cash is used but the exact amount must be provided.

• CREDIT_CARD: Credit cards are accepted.

• DEBIT_CARD: Bank/debit cards are accepted.

• TRAVEL_CARD: Travel cards are accepted.

• ETC: Electronic toll collect either via camera or transponder.

• ETC_TRANSPONDER: Electronic toll collect via transponder.

• ETC_VIDEO_CAMERA: Electronic toll collect via camera.

• SUBSCRIPTION: Toll collect based on subscription.

This object provides a representation of the error message. It contains a code and a message field.

The original HTTP status code as listed in response codes (included for content type jsonp only).

This object describes a single road shield reference. It contains the following fields: