Skip to main content
Technical Preview

Overview

Client-mode REST API connectors for Google Maps Platform: geocoding, elevation, time zone, device geolocation, Routes API ETAs and matrices, Roads API snap to roads and speed limits, Places search, Address Validation, Weather and Air Quality. This is one of the templates in the Google Maps Platform REST API app (google-maps-platform). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Not yet verified against the live vendor API: No Google Maps Platform API key: every event needs a key. All 18 events were sent to the real Google hosts with a dummy key and got Google’s invalid-key answer (classic web services 200 status REQUEST_DENIED, newer APIs 400 API_KEY_INVALID), but no keyed call could run.

Auth

  • schemes: [“API key query parameter key= (Geocoding, Elevation, Time Zone, Geolocation, Roads, Address Validation, Weather, Air Quality)”, “X-Goog-Api-Key header + required X-Goog-FieldMask header (Routes API, Places API (New))”]
  • secrets: [“GOOGLE_MAPS_API_KEY”]
  • note: OAuth 2.0 service accounts not packaged (Fleet Engine and Route Optimization need OAuth).
Auth headers used by the template: X-Goog-Api-Key: {value.json.apikey}.

Template parameters

BASE_ADDRESS default: https://routes.googleapis.com.

Events

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:
The deployable connector from the REST API app, with BASE_ADDRESS already filled in:
Deploy it with -addRoute (do not include ADD METADATA).

Usage example

Call ComputeRoutes by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 21, 2026