How are the Toll API transactions counted

Last updated on Sep 2, 2025 · 2 minutes

Transactions are counted differently based on the endpoints used:

1. Tolls between origin, destination, and waypoints:

Transaction calculation depends on the routing service provider (serviceProvider) specified in your request (tollguru / here / gmaps). Geocoding is performed when you provide addresses without latitude/longitude coordinates for waypoints. Each geocoding counts as 1 transaction for tollguru, here, and 2 transactions for gmaps. Additional transactions are added based on the total number of waypoints (see “Waypoint processing”) and whether route optimization (optimizeWaypoints) is enabled in the request.

Waypoint processing transactions:
  • Up to 10 waypoints – No extra transactions
  • 10-20 waypoints – 1 transaction
  • 20-50 waypoints – 2 transactions
  • 50+ waypoints – 3 transactions

Transaction breakdown examples:

Example 1 – Simple route (origin to destination):

  • 2 transactions for processing from and to addresses for tollguru / here, 4 for gmaps
  • 2 transactions for route calculation
  • 1 transaction for toll calculation

Total for tollguru / here: 5 transactions

Total for gmaps: 7 transactions

Example 2 – Route with from / to addresses and 15 additional waypoints (6 / 15 waypoints require geocoding), route optimization enabled (optimizeWaypoints=true):

  • 5 base transactions for tollguru / here, or 7 base transactions for gmaps (similar to Example 1)
  • 6 transactions for geocoding 6 waypoint addresses, doubled for gmaps (12 transactions).
  • 1 transaction for processing up to 20 waypoints
  • 1 transaction for route optimization.

Total for tollguru / here: 13 transactions

Total for gmaps: 21 transactions

2. TollTally – Complete route polyline from a mapping service:

Please reach out to learn more about transaction charges for this endpoint.

3. TollTally – GPS Tracks to Toll: 

Please reach out to learn more about transaction charges for this endpoint.

Note: One transaction will be charged for every request made with input errors.

Related FAQs