Skip to main content

Common Parameters

Last updated: April 1, 2026 | 7 minutes read

This guide describes common parameters and features shared by the Routing API and Isochrones API.

Transport Modes​

Both APIs accept a transport parameter to specify the mode of transportation:

ValueDescriptionRoutingIsochrones
carStandard car routing✅✅
lorryLorry / heavy goods✅✅
truckAlias for lorry✅✅
bikeBicycle routing✅✅
pedestrianWalking / hiking✅✅
publicPublic transit✅—

Route Types​

The type parameter controls the optimization goal:

ValueDescriptionRoutingIsochrones
fastestMinimize travel time✅✅ (ranges in seconds)
shortestMinimize distance✅✅ (ranges in meters)
economicOptimize energy efficiency✅✅ (ranges in Wh, e-bikes only)
scenicPrioritize scenic roads✅✅

Route Avoidance​

The avoid array lets you exclude specific road features from the computed route or isochrone:

ValueDescriptionRoutingIsochrones
highwayAvoid highways / motorways✅✅
tollAvoid toll roads✅✅
ferryAvoid ferry connections✅✅
unpavedAvoid unpaved roads✅✅
turnaroundAvoid U-turns at intermediate waypoints. Default is true for car/truck and false for bike/pedestrian/public✅✅
trafficAvoid current traffic congestions and roadblocks. If no route is possible, a solution with best-effort roadblock avoidance is returned✅✅
roadblocksAvoid only roadblocks. If no route is possible, a best-effort solution is returned✅✅
immutable_roadblocksAvoid permanent roadblocks. If no route is possible, a "waypoints access" error is returned instead of a fallback✅✅

Vehicle Specifications​

The vehicle object allows detailed configuration of vehicle characteristics. It is supported by both APIs.

Transport Profiles​

The profile field selects a detailed profile within a transport mode:

Bike profiles:

ProfileDescriptionRoutingIsochrones
roadRoad bike✅✅
crossCross / gravel bike✅✅
cityCity / urban bike (default)✅✅
mountainMountain bike✅✅

E-bike pedelec profiles:

ProfileDescriptionRoutingIsochrones
road_pedelecRoad e-bike (pedelec)✅✅
cross_pedelecCross e-bike (pedelec)✅✅
city_pedelecCity e-bike (pedelec)✅✅
mountain_pedelecMountain e-bike (pedelec)✅✅

E-bike speed pedelec profiles:

ProfileDescriptionRoutingIsochrones
road_spedelecRoad e-bike (speed pedelec)✅✅
cross_spedelecCross e-bike (speed pedelec)✅✅
city_spedelecCity e-bike (speed pedelec)✅✅
mountain_spedelecMountain e-bike (speed pedelec)✅✅

Pedestrian profiles:

ProfileDescriptionRoutingIsochrones
walkStandard walking (default)✅✅
hikeHiking✅✅

Physical Properties​

ParameterTypeDescription
massintegerVehicle mass in kg
heightintegerVehicle height in cm
lengthintegerVehicle length in cm
widthintegerVehicle width in cm
axleintegerAxle load in kg
speedfloatReference speed in m/s. For truck transport, this is treated as the vehicle max speed

These properties are used to compute routes that respect dimensional and weight restrictions on roads (e.g., low bridges, weight-limited roads).

Fuel and Electric Vehicle Properties​

ParameterTypeDescriptionRoutingIsochrones
fuelstringFuel type: electric, petrol, diesel, lpg. For electric with car/truck, EV routing is used with intermediate charging station stops✅—
batt_capacityintegerBattery capacity in Wh (for EV and e-bikes)✅—
charger_portsstring[]Available charging port types (see below)✅—
rangeintegerVehicle range in meters (currently EV only)✅—
chargeintegerKilometers charged in one hour (with battery between 10%–80%)✅—
departure_socfloatDeparture battery state of charge (0 = empty, 1 = full)✅—
destination_socfloatMinimum SoC when arriving at destination✅—
chargerArrival_socfloatMinimum SoC when arriving at a charging station✅—
chargerDeparture_socfloatMaximum SoC when leaving a charging station✅—
charger_overheadfloatOverhead time at a charging station in minutes✅—
platestringVehicle plate, used for road access restrictions based on plate mantissa✅—

Supported charger_ports values:

ValueDescription
type1Type 1 (SAE J1772) AC connector
type2Type 2 (IEC 62196) AC connector
nacsNorth American Charging Standard (Tesla)
ccs1Combined Charging System 1
ccs2Combined Charging System 2
chademoCHAdeMO DC connector
chaojiChaoJi high-power DC connector
gbt_acGB/T AC connector (China standard)
gbt_dcGB/T DC connector (China standard)

Geometry Encoding​

The geometry parameter controls how path coordinates are encoded in the response:

ValueFormat
lineStringCoordinate array [[lon, lat]] (default for Routing)
polylineGoogle encoded polyline string

Fitness Factor​

The fitness parameter (float, 0–1) tunes bike and pedestrian routing to the user's fitness level. Lower values favor flatter, easier routes; higher values allow steeper, more direct paths. Default: 0.5.

Emergency Mode​

Setting emergency to true enables emergency vehicle routing, which grants access to roads flagged as "emergency only" and ignores left/right turn restrictions.

Geofence Avoidance​

Both APIs support geofence-based route avoidance:

ParameterDescription
avoid_geofence_areasArray of geofence area tags/names to avoid
avoid_geofence_anti_areasArray of geofence anti-area tags/names to avoid

For more details on creating and managing geofences, see Geofences & Asset Monitoring.

Locale​

The locale parameter accepts an ISO 3166-1 language code (e.g., en, de, fr) to localize the result (navigation instructions in Routing, attribution text in Isochrones). Default: en.

Debug​

Setting debug to true formats the JSON response with indentation for easier human readability. Default: false.

For detailed usage and examples of route computation, see Routing API.

For calculating reachable areas from a given location, see Isochrones API.