Mode of transportation. driving and walking are supported.

String of format {longitude},{latitude};{longitude},{latitude}[;{longitude},{latitude} ...] or polyline({polyline}) or polyline6({polyline6}).
You can send up to a maximum of 25 coordinate pairs per request (except Nearest API where coordinates only supports a single {longitude},{latitude} entry)

Limits the search to segments with given bearing in degrees towards true north in clockwise direction. List of positive integer pairs separated by semi-colon and bearings array should be equal to length of coordinate array. Accepted Value :- {bearing};{bearing}[;{bearing} ...] Each {bearing} follows the following format: {value},{range} integer 0 .. 360,integer 0 .. 180

Limits the search to given radius in meters Radiuses array length should be same as coordinates array, each value separated by semi-colon. Accepted Value - {radius};{radius}[;{radius} ...] Each {radius} has following format: double >= 0 or unlimited (default)

Hint from previous request to derive position in street network. Accepted value: {hint};{hint}[;{hint} ...]

Returned route steps for each route leg. Accepted value: true, false (default)

Returns additional metadata for each coordinate along the route geometry. Accepted value: true, false (default), nodes, distance, duration, datasources, weight, speed

Returned route geometry format (influences overview and per step). Accepted value: polyline (default), polyline6, geojson

Add overview geometry either full, simplified according to highest zoom level it could be display on, or not at all. Accepted value: simplified (default), full, false

Forces the route to keep going straight at waypoints constraining uturns there even if it would be faster. Accepted value: default (default), true, false. Default value depends on the profile.

Treats input coordinates indicated by given indices as waypoints in returned Match object. Default is to treat all input coordinates as waypoints. {index};{index};{index}... ]