The Autohive OpenRouteService integration connects you to the OpenRouteService API, enabling:

  • Address geocoding - Find the best matching coordinates for an address or place name, defaulting to New Zealand
  • Drive-time isochrone generation - Generate one or more drive-time catchment polygons (GeoJSON) from a single origin point
  • Travel-time matrix calculation - Calculate road-network driving durations (and optional distances) for many labelled origin-destination pairs in a single request

Install the integration

  1. Log in to Autohive and navigate to Your user profile > Integrations or Your workspace -> Integrations

  2. Locate the OpenRouteService Integration card and click Connect to workspace

    List of integrations in Autohive

  3. Authenticate - this integration uses a free OpenRouteService API key:

  4. Confirm installation - you’ll see “Connected” status displayed

Use the integration

You can now use the integration with your agents, workflows and scheduled tasks!

  1. Follow our Create your first agent guide on how to create an agent.
  2. In the ‘Agent settings’, scroll down to the ‘Add Integrations and Agents’ section, click ‘Add integrations and agents’, and select OpenRouteService. You can choose what individual OpenRouteService capabilities to turn on and off.
  3. Once the settings have been selected, begin prompting the agent with the workflow you’d like to achieve with Autohive and OpenRouteService!

Available capabilities

Geocoding

  • Geocode Address: Find the best matching address or place through HeiGIT Pelias. Defaults the country boundary to New Zealand and flags matches below 0.8 confidence (is_low_confidence) for human confirmation before using them downstream.

Isochrones

  • Get Isochrone: Generate one or more drive-time bands (1-10 bands, 1-60 minutes each) from a single origin point in a single request, returning the unaltered OpenRouteService GeoJSON FeatureCollection. The current release supports the driving-car travel profile only. Optionally export the FeatureCollection as a platform file.

Travel-Time Matrix

  • Get Travel-Time Matrix: Return driving durations (and optional distances) for every labelled origin-destination pair in a single request. Each origin and destination is a caller-defined {id, latitude, longitude} point; up to 10,000 origins, 10,000 destinations, and 10,000 total pairs (origins x destinations) per request. Larger matrices are split into provider-compliant batches automatically, then reassembled so every pair appears exactly once. Unreachable, unsnappable, or non-finite pairs return null rather than 0. Optionally export the compact result as a platform file.

Key features

New Zealand-first geocoding with confidence flags

Geocoding defaults its country boundary to NZ, matching the integration’s primary use case of New Zealand catchment analysis, though any ISO 3166-1 alpha-2 country can be supplied. Matches below 0.8 confidence are flagged via is_low_confidence so a calling workflow can confirm the result before using it in a downstream isochrone or matrix call.

Multi-band isochrones in one request

Get Isochrone accepts up to 10 driving-time bands (e.g. 10, 15, and 30 minutes) in a single call, returning them all in one GeoJSON FeatureCollection rather than requiring one request per band.

Labelled travel-time matrices at scale

Get Travel-Time Matrix returns an origin-major, destination-minor table of driving durations for every requested pair, automatically batching and reassembling requests larger than OpenRouteService’s per-call route limit. This is a labelled origin-destination table only - it does not select facilities or apply demographic or catchment rules itself.

Provider errors returned as data, not exceptions

Provider failures (rate limits, quota errors, invalid requests) come back as a successful action payload with result: false rather than throwing, so a calling skill can read error_type and retry_after_seconds and decide whether to retry. Credentials and provider error bodies are never returned.

Rate limits and quotas

HeiGIT enforces two quotas per API key: a sliding 60-second rate limit (error_type: "rate_limit", retry after retry_after_seconds) and a rolling 24-hour daily quota (error_type: "quota_exceeded" or "quota_or_unauthorized" - do not retry immediately; check the HeiGIT dashboard).

Common use cases

Demographic catchment analysis

  1. Geocode Address for a site or store location, confirming the match if is_low_confidence is true
  2. Get Isochrone with the drive-time bands you need (e.g. 10, 15, 30 minutes) to produce map-ready coverage areas
  3. Feed the resulting GeoJSON into further analysis, such as a Stats NZ Datafinder query scoped to the isochrone polygon

Delivery and service area planning

  1. Geocode Address for each depot or service location
  2. Get Isochrone to generate drive-time coverage polygons for delivery or service planning
  3. Compare coverage areas across multiple bands to plan service tiers

Site selection and accessibility

  1. Geocode Address for candidate sites
  2. Get Isochrone to visualize how far customers or staff can travel to each site within a given time
  3. Use the results to compare accessibility across candidate locations

Multi-site travel-time comparisons

  1. Geocode Address for each staff, customer, or facility location you want to compare
  2. Get Travel-Time Matrix with those points as labelled origins and destinations to get driving durations (and optional distances) for every pair in one request
  3. Use the results to compare travel burden across facilities, plan staff rosters, or rank candidate sites by aggregate travel time

Notes

  • New Zealand default, global capable: geocoding defaults to the NZ country boundary but accepts any ISO 3166-1 alpha-2 country code.
  • Driving only currently: Get Isochrone and Get Travel-Time Matrix currently support the driving-car travel profile only.
  • Isochrone limits: driving-time bands are capped at 60 minutes and 10 intervals per request - this matches OpenRouteService’s public isochrone limit.
  • Travel-time matrix limits: each of origins and destinations is capped at 10,000 points, and the product (origins x destinations) is capped at 10,000 pairs per request.
  • No key leakage: the API key is passed only in the Authorization header and is never included in request URLs or action output.
  • 90-second timeout, no retry: Get Isochrone and Get Travel-Time Matrix use a 90-second timeout per request/batch and do not retry on timeout, so a slow compute that already counted against the daily quota is not charged again.

Disconnect the integration

Important: Disconnecting removes access to OpenRouteService from your Autohive workspace.

  1. Navigate to Your user profile -> Connections or Your workspace -> Integrations
  2. Find the OpenRouteService Integration
  3. Click Disconnect and confirm

Data Impact: Disconnecting stops API access using your stored key but does not affect any data held by OpenRouteService or your OpenRouteService account.

About OpenRouteService

OpenRouteService is an open-source routing and geospatial analysis service built on OpenStreetMap data and operated by HeiGIT (Heidelberg Institute for Geoinformation Technology). It provides geocoding, routing, and isochrone (drive-time catchment) generation used widely for logistics, accessibility, and demographic analysis.