Tolls

This page documents the toll request options and toll response fields for all routing endpoints. See each endpoint's documentation for all other request parameters and response fields.

• Route: GET, POST
• Alternate Routes: GET, POST
• Optimized Route: GET, POST

These endpoints can return toll information and calculate a toll cost based on your available payment methods.
Setting tollCost=true will then include a tollCost: number in the response as the total expected tolls to be paid along the route.
By providing tollPaymentMethods as a list of the payment methods available to you, tollCost is computed with the cheapest eligible fare at each toll.
Without tollPaymentMethods, the default remains to use the most expensive fare.
Setting tollSummary=true opts into the response having tollSummary, which includes the list of all tolls and their fares along the route.

Request Parameters

All toll data requires tollCost=true. The tollSummary and tollPaymentMethods options refine what is returned but do nothing on their own.

Parameter	Description	Required
tollCost Boolean	Set to true to return toll data. Returns tollCost as the total expected cost of all tolls passed along the route. See the tollCost parameter on the Route GET page for additional information.	Yes (for toll data)
tollSummary Boolean	Returns a tollSummary object in the response that lists every toll on the route along with its available fares. Default: false	No
tollPaymentMethods String collection	The methods you possess to pay a toll, improving fare selection when totalling tollCost. See Payment Methods for the accepted values. Default: empty (most expensive fare at each toll).	No

Vehicle class

Toll fares can vary by vehicle class. See the Truck Routing reference for how to provide vehicle specifications for an improved estimate. Otherwise a typical 2 axle car is assumed.

Example

?tollCost=true&tollSummary=true&tollPaymentMethods=EZPASS,TXTAG,CASH,PLATE

"options": {
  "tollCost": true,
  "tollSummary": true,
  "tollPaymentMethods": ["EZPASS", "TXTAG", "CASH", "PLATE"]
}

Payment Methods

The accuracy of tollCost can be improved by providing tollPaymentMethods, which declares which payment methods you possess. Common case is to list your toll transponders to access their cheaper fares. Routing is unaffected by the presence or absence of any payment methods.

Value	Description
CASH	Pay at a booth with cash.
CARD	Credit or debit card at a booth.
PLATE	License plate reader which sends a bill to the registered address of the vehicle.
TRANSPONDER	Wildcard meaning you carry every transponder, so there is no need to name each one. Uses the cheapest fare at every toll.
named transponders	Any number of the named transponder systems.

Named transponder systems

Value	Coverage
EPASS	Florida, Central Florida Expressway
EXPRESSTOLL	Colorado, E-470 and Northwest Parkway
EZPASS	19 states, Northeast and Midwest
EZTAG	Texas, Houston
FASTRAK	California
GEAUXPASS	Louisiana
GOODTOGO	Washington
IPASS	Illinois
KTAG	Kansas
LEEWAY	Florida, Lee County bridges
MACPASS	Michigan, Mackinac Bridge
NCQUICKPASS	North Carolina
NEXPRESS	Detroit-Windsor Tunnel
PALMETTOPASS	South Carolina, Southern Connector
PASE	Mexico, federal highways
PEACHPASS	Georgia, Atlanta express lanes
PIKEPASS	Oklahoma
RIVERLINK	Kentucky and Indiana, Louisville bridges
SUNPASS	Florida
TELEVIA	Mexico City urban tollways
TOLLTAG	Texas, Dallas-Fort Worth
TXTAG	Texas statewide
VIAPASS	Mexico

Response

Route Response Fields

Refer to the Route Response Fields for a full list of available fields. The following fields are specific to tolls.

Response Field	Description
tollCost	The aggregate projected cost of tolls for the entire route in USD, rounded to two decimals. Returned when tollCost=true. By default each toll is priced at its most expensive fare. When tollPaymentMethods is supplied, each toll is priced at the cheapest fare among the declared methods.
tollSummary	Returned when tollSummary=true. Contains a tolls array with one entry per toll on the route, in route order. A toll system that charges more than once on a route appears more than once.
tolls[].system	The toll authority's name as reported by the toll data provider, for example NEW JERSEY TURNPIKE.
tolls[].fares	The available fares for this toll, sorted with non-transponder methods first in the order CASH, CARD, PLATE, followed by named transponder systems alphabetically. Empty if none of the toll's fares are recognized.
tolls[].fares[].method	The payment method for this fare. One of the values listed in Payment Methods. Never TRANSPONDER; transponder fares are listed under their named system such as EZPASS.
tolls[].fares[].price	The fare in USD.
routeWarnings	Includes tollDataUnavailable when toll data is not available for a section of the route.

Example Response

"tollCost": 22.84,
"tollSummary": {
  "tolls": [
    {
      "system": "NYC CONGESTION PRICING",
      "fares": [
        { "method": "PLATE",  "price": 8.1 },
        { "method": "EZPASS", "price": 5.4 }
      ]
    },
    {
      "system": "NEW JERSEY TURNPIKE",
      "fares": [
        { "method": "CASH",   "price": 20.14 },
        { "method": "EZPASS", "price": 17.44 }
      ]
    }
  ]
}

In this example the request declared tollPaymentMethods=EZPASS,CASH,PLATE, so the EZPASS fare was utilized for each toll, resulting in 22.84 = 5.40 + 17.44. A tollPaymentMethods without EZPASS, or omitted entirely, would instead have had "tollCost": 28.24 for matching the other method or falling back to the highest priced fare.