This article outlines two primary methods for generating a Google Maps route (URL) with multiple coordinates without a private API key or a complex development environment.
The URL generated from either of these methods can then be launched in the app, for example, an Action field with the User Interaction set to “Open Link in Web Browser” or “Open URL in App”, and passing the generated URL as a parameter.
Note: Generating the URL in-app can be achieved using the CONCAT(value1, value2, value3,…) function that can contain static and dynamic values captured in a form.
The Google Maps “Universal” URL (API-Style)
Launching a Google Maps route with multiple coordinates is best done using the Google Maps URLs API. This is a universal, cross-platform format that works in any browser and automatically opens the Google Maps app on iOS and Android.
Key Parameters
| Parameter | Requirement | Description |
api=1 | Required | Mandatory parameter to trigger this specific URL handler. |
origin | Optional | Starting point. If left blank, it defaults to the user’s current location. |
destination | Required | The final stop on your route. |
waypoints | Optional | A list of intermediate stops separated by a “|” pipe character. |
travelmode | Optional | Can be driving, walking, bicycling, or transit. |
Example URL
If you want to start at one coordinate, hit two intermediate stops, and end at a final destination, your URL would look like this:
Note: If you are building this URL programmatically (like in Javascript or Python), make sure to URL-encode the pipe character (|) as %7C to prevent the link from breaking in certain browsers.
The Google Maps “Browser” URL (Direct-Style)
This is the “classic” URL seen in your browser address bar. It is often more flexible for desktop users and supports a slightly higher number of waypoints in some browsers.
- Structure: Each coordinate set is simply a new “folder” in the URL path, separated by a
/. - Sequence: The first coordinate is the start, the last is the end, and everything in between is a stop.
- Simplicity: No parameter names (like
origin=) are required.
Example URL
To go from a park to a museum via a specific street corner:
Note: Do not use spaces after the commas, as browsers will replace them with %20, making the URL harder to read.
Comparison: API-Style vs. Browser-Style
| Feature | Universal URL (/dir/?api=1) | Browser URL (/maps/dir/) |
| Primary Use | Best for Apps, websites, and QR codes. | Best for desktop browsers and manual link sharing. |
| Pros | Guaranteed to open the mobile app; very stable. | Human-readable; faster to manually edit. |
| Stop Limit | Maximum 11 total points (9 waypoints). | Can sometimes handle up to 25 points on desktop. |
| When to Use | Use this for software integration or when you need a link to work perfectly on both iPhone and Android. | Use this for quick personal planning or when you need more than 9 intermediate stops. |
Critical Tips for Both Methods
- URL Encoding: If you are using the API-style (
api=1), the pipe character|between waypoints often needs to be encoded as%7Cto prevent the link from breaking in certain apps or email clients. - No Spaces: Never put a space after the comma in a coordinate pair (e.g., use
40.7,-74.0, not40.7, -74.0). - Coordinate Order: Google always uses
Latitude, Longitudeorder. Swapping them will likely land your route in the middle of the ocean.