Where can I get help?
What is one credit?
You can use the estimator in the dashboard to roughly estimate the necessary credits per day, but note that it can give precise results only in standard cases.
If you need an better estimate contact us or read through the following steps:
- one Routing API request costs 1 credit. Every 10 via-points cost 1 more credit. E.g. 11 via-points cost 2 credits, 21 via-points costs 3 credits and so on. And if you specify
optimize=truethe credits will be multiplied by 10 i.e. one requests costs 10 credits for 1 to 10 locations, 20 credits for 11 to 20 locations and so on. Using the parameter
ch.disable=trueto unlock certain features costs additionally 2 credits, i.e. calculating the route between two points costs 1+2=3 credits.
- Ten Geocoding API requests for the default provider cost 3 credits. For other providers ten Geocoding requests costs 15 credits.
- the costs for one Route Optimization API request depends on the number of vehicles and activities and is calculated as
vehicles * activitiesand at least 10 credits. For custom packages a location independent credit calculation can be arranged.
- the costs of one Map Matching API request costs certain credits calculated by the formula
input_locations / 100.
- the costs of one Matrix API request are calculated as follows: If either the number of
originsor the number of
destinationsis less than 20, it costs
origins * destinations / 2credits. For bigger matrices we use a more favourable formular:
MAX_OF(origins, destinations) * 10. In both cases at least 1 credit is charged. For example, if you have 2 origins and 10 destinations,
2 * 10 / 2 = 10credits will be charged. If you have 30 origins and 40 destinations, the required credits amount to
40 * 10 = 400. If you have one-to-N matrices like 1-to-100, then always the
- the costs for one Isochrone API request is 5 credits for every minute it explores and at least 10 credits. E.g. if you set the
time_limitto 20 minutes then this request will cost
How many credits do I have?
The API credit limits are listed in the dashboard and depend on the selected package.
What happens if I go over the credit limit?
Your API key will not stop working. If this happens frequently, we'll contact you to discuss.
What happens if I go over the location limit?
Location limits are hard limits and you'll get an error e.g. for the Routing API (max. via points), the Route Optimization API (max. services/shipments), for the Matrix API (max. locations) or for the Map Matching API (max. measurements).
What are the rate limits?
The default limits are outlined below. For different limits, please contact us.
You can send up to 100 requests per minute to an end point of the GraphHopper Directions API.
The Geocoding and Routing API, as well as GET requests against the Route Optimization API allow an exception with up to 600 requests per minute.
The Matrix API has an additional limitation where the sum over all locations in all Matrix-requests over a timespan of 5 seconds cannot exceed 300.
Where can I find the documentation or some demos?
Where can I find the pricing?
You can find the detailed pricing in the dashboard. For individual requirements we offer custom packages. Additionally we offer support contracts and a self-hosted Directions API, see here for more details.
Where can I change my credit card or payment data
This is possible in the overview of the dashboard, then click edit data.
Can I pay on demand?
It is possible to pay online e.g. per month for a specific amount of credits/requests. If you exceed this you currently do not need to pay for and the requests won't be blocked but we ask you to upgrade if that happens frequently. Please let us know of your needs and we find a solution.
Do you offer discounts?
Yes, you get a discount if you sign up for an annually contract. Also follow us on Twitter to get the latest campaign.
How to cancel, upgrade or downgrad my package?
Please contact us
Do I need to link or mention the use of the GraphHopper Directions API
Yes, please see here for more details about it. Of course, you can also get rid of this (but not of the OpenStreetMap attribution) if you pay for the extra white-label option or need to use it for an in-house application.
What is the difference between the GraphHopper Directions API and the open source projects like the GraphHopper routing engine and the optimization engine jsprit?
The GraphHopper Directions API is a collection of routing related APIs: the Routing API, the Matrix API, the Route Optimization API and the Geocoding API. This entire set is also available for self-hosting.
We use jsprit to implement our Route Optimization API, it is our open source vehicle route optimization project. The Route Optimization API is an efficient way to consume jsprit: properly configured for a lot of use cases, with a proper distance/time matrix calculated from GraphHopper, with a simple JSON API and some advanced featured not in jsprit.
The Routing API is based on the open source GraphHopper and is nearly identical to it.
We have decided to keep the Matrix API closed source, see graphhopper#131
See here for a more detailed comparison.
Is it possible to use the GraphHopper Directions API with a custom GraphHopper or jsprit version?
Yes, we host custom and recent versions, be it GraphHopper or jsprit. This way you'll be able to use our Route Optimization API and the Matrix API with your custom GraphHopper or jsprit version including custom vehicles, speed profiles, constraints etc.
Can I model a specific vehicle routing problem with your API and if yes, how?
You can get yourself easily familiar with our Route Optimization API using the documentation. But of course we provide every customer support and help to get there vehicle routing problems modeled and solved.