Skip to main content

How are the TollGuru API transactions counted?

Last updated on Jun 9, 2026 · 2 minutes

What Is a Transaction?

A transaction is a single billable unit in TollGuru's Toll API. Each API request may consume multiple transactions depending on the complexity of your request, the routing service used, and the data processing required.

Quick Reference

Request Type Base Transactions Additional Factors
Simple route (origin → destination) 5–7 Routing provider choice
Route with waypoints 5–7+ Number of waypoints, geocoding needs, optimization
Complete route polyline Custom Contact us for pricing
GPS tracks Custom Contact us for pricing

How Transactions Are Calculated

Transaction counting depends on which endpoint you use:

1. Routes with Origin, Destination, and Waypoints

This is the most common use case. Transaction count depends on three factors:

A. Base Processing

Every route request includes these base transactions:

Component TollGuru / HERE Google Maps
Address processing (origin & destination) 2 transactions 4 transactions
Route calculation 2 transactions 2 transactions
Toll calculation 1 transaction 1 transaction
Base Total 5 transactions 7 transactions

Note: Google Maps charges 2 transactions per geocode, while TollGuru/HERE charges only 1. This results into higher base cost for Google Maps.

B. Geocoding Charges

When you provide addresses without coordinates for waypoints, additional geocoding transactions are charged:

  • TollGuru/HERE: 1 transaction per address
  • Google Maps: 2 transactions per address

C. Waypoint Processing

Additional transactions based on total waypoint count:

Number of Waypoints Extra Transactions
Up to 10 waypoints 0
10-20 waypoints 1
21–50 waypoints 2
51+ waypoints 3

D. Route Optimization

When you enable optimizeWaypoints=true,

  • +1 transaction is charged for calculating the optimal waypoint sequence

Examples with Clear Breakdowns

Example 1: Simple Route

Request: Drive from Address A to Address B (no waypoints)

Component TollGuru/HERE Google Maps
Process addresses 2 4
Calculate route 2 2
Calculate tolls 1 1
TOTAL 5 7

Example 2: Complex Route with Waypoints

Request:

  • Origin & destination (addresses)
  • 15 additional waypoints (6 are addresses, 9 have coordinates)
  • Route optimization enabled

Transaction Breakdown (TollGuru/HERE):

Component Transactions Explanation
Base processing 5 Origin/destination + routing + tolls
Geocoding 6 waypoints 6 6 addresses × 1 transaction each
Waypoint processing 1 15 waypoints = 11-20 range
Route optimization 1 optimizeWaypoints=true
TOTAL 13

Transaction Breakdown (Google Maps):

Component Transactions Explanation
Base processing 7 Origin/destination (4) + routing (2) + tolls (1)
Geocoding 6 waypoints 12 6 addresses × 2 transactions each
Waypoint processing 1 15 waypoints = 11-20 range
Route optimization 1 optimizeWaypoints=true
TOTAL 21

Related FAQs