Developer Q&A

Request an API Developer Account and register using the invitation token. Only one account per developer is permitted. Within that account, choose the OSM or Google plan and use the API key and documentation for that plan to make your first request.

Each API has its own 30-day trial: you can try both Google and OSM within your developer account. Only one account per developer is permitted. Check the included trial usage and expiry for each API in the Developer Console.

The web toll calculator and API service are separate subscriptions. Choose an API plan in the Developer Console and review its current price and included usage.

The invitation token creates your developer account; it is different from the API key used in requests. If the invitation has expired, request a replacement. If registration failed after you entered a valid token, contact support with the error message.

Sign in to the Developer Console and download the PDF documentation under your selected plan. OSM and Google have separate documentation, so use the document that matches your plan. If documentation is missing, contact support and identify your plan.

Contact support with the error message and the email address used for registration. Avoid creating more accounts or repeatedly changing passwords to work around the error. Support can check whether registration completed and whether the account needs activation or correction.

Download the latest PDF for your plan from the Developer Console and compare its endpoint URLs and request format with your integration. Update any legacy URLs. If you need help, provide a sanitized request and the response you received.

You can continue using the key issued for your selected plan when the trial ends. You can also rotate the key; update your integration to use the replacement key if you do. To continue beyond the trial, activate the paid plan in the Developer Console and confirm its price, usage allowance and billing settings.

There are three usage-limit settings: (1) Stop API access until the next billing period starts. This is the default. (2) Automatically increase to a higher tier when the allowance is exhausted. (3) Continue using the API and pay for additional usage at the plan's extra-query rate. Choose the setting in the Developer Console and review the applicable tier prices and extra-query rate.

Yes. Within the tiered structure, one HTTPS request counts as one API call. In Google pay-as-you-go mode, a typical request with an origin address and a destination address involves two geocodes plus one toll calculation, counted as three usage units. Requests with additional stops can involve further usage. OSM continues to count as one usage unit per call, including pay-as-you-go mode.

Google and OSM plans have separate API keys. Use the key issued for the backend you are calling, and check that the plan is active in the developer console. If a matching key still fails, send support the endpoint, timestamp, request ID and a sample request with the key removed.

No. OSM_EMPTY_RESPONSE is an error, normally returned with HTTP 502. A successful toll-free route still returns a nonempty result array with zero toll totals. Check error.code, error.retryable and error.request_id, use bounded retries where indicated, and report persistent failures with the request ID.

Include the endpoint, approximate request time and timezone, HTTP status, error code, request ID, and a reproducible payload with API keys and personal information removed. For an unexpected toll, include the vehicle characteristics, relevant transponder selection and route or trace so support can reproduce the calculation.

For planning a trip, either the Google or OSM plan will do: submit an origin, destination and optional waypoints to that plan's routing endpoint. To reconstruct a recorded trip from GPS points, use OSM map matching at /TollsAPI/osm/map_matching.

The Google API accepts a supplied_route array for an existing detailed Google route. Route geometry needs enough detail to identify the roads and toll crossings accurately. Matching a third-party route does not guarantee compatibility.

OSM point-to-point trip planning typically takes milliseconds. The Google-based API generally takes longer because it analyzes the full route geometry before calculating tolls. OSM map matching can take longer depending on the length of the recorded trip. These are typical processing characteristics; actual response times vary by request.

Both APIs document numeric distance_meters and duration_seconds fields for a route or route segment.

Supply the supported transponder accounts you want the API to consider. Eligible common transponder discounts are reflected in personalized_value. Special discounts such as local-resident programs are not generally computed. Account formats and coverage differ by backend, so use that backend's documentation.

Yes. Vehicle specifications can be supplied for vehicles up to nine axles. Complete the relevant vehicle and trailer characteristics rather than relying on the default two-axle passenger vehicle. Keep type flags consistent, since conflicting types or missing classification details can change the price. OSM also offers truck-aware routing.

Submit a continuous trace with no more than 1,000 points, a total outlined distance no greater than 1,000 km and no consecutive-point gap greater than 50 km. The documented minimum route length is 600 m. Supply accurate latitude/longitude, epoch-millisecond time_stamp values, and speed and signal_accuracy when available. GPS quality and continuity matter as much as point count.

Map matching estimates the road traveled from the supplied GPS trace. Points on the opposite carriageway, poor horizontal accuracy or large gaps can make the reconstructed path differ from the actual journey. Inspect the returned route against the trace, remove clearly inaccurate points, and test with a continuous, representative set of points before relying on the toll result.

Check the documented point-count, total-distance and point-gap limits first. For a trip that still times out, try splitting it into consecutive requests, preserving continuity and submitting them sequentially. There is no universal recommended split length. Ticketed toll roads need special handling because their price may depend on an entry in one request and an exit in another.

A ticketed road may require both entry and exit to calculate its price. on_ticketed_road indicates a partial journey on such a road, so a missing or zero entry/exit price is not confirmation that the road is free. If your integration needs to join split trips, contact support about enabling toll IDs and using /readprices with the paired entry and exit.

NOT_READY indicates that a timing or concurrency gate rejected the request, often because earlier work is still running. Keep one OSM map-matching request in progress per key unless parallel processing has been enabled for your plan. Check the retryable field and use bounded retries with increasing delays when appropriate.