ApivomApivom
Get Demo

Google Maps Web Services (Legacy) Connector

Google's legacy Maps web services on maps.googleapis.com — Geocoding, Directions, Distance Matrix, Elevation, Time Zone, Street View and the legacy Places endpoints — registered in Apivom Atlas as 14 read-only routes for systems that still depend on the classic request format, with your own Maps Platform key.

What you can do

  • Geocode addresses and reverse-geocode coordinates; look up time zones and elevation for any point
  • Legacy Directions and Distance Matrix for drive times where the newer Routes API is not yet adopted
  • Legacy Places endpoints: text, nearby and find-from-text search, details, autocomplete and photos
  • Street View static images and metadata for a location or panorama id
  • All 14 routes read-only; Google recommends the Routes and Places (New) APIs for new work

Use cases

  • Keep an older integration running — Route an existing Geocoding or Distance Matrix client through Atlas to gain per-tenant logging without rewriting it for the new APIs yet.
  • Enrich addresses with time zone and elevation — Geocode a site address, then fetch its time zone and elevation in two follow-up calls for scheduling or engineering records.

Before Routes API and Places API (New), Google Maps Platform exposed its server-side features as a family of simple GET web services under maps.googleapis.com — Geocoding, Directions, Distance Matrix, Elevation, Time Zone, Street View Static and the original Places endpoints. Many ERPs, logistics tools and older integrations still speak this format. Apivom Atlas registers 14 of these legacy routes, all read-only, so a tenant can keep using them through the gateway with per-tenant logging and the AI integration guide (llms.txt) while planning a migration: Google has marked the legacy Places and Directions services as legacy and steers new development to Routes API and Places API (New), both of which Apivom registers as separate connectors. No Apivom product workflow calls the legacy services today — Apivom's own map features use the newer APIs — so this connector is there for your own tooling and for compatibility, with your own Maps Platform key and your project's quotas.

Authentication

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

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Should I build on this or on the newer Google APIs?

On the newer ones. Google treats Directions, Distance Matrix and the original Places endpoints as legacy; Routes API and Places API (New) are the supported successors and are registered as their own connectors. Use this connector for compatibility and migration windows.

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.