API Pricing
The Targomo API is priced based on usage type and volume. Find the right plan for your business needs.
|
Free
0€
Free Tier
|
Basic
50€ / month
Sign Up
|
Pro
150€ / month
Sign Up
|
Advanced
300€ / month
Sign Up
| |
|---|---|---|---|---|
| GENERAL | ||||
|
requests per month*
how many individual get/post requests to the API each month
|
3,000
|
15,000 | 50,000 | 150,000 |
|
logo/link
inclusion of the Targomo logo and attribution in application
|
logo & link
|
link only | link only | link only |
|
SLA 99%
service level agreement
|
highlight_off | check_circle_outline | check_circle_outline | check_circle_outline |
|
dedicated support
our developers on-hand to help you
|
highlight_off | 48h | 24h | 12h |
|
commercial
commercial use allowed
|
highlight_off | check_circle_outline | check_circle_outline | check_circle_outline |
|
private or paid-use implementation
usage allowed in a non-public and/or paid-use scenario
|
highlight_off | highlight_off | highlight_off | check_circle_outline |
|
printing
allowed to use product for professional print services
|
highlight_off | check_circle_outline | check_circle_outline | check_circle_outline |
|
rush-hour modeling
model travel times respecting peak travel periods - where available
|
highlight_off | check_circle_outline | check_circle_outline | check_circle_outline |
|
enable elevation
use elevation data to improve precision
|
check_circle_outline | check_circle_outline | check_circle_outline | check_circle_outline |
|
walk and bike speed
how fast travel people and bikes
|
check_circle_outline | check_circle_outline | check_circle_outline | check_circle_outline |
| BASIC SERVICES | ||||
|
manipulate your polygons
buffer and simplify your polygons
|
highlight_off | highlight_off | check_circle_outline | check_circle_outline |
|
buffering
maximum buffer meters/degrees
|
highlight_off | highlight_off | 100/0.002 | 250/0.004 |
|
maximum routing time
upper limit (time) for polygon/route/time/multigraph requests
|
30min
|
1h | 2h | 4h |
|
maximum routing distance
upper limit (distance) for polygon/route/time/multigraph requests
|
60km
|
120km | 240km | 480km |
|
maximum polygon rings
upper limit for polygons per request
|
3
|
4 | 6 | 8 |
|
maximum polygon sources
maximum number of points which can be used for polygon requests
|
25
|
100 | 500 | 5,000 |
|
maximum sources route/time
maximum number of points which can be used to for route/time requests
|
2
|
3 | 5 | 10 |
|
maximum route targets
maximum number of points which can be routed per route request
|
25
|
100 | 1,000 | 2,000 |
|
maximum time targets
maximum number of points which can be routed per time request
|
250
|
1,000 | 10,000 | 20,000 |
|
minimum hole size
level of internal precision allowed in polygon creation
|
100km²
|
50km² | 10km² | 10km² |
|
intersect your polygons
create aggregations for many source points
|
union
|
union / intersection | union / intersection / average | union / intersection / average |
|
sources for intersecting - union
maximum number of sources for polygon/time union
|
25
|
100 | 500 | 2,000 |
|
sources for intersecting - non-union
maximum number of sources for polygon/time intersection/average
|
2
|
3 | 5 | 10 |
| MULTIGRAPH SERVICE | ||||
|
multigraph non-aggregated response
create un-aggregated multi graph responses for many source points
|
highlight_off | check_circle_outline | check_circle_outline | check_circle_outline |
|
sources for basic multigraph aggregation
maximum number of sources for aggregations - `routing_union` mode
|
25
|
100 | 500 | 5,000 |
|
sources for advanced multigraph aggregation
maximum number of sources for aggregations - `max/min/avg/mean/median/nearest/sum` modes
|
2
|
3 | 5 | 10 |
|
multigraph serialization formats
applicable serialization formats for the multi graph service
|
geojson / mvt
|
geojson / mvt / json | geojson / mvt / json | geojson / mvt / json |
|
multigraph maximum geometries returned
approximate upper limit of how many geometries may be returned per request
|
100,000
|
200,000 | 400,000 | 800,000 |
The following services are accessible to standard API users, but their functionalities are quite restricted - for you to test out, primarily. Do you want to use either of these powerful services? Contact us below, and we'll get you set-up with these services.
How is an operation counted?
For the majority of our services, 1 request counts as 1 operation. Tile-based services are counted as 15 tiles to 1 operation.
What payment types are accepted?
Our paid plans are payable by major credit cards. If you require a special payment method, please use the form on this website.
When do I need to contact sales?
If you have needs outside the listed plans, you need to use the contact form on the pricing page so we can get you set up with a custom plan.