Set up Google Maps in RouteIQ
Create a Google Maps Platform API key, enable only the services RouteIQ needs, and decide which mapping operations Google should handle for your site.
What you will connect
RouteIQ sends mapping requests from its servers using your Google Maps Platform API key. The key is stored encrypted and is not sent to drivers, dispatchers, or customer browsers.
Google Maps can power every RouteIQ mapping operation: address autocomplete, forward and reverse geocoding, route-matrix calculations, routing, and stop sequencing.
Before you start
You will need:
- A Google account with permission to create or manage a Google Cloud project.
- A billing account attached to that project.
- Administrator access to your RouteIQ site.
Create a key specifically for RouteIQ rather than reusing one from a website, mobile app, or another server. This makes restrictions, monitoring, and rotation safer.
1. Create or choose a Google Cloud project
- Open Google Maps Platform in Google Cloud Console.
- Select an existing project or create a project dedicated to RouteIQ.
- Confirm that billing is enabled for the selected project. Google will not serve normal Maps Platform requests without a billing account.
2. Enable the APIs RouteIQ will use
Open the Google Maps API Library for the same project. Enable the API associated with every RouteIQ operation you plan to select:
| RouteIQ operation | Google service to enable | What it affects |
|---|---|---|
autocomplete |
Places API (New) | Address suggestions while a user types. |
geocode |
Geocoding API | Converting a street address into coordinates. |
reverse_geocode |
Geocoding API | Converting coordinates into a readable address. |
matrix |
Routes API | Travel-time and distance calculations between locations. |
routing |
Routes API | Calculating the route between stops. |
sequence |
Route Optimization API | Finding the most efficient order for multiple stops. |
Do not enable unrelated Google APIs for this key. You can return later if you assign another supported operation to Google.
3. Create and restrict the API key
- Open Credentials in Google Cloud Console.
- Select Create credentials, then API key.
- Give the key a recognizable name such as RouteIQ production.
- Under API restrictions, choose Restrict key and select only Places API (New), Geocoding API, Routes API, and Route Optimization API, or the subset matching your RouteIQ operations.
- Save the restrictions, then copy the key. Treat it like a password.
RouteIQ calls Google from its servers and does not provide stable outbound IP addresses. An IP-address application restriction will therefore block legitimate RouteIQ requests. Website-referrer restrictions will also block these server-side requests. Leave application restrictions unset and limit the key to the required Google APIs instead.
Google's API key security guidance explains the available restrictions and rotation practices in detail.
4. Connect Google Maps to RouteIQ
- Sign in to RouteIQ and open Settings > Integrations.
- Find the Google Maps card and turn it on.
- After the card shows Connected, select Configure.
- Paste the key into Google Maps API Key.
- Select the operations Google should handle. Use the next section to choose.
- Leave Is Active selected and save the configuration.
5. Choose the right operations
Each map feature, such as address search or route planning, uses one provider at a time.
Mix providers to control cost
You do not have to use one map provider for everything. You can choose Google Maps, HERE Maps, Mapbox, or an included provider for each feature. Compare each provider's pricing, allowances, accuracy, and regional coverage, then use the most cost-effective provider for each feature.
For example, you can use Google for address search and geocoding while another provider handles route calculations. Changing one feature later does not affect the others.
Google Maps coverage
Google Maps supports every RouteIQ mapping operation. Select all six operations to use Google for the entire mapping workflow, or assign only the operations where it gives you the best combination of cost, accuracy, and coverage.
Adding matrix requires the Routes API and may materially increase Google usage,
so compare the expected request volume and pricing before assigning it.
6. Verify the setup
- Return to the Google Maps integration card and confirm it says Connected and displays the operations you selected.
- Create or edit a test job and begin entering a new street address.
- Select a suggestion and confirm RouteIQ places the address correctly on the map.
- In Google Cloud, check Metrics for the enabled APIs after a few minutes to confirm the requests are using the new key.
If you enabled matrix, use a non-production test job with at least two valid
locations and confirm that RouteIQ calculates travel time and distance.
If you enabled routing or sequence, use a test job with multiple
stops and confirm that RouteIQ calculates the route and optimized stop order.
Troubleshooting
Google reports that the request was denied
Confirm billing is active, the required API is enabled in the same project as the key, and the key restrictions allow that API. Website-referrer restrictions are not compatible with RouteIQ's server-side requests.
Address suggestions do not appear
Confirm that Places API (New) is enabled and that autocomplete is assigned to
Google Maps in RouteIQ.
RouteIQ rejects an operation assignment
Check whether another active mapping provider already owns that operation. Move the operation from the other provider before assigning it to Google Maps.
The key works and then starts failing
Check Google Cloud quotas, billing status, restriction changes, and API usage. Avoid deleting a working key until its replacement has been verified.
Rotate or remove the key
- Create and restrict a replacement key in the same Google Cloud project.
- In RouteIQ, select Configure on the Google Maps card and replace the existing key.
- Verify address search and any assigned matrix operation.
- Disable or delete the old key in Google Cloud only after verification succeeds.