Enterprise Toll SDK
Power your product with live Route, Toll & Fuel interactions.
Integrate real-time toll calculations, fuel expenses, and cost-optimized route intelligence directly into your apps or private cloud infrastructure.
Loved by Developers & Logistic Leaders at:
Use cases
One SDK, three jobs your team is already doing by hand.
01
Quote a journey before it starts
Price a route for a specific vehicle, including fuel, so the number you give a customer holds up when the invoice arrives.
02
Choose cheapest, fastest, or optimal
Run a trade-off analysis across candidate routes for the exact vehicle configuration rather than assuming one fixed path.
03
Reconcile what was actually driven
Feed raw telematics into snap-to-roads matching and get the exact tolls incurred, so reimbursements match reality.
Quickstart
Any language. Any stack. Live in an afternoon.
The API is language-agnostic HTTP. Deploy with Terraform, send your first request, and read the toll back.
post /origin-destination-waypoints
{ "from": { "lat": 36.61596, "lng": -121.93112 }, "to": { "lat": 36.59951, "lng": -121.96013 }, "waypoints": [ { "lat": 36.65984, "lng": -121.94456 }, { "lat": 36.58961, "lng": -121.94980 } ], "vehicle": { "type": "2AxlesAuto" }, "departure_time": "2023-06-15T17:36:34", "fuelOptions": { "fuelCost": { "value": 3.85, "currency": "USD", "units": "$/gallon" }, "fuelEfficiency": { "city": 23.4, "hwy": 30, "units": "MPG" } }}Infra setup guide
Terraform scripts and step-by-step cloud deployment in the MapUp-SDK-Infra-Setup-Guide.
Read GuideSample requests
Region-specific test cases supplied as JSON files, ready to fire at your deployment.
Get SamplesSupport
Questions on integrating, vehicle profiles, or coverage? Go straight to the API team.
Contact UsBuilt to sit inside your infrastructure, not beside it.
Self-hosted deployment, tunable vehicle profiles, and error responses precise enough to debug from a log line.
Complete vehicle customization
Type, axle count, height, weight, length, emission category and occupancy. Each one can change the toll class on the same stretch of road. Units in meters or feet, tonnes or pounds.
Reliability
Standard HTTP conventions throughout — 2xx success, 4xx for input errors, 5xx for server errors. Every failure names the field and the accepted values.
Multi-currency and multi-unit
Fuel cost in USD, AUD and more; efficiency in MPG or L/100km; separate city and highway figures.
Deploys into your own cloud
Infrastructure is provisioned with Terraform scripts, so the SDK runs inside your account and your network boundary. Route data never crosses into a vendor environment.
Frequently Asked Questions
The TollGuru SDK is a containerized developer toolkit that allows enterprise businesses to host and run TollGuru's toll and fuel cost calculation engine directly within their own cloud infrastructure (such as AWS), rather than sending data out to the public TollGuru REST API.
The SDK is designed for enterprise users who require ultra-low latency, process massively high transaction volumes, or have strict data privacy and compliance requirements. Because the SDK is deployed in your own Virtual Private Cloud (VPC), your proprietary routing and GPS data never leaves your internal network.
The SDK is deployed using Docker containers orchestrated via Kubernetes. MapUp provides setup configurations (Helm charts/YAMLs) to deploy the necessary pods and services. Once deployed, it provisions an internal Load Balancer, providing a custom BASE_URL that your internal applications use to make requests.
While the primary documentation and comprehensive setup guides focus on AWS Cloud (using Amazon EKS or Fargate), the containerized nature of the SDK means it can be deployed on any major cloud provider that supports Kubernetes, such as Google Cloud Platform (GCP) or Microsoft Azure.
MapUp provides configurations to set up dedicated analysis dashboards. By deploying Prometheus and Grafana within your Kubernetes cluster (typically in a custom namespace like tollguru-sdk), you can continuously monitor pod health, service status, latency, and request throughput.
After deployment, you can validate the SDK manually using tools like Postman by sending a POST request to your newly generated internal BASE_URL. MapUp also provides shell scripts (e.g., run-requests.sh) to perform load testing, allowing you to verify that your Horizontal Pod Autoscalers (HPA) trigger correctly under heavy traffic.
According to the Toll SDK troubleshooting runbook, these errors usually indicate resource constraints within your cloud environment (such as AWS Fargate CPU/memory limits being hit) or load balancer timeout settings that are too short for processing massive polyline requests. You will need to adjust your pod resource allocation or auto-scaling rules.
An INPUT_ERROR often occurs if your request payload contains duplicate timestamps or improperly formatted coordinates. A ROUTING_ERROR (such as "Location not found" or "Pair not found") typically means there are gaps in your polyline or you failed to provide both the entry and exit points required to calculate tolls on a closed ticket system.
You manage SDK security natively through your cloud provider. For AWS, this involves configuring strict Security Groups, deploying the Kubernetes worker nodes in private subnets, and implementing HTTPS/SSL certificates on your internal Load Balancer to encrypt all traffic interacting with the SDK.
Yes, the SDK mirrors the robust capabilities of the public API. You can pass highly specific, URI-encoded vehicle objects in your requests, defining attributes like vehicle type (e.g., 5AxlesTruck), height, weight, number of axles, and region-specific metrics like European CO2 emission classes.
Ready to integrate
Toll Intelligence?
Get started with TollGuru Toll Calculator or Toll API or Cloud Services.