Fleet Optimization with TollGuru API
Last updated on Apr 18, 2025 · 4 minutes
Fleet Optimization with TollGuru API
Optimizing fleet operations can save time, reduce fuel consumption, and significantly cut costs. TollGuru’s robust API offers powerful tools for fleet management. In this blog, we’ll explore two key components: the Taxi Fleet API and the State Mileage API.Taxi Fleet API
The Taxi Fleet API is a specialized service designed for taxi and ride-hailing services. It offers routes and toll costs between an origin and a destination, helping drivers choose the most cost-effective and efficient routes. The Taxi Fleet API can calculate routes and toll costs for a single vehicle or a fleet of vehicles, providing insights into the overall costs of running a fleet. One of the key features of the Taxi Fleet API is its ability to calculate taxi charges based on the distance traveled in each state, including additional fees like congestion charges. Here is an example of the data you can expect to receive – (Along with tolls):
"taxiCharges": {
"taxiFare": [
{
"state": "Texas",
"distanceTravelled": 175,
"costPerUnitMile": 0.9,
"taxiFareForDistanceTravelled": 158
},
{
"state": "Arkansas",
"distanceTravelled": 268,
"costPerUnitMile": 2,
"taxiFareForDistanceTravelled": 536
}
],
"airportCharges": [],
"congestionSurcharge": [
{
"zone": "New York Congestion Zone 1",
"charge": 2.5
}
],
"taxiSummary": {
"totalTaxiCost": 1828,
"totalTaxiFare": 1810,
"totalDistanceTravelled": 1532,
"totalExtraCharges": 2.5,
"tollCost": 15.43,
"currency": "USD",
"distanceUnit": "miles"
}
}
This data provides a comprehensive view of the total cost of a trip,
factoring in the distance traveled, the fare per state, any additional
surcharges, and the overall taxi cost.
State Mileage API
The State Mileage API calculates the distance traveled in each state for a given route. This is particularly useful for logistics and transportation companies that need to track state-based mileage for tax and reporting purposes. The API can provide state mileage information for both an origin-destination pair and a polyline endpoint. Note that when using the polyline endpoint, the traffic time data will not be included Here is an example of the data you can expect to receive from the State Mileage API (Along with tolls):
"territoryMileage": [
{
"territory": {
"name": "Texas",
"code": "Texas",
"type": "state"
},
"trafficTime": "3 h 51 m"
},
{
"territory": {
"name": "Tennessee",
"code": "Tennessee",
"type": "state"
},
"distance": {
"text": "501",
"metric": "805.8",
"value": "805802.0"
},
"trafficTime": "7 h 23 m"
}
] "distance": {
"text": "178",
"metric": "286.1",
"value": "286103.0"
},
"trafficTime": "2 h 31 m"
},
{
"territory": {
"name": "Arkansas",
"code": "Arkansas",
"type": "state"
},
"distance": {
"text": "273",
"metric": "439.8",
"value": "439838.0"
},
]
This data provides detailed information about the distance traveled and
the time taken in each state.