- Compute Routes: duration, distance, encoded polyline and step-by-step legs for driving, walking, cycling or transit
- Compute Route Matrix: many origins × many destinations in one call for territory and visit planning
- Traffic-aware routing (TRAFFIC_AWARE / TRAFFIC_AWARE_OPTIMAL) and departure-time options
- Halo gives route and ETA answers through Atlas in its maps scenario; Iris admins run both routes from the hub
- Both routes read-only; field masks limit response size and billing SKU; every call logged in your tenant
Google Routes API Connector
Google's Routes API — compute routes and route matrices with traffic-aware durations, distances and polylines — connected to Apivom Iris and Apivom Halo with your own Maps Platform key: travel times for field planning in the CRM and live directions from the assistant.
What you can do
Use cases
- ETA in the assistant's answer — Halo tells a customer how long the drive to your showroom is right now, with traffic, instead of a static “about 20 minutes”.
- Plan a day of visits — Run a route matrix across the companies a sales rep wants to visit and order the day by real driving time rather than straight-line distance.
- Delivery and service windows — Compute traffic-aware durations for a departure time to quote realistic arrival windows on service tickets.
The Routes API is Google's successor to the legacy Directions and Distance Matrix services on routes.googleapis.com. Two operations cover it: Compute Routes returns one or more routes between an origin and a destination — duration, distance, an encoded polyline and the legs and steps to render turn-by-turn — with traffic-aware timing and travel-mode options; Compute Route Matrix returns durations and distances for every origin–destination pair in a single request, which is what visit planning and territory balancing need. Apivom Atlas registers both read-only routes. Apivom Halo uses them in its maps scenario: when a caller asks how long it takes to reach a branch or how to get there, the assistant computes the route through Atlas with the tenant's key and answers with a current ETA. In Apivom Iris, administrators can run either route from the integrations hub against the stored key, and the Google Maps features of the CRM build on the same key family. Field masks are mandatory on this API, so each call is scoped to the fields you need and billed on the matching SKU. Every request and response is logged in your tenant.
Your own Google Cloud API key (Maps Platform) with this API enabled on the project; the Apivom product sends it as the x-goog-api-key header on each call. Google bills the project that owns the key. The key is encrypted in your Iris tenant; Apivom Atlas stores nothing.
Frequently asked questions
Is this the same as the old Directions API?
It replaces it. Routes API returns the same kind of result — routes, legs, steps, polylines — with better traffic modelling, more vehicle and routing options and a field-mask-based pricing model. The legacy web services are registered separately as the Google Maps (Legacy) connector.
Which travel modes and traffic options are supported?
Driving, walking, cycling, two-wheeler and transit, with routing preferences such as TRAFFIC_AWARE and TRAFFIC_AWARE_OPTIMAL and an optional departure time. The options you pass are forwarded unchanged to Google.
Which Google Cloud project pays for the calls?
The project that owns the API key you connect. Enable this specific API on that project, restrict the key to the APIs you actually use, and Google's Maps Platform pricing and monthly credit apply to it directly — Apivom adds no charge and shows every call in your tenant's integration log.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.