VehicleParameters without the two things this endpoint has no parameter for:
state.heading, which it rejects with "Unknown JSON field '.vehicleHeadingInDegrees'". The
routing API takes it under that name.preferences, whose only member is chargingPreferences. Those belong to the charging-stops
endpoint, and a range has no stops to plan. A predefined model.variantId therefore needs
nothing beside it here, unlike on calculateRoute.Both stay available on calculateRoute. Everything else carries over, including the
engine-specific state variants — an electric vehicle picks between the percentage and kWh
forms.
Vehicle parameters accepted by
calculateReachableRange.