- Interactive map in Iris — prospecting Map mode with rectangle, circle and polygon search areas — rendered in the browser with your key
- Optional Map ID enables vector rendering and Advanced Markers with your own map styling
- Browser key is non-secret by design: restrict it by HTTP referrer to your Iris host and to the Maps JavaScript API only
- Zero proxied routes: Apivom Atlas publishes the credential contract so Iris can store the key per tenant
- Google bills the project that owns the key; map loads are visible in your Google Cloud console
Google Maps JavaScript API (Browser Key)
The browser-side Google Maps JavaScript API that renders the interactive map in Apivom Iris: your referrer-restricted browser key and optional Map ID are stored as a credential so Map mode in prospecting works with your Google Cloud project. No routes are proxied — this entry publishes the credential contract only.
What you can do
Use cases
- Draw where you want to prospect — Switch prospecting to Map mode, draw the district on the map and let the Places Aggregate connector fill the list for that exact shape.
- Tell prospects from customers at a glance — Search results are pinned on the same map, with companies already in your CRM shown in a distinct colour, so you see white space in a district before you export the list.
The Maps JavaScript API is the part of Google Maps Platform that runs in the browser: it draws the map, the markers and the shapes a user interacts with. In Apivom Iris it powers exactly one surface: Map mode in prospecting, where you draw a rectangle, circle or polygon to search an area and the results are pinned on the map, existing customers in their own colour. Because the script loads client-side, Google requires a browser key that is intentionally visible; the right protection is to restrict that key by HTTP referrer to your Iris host and to enable only the Maps JavaScript API on it. This registry entry exists so Iris can store the tenant's browser key, and an optional Map ID for vector maps and Advanced Markers, as a credential alongside the server-side Google keys. Apivom Atlas proxies no routes here — there is nothing to forward — which is why the route count is zero. Server-side data (places, routes, area insights) comes from the separate Google connectors with their own keys.
A Google Cloud API key restricted by HTTP referrer to your Iris host with only the Maps JavaScript API enabled, plus an optional Map ID. The key is shipped to the browser by design (not a secret); Iris stores it per tenant. Apivom Atlas proxies no routes for this entry.
Frequently asked questions
Isn't it dangerous to store an API key that the browser can see?
A browser key is meant to be public; its security comes from restrictions. Limit it by HTTP referrer to your Iris host and to the Maps JavaScript API only, so it is useless elsewhere. Keep server-side APIs on separate, secret keys.
Why does this connector show zero routes?
Because the Maps JavaScript API is loaded by the browser, not called through a server. Apivom Atlas only publishes the credential contract for this entry so Iris knows how to store and validate the key and Map ID.
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.