FAQ and Support

Generallink

Where do I get my API key?link

You can see our offering on the pricing page. When you sign up for a plan, your API key will be emailed to you, and will likewise be available on your dashboard.

Is this service available for my geographic region?link

Targomo’s API services offer global coverage. For walk, bike, and car modes, the coverage comes from OpenStreetMap project, and is global in nature. For transit mode, coverage is determined by available GTFS data. See our coverage page for full details.

How accurate are Targomo's APIs?link

Regarding our API accuracy - the main points to know are what we base our services upon. Our primary data source is OpenStreetMap. We use this for walk, bike, and car routing, as well and access to and from transport hubs. Lyft has written about OSM data quality and accuracy, and their findings speak volumes. For transit routing, we use publicly available GTFS data. If the data sources are good, the routing is good, but if the source data isn’t great, we can’t make up for that. Fortunately (at least in North America and Europe,) GTFS is a pretty established standard, and the routing is therefore good. What we can’t account for is missing data sources. If there is a public transit provider whose data is hard to find, or not open at all, we have a hard time knowing this. That said, it’s easy for us to add new sources, so we count on our users to help us learn of new sources. Contact us if you want to bring a data source to our attention. Used throughout our routing is our rush-hour/congestion mode. We build machine-learning models of traffic density patterns from GPS data sources, and apply these models to our entire global network. This means we have decent estimates globally. These estimates are not live data, but comparing our routing times with well-known global routing providers, our results fall within the estimate windows they return. Perfect congestion routing is not possible, but we are on-target with the industry expectations.

How much does it cost to use the Targomo API?link

The Targomo API for public use includes a credit of 300 € each month. As you use the APIs, any operations you accrue will not be charged until they exceed the 300 € credit. Beyond the credit, the operations for each API are assigned costs based on the costs per operation charts on the pricing page.

What do I need to attribute to use Targomo Services?link

You need to attribute Targomo Services and OpenStreetMap Contributors, as our services derive travel times based on OpenStreetMap data. Depending on your region, you may need to attribute other data providers. Unless otherwise agreed upon, you must include our logo, along with a link to our attribution page. Guidelines can be found at the attribution page. Custom plans can be arranged which allow attribution-free use - contact us if this is a requirement.

Polygonslink

What coordinate system are the polygons in?link

By default, the polygons are in the web mercator projection, which is the current de facto for web maps. If you set the polygon.serializer to “geojson”, and the polygon.srid to “4326”, you can get WGS 84 GeoJSON polygons.

Pricinglink

What does 'Private-Use/OEM' mean?link

Any utilization of our APIs which are not freely accessible to the public are classified as “Private-Use/OEM”. This includes internally used applications, paid-use applications, and use in offline analyses. If your use isn’t public, you need to contact our sales team to get our private use pricing.

Can I cache or store the API results?link

Targomo’s API is a volume-based model, and results of the APIs may not be permanently stored for future re-use. If your use-case requires this, we are happy to discuss this as part of a custom offering - contact us if this is a requirement.

How is an operation counted?link

Several factors influence how a request to our APIs translates into operations

  • maxRoutingtime: each 60 minutes is counted as 1 operation
  • sources(and targets): each source is counted as 1 operation. If the API accepts targets as well, each 100 targets counts as 1 operation
  • routing intersections: for multigraph API, any intersection mode other than “routing_union” counts as 2x operations. For non-multigraph APIs, any intersection mode other than “union” counts as 2x operations

factors are multiplicative: 2 sources routing to 60 minutes would equal 2*1 = 2 operations. 3 sources routing 120 minutes to 1000 targets would be 3*2*10 = 60 operations.

What payment types are accepted?link

We accept all major credit cards. If you have special billing requirements, please contact our sales team.

Support Requestlink

Reach out if you need more help with something


First name is required

Last name is required

This email is invalid

You need to include an actual message