TollTally Route Polyline to Tolls API
Each polyline submitted to TollTally API (up to 300 miles in length) is counted as one billable API transaction.
For polylines exceeding 300 miles, the input is automatically segmented into multiple requests of up to 300 miles each, with billing applied accordingly on a per-segment basis.
TollTally GPS Tracks to Tolls API
Each GPS track submitted to TollTally API (up to 300 miles in length) is counted as two billable API transactions:
(1) one transaction for map-matching to generate an accurate logical route, and
(2) one transaction for computing toll costs along that route.
For GPS tracks exceeding 300 miles, the input is automatically segmented into multiple requests of up to 300 miles each, with billing applied accordingly on a per-segment basis.
Monthly volume tiers
Billing for API usage is tiered on a monthly basis, following a stair-stepped pricing model. Monthly API transaction volume determines the applicable per-transaction rate, as outlined in the TollTally subscription pricing in MapUp dashboard.
Each tier applies a fixed rate to the number of transactions that fall within that tier. Higher volumes result in progressively lower unit costs.
How are API transactions counted?
API transaction counts vary by endpoint and are based on route distance, with special cases for certain parameters and errors. Here's how it works:
| Route Length | GPS Tracks (CSV Upload) | Polyline Map Matching | Complete Polyline |
|---|---|---|---|
| ≤300 miles | 2 transactions | 2 transactions | 1 transaction |
| 301-1000 miles | 4 transactions | 4 transactions | 2 transactions |
| >1000 miles | 6 transactions | 6 transactions | 3 transactions |
Important Notes
- Any input or routing errors count as 1 transaction.
- Refer to the full Error Guide for error codes and troubleshooting.
Understanding how transactions are counted helps you better estimate your costs and optimize your API usage.