ApivomApivom
Get Demo

Google Geolocation API Connector

Google's Geolocation API — estimate a device's position and accuracy radius from the cell towers and Wi-Fi access points it can see, without GPS — registered in Apivom Atlas for field-service and IoT tenants, with your own Maps Platform key.

What you can do

  • Single geolocate route: send cell-tower and Wi-Fi scan data, receive latitude, longitude and an accuracy radius in metres
  • Works where GPS does not — indoors, in vehicles, on devices without a GNSS chip
  • Supports carrier, radio type and IP-based fallback when scan data is thin
  • One route registered in Atlas with the credential contract and the AI integration guide (llms.txt)

Use cases

  • Locate assets without GPS — Resolve the position of trackers or kiosks that only report the cells and Wi-Fi networks around them, and place them on your map.
  • Indoor check-in for field staff — Confirm a technician is on site when the building blocks GPS, using the Wi-Fi scan from their device.

The Geolocation API answers a narrow but useful question: given the mobile cell towers and Wi-Fi access points a device can currently see, where is it? Its single geolocate route accepts the scan — cell ids, location-area codes, signal strengths, Wi-Fi MAC addresses — together with carrier and radio-type hints, and returns an estimated latitude and longitude with an accuracy radius; when the scan is empty it can fall back to the requester's IP address. That makes it the standard way to locate trackers, kiosks, vehicles and handsets that have no GPS fix. Apivom Atlas registers the route with the Maps Platform credential contract, per-tenant logging and the AI integration guide (llms.txt); your key, project and quotas apply. No Apivom product workflow uses the Geolocation API today — it is available for tenants building field-service or asset-tracking features, and a product flow is scoped per customer.

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.

How accurate is it?

It depends on what the device sees: dense Wi-Fi environments give tens of metres, cell-only scans hundreds to thousands. Every response carries its own accuracy radius so your application can decide whether the fix is good enough.

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.