Routing API Returns No Toll Costs for Certain Private Bus Routes

Summary
-------

When calculating routes using the HERE Routing API v8 with transportMode=privateBus, toll costs may be missing from the response even though toll roads exist on the route and the request contains toll-related parameters.

Issue
-----

You may observe that a route response does not contain expected toll costs for bus routes in countries where tolls apply.

Example symptoms:

The route traverses tolled roads or toll infrastructure.
The return=tolls parameter is included in the request.
The response contains no toll costs or incomplete toll information.
The issue is reproducible with specific privateBus routes.

Cause
-----

The defect Routing API toll calculation logic prevents toll costs from being returned for certain privateBus requests when occupancy-related values were not explicitly provided.

Resolution
----------

A product fix was investigated by HERE Routing team to improve the handling of default request parameter values related to occupancy.

### Workaround

Until the fix is available in our environment, explicitly include the occupancy parameter in the route request.

Example:

vehicle[occupancy]=10

Adding an explicit occupancy value allows the Routing API to correctly calculate and return toll costs for the affected routes.

Validation
----------

After adding the occupancy parameter:

1. Re-submit the route request.
2. Ensure return=tolls is included.
3. Verify that toll information is returned in the route response.
4. Compare the returned toll costs with the expected toll infrastructure along the route.

Applies To
----------

HERE Routing API v8
Toll Cost Calculation
* transportMode=privateBus routes

Tags
----

Routing API v8, Toll Costs, Private Bus, Toll Calculation, Routing, TransportMode PrivateBus, Occupancy Parameter, Known Issue