ApivomApivom
Get Demo

Google Roads API Connector

Google's Roads API — snap a sequence of GPS points to the road network and find the nearest road segments for individual coordinates — registered in Apivom Atlas for fleet, telematics and field-service tenants, with your own Maps Platform key.

What you can do

  • Snap to Roads: up to 100 GPS points per request aligned to the most likely road geometry, with optional interpolation
  • Nearest Roads: the closest road segment and place id for up to 100 independent points
  • Both routes read-only; results carry place ids that link to the rest of Google Maps Platform
  • Registered in Atlas with the credential contract and the AI integration guide (llms.txt)

Use cases

  • Clean trip traces for mileage — Snap a day's GPS trace from a field vehicle to the road network before computing distance, so expense and mileage reports are not inflated by GPS noise.
  • Which road was the asset on? — Use Nearest Roads to turn a tracker's coordinate into a road segment and place id for incident reports and geofencing.

Raw GPS traces wander: points drift onto buildings, the wrong carriageway or the parallel street. The Roads API on roads.googleapis.com fixes that. Snap to Roads takes up to 100 consecutive points from a vehicle or phone and returns them aligned to the most probable road geometry — optionally interpolated so the path follows the road between samples — each with the place id of the road segment. Nearest Roads does the same for unrelated points, returning the closest segment for each. Apivom Atlas registers both read-only routes 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 Roads API today — the connector is available to tenants building fleet, telematics or mileage 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 many points can I send at once?

Up to 100 per request for both routes. For longer traces, split them into overlapping windows; with interpolation enabled on Snap to Roads the returned path stays continuous across 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.