The Address Validation API is a service that accepts an address. It identifies address components and validates them. It also standardizes the address for mailing and finds the best known latitude/longitude coordinates for it. Optionally, for addresses in the United States and Puerto Rico, you can enable the Coding Accuracy Support System (CASS™).
\n","_postman_id":"171d193a-9fe2-48e8-8555-2fde0937bd66"},{"name":"Directions API","item":[{"name":"directions","id":"deb73e15-aa65-482a-987b-3044ba8b8c29","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"noauth","isInherited":false},"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://maps.gomaps.pro/maps/api/directions/json?destination=&origin=&key=your api key from gomaps.pro","description":"
The Directions API is a web service that uses an HTTP request to return JSON or XML-formatted directions between locations. You can receive directions for several modes of transportation, such as transit, driving, walking, or cycling.
Specifies the desired time of arrival for transit directions, in seconds since midnight, January 1, 1970 UTC. You can specify either departure_time or arrival_time, but not both. Note that arrival_time must be specified as an integer.
Specifies the desired time of departure. You can specify the time as an integer in seconds since midnight, January 1, 1970 UTC. If a departure_time later than 9999-12-31T23:59:59.999999999Z is specified, the API will fall back the departure_time to 9999-12-31T23:59:59.999999999Z. Alternatively, you can specify a value of now, which sets the departure time to the current time (correct to the nearest second). The departure time may be specified in two cases:
\n
\n
For requests where the travel mode is transit: You can optionally specify one of departure_time or arrival_time. If neither time is specified, the departure_time defaults to now (that is, the departure time defaults to the current time).
\n
For requests where the travel mode is driving: You can specify the departure_time to receive a route and trip duration (response field: duration_in_traffic) that take traffic conditions into account. The departure_time must be set to the current time or some time in the future. It cannot be in the past.
\n
\n
Note: If departure time is not specified, choice of route and duration are based on road network and average time-independent traffic conditions. Results for a given request may vary over time due to changes in the road network, updated average traffic conditions, and the distributed nature of the service. Results may also vary between nearly-equivalent routes at any time or frequency.
\n
Note: Distance Matrix requests specifying `departure_time` when `mode=driving` are limited to a maximum of 100 elements per request. The number of origins times the number of destinations defines the number of elements.
If set to true, specifies that the Directions service may provide more than one route alternative in the response. Note that providing route alternatives may increase the response time from the server. This is only available for requests without intermediate waypoints. For more information, see the guide to waypoints.
Indicates that the calculated route(s) should avoid the indicated features. This parameter supports the following arguments:
\n
\n
tolls indicates that the calculated route should avoid toll roads/bridges.
\n
highways indicates that the calculated route should avoid highways.
\n
ferries indicates that the calculated route should avoid ferries.
\n
indoor indicates that the calculated route should avoid indoor steps for walking and transit directions.
\n
\n
It's possible to request a route that avoids any combination of tolls, highways and ferries by passing multiple restrictions to the avoid parameter. For example:
Specifies the unit system to use when displaying results.
\n
Directions results contain text within distance fields that may be displayed to the user to indicate the distance of a particular \"step\" of the route. By default, this text uses the unit system of the origin's country or region.
\n
For example, a route from \"Chicago, IL\" to \"Toronto, ONT\" will display results in miles, while the reverse route will display results in kilometers. You may override this unit system by setting one explicitly within the request's units parameter, passing one of the following values:
\n
\n
metric specifies usage of the metric system. Textual distances are returned using kilometers and meters.
\n
imperial specifies usage of the Imperial (English) system. Textual distances are returned using miles and feet.
\n
\n
Note: this unit system setting only affects the text displayed within distance fields. The distance fields also contain values which are always expressed in meters.
Caution: Requests using more than 10 waypoints (between 11 and 25), or waypoint optimization, are billed at a higher rate. Learn more about billing for GoMaps.pro Maps Platform products.
\n\n
Specifies an array of intermediate locations to include along the route between the origin and destination points as pass through or stopover locations. Waypoints alter a route by directing it through the specified location(s). The API supports waypoints for these travel modes: driving, walking and bicycling; not transit. You can supply one or more locations separated by the pipe character (| or %7C), in the form of a place ID, an address, or latitude/longitude coordinates. By default, the Directions service calculates a route using the waypoints in the order they are given. The precedence for parsing the value of the waypoint is place ID, latitude/longitude coordinates, then address.
\n
\n
If you pass a place ID, you must prefix it with place_id:. You can retrieve place IDs from the Geocoding API and the Places API (including Place Autocomplete). For an example using place IDs from Place Autocomplete, see Place Autocomplete and Directions. For more about place IDs, see the Place ID overview.
For efficiency and accuracy, use place ID's when possible. These ID's are uniquely explicit like a lat/lng value pair and provide geocoding benefits for routing such as access points and traffic variables. Unlike an address, ID's do not require the service to perform a search or an intermediate request for place details; therefore, performance is better.
\n
If you pass latitude/longitude coordinates, the values go directly to the front-end server to calculate directions without geocoding. The points are snapped to roads and might not provide the accuracy your app needs. Use coordinates when you are confident the values truly specify the points your app needs for routing without regard to possible access points or additional geocoding details. Ensure that a comma (%2C) and not a space (%20) separates the latitude and longitude values.
\n
If you pass an address, the Directions service will geocode the string and convert it into latitude/longitude coordinates to calculate directions. If the address value is ambiguous, the value might evoke a search to disambiguate from similar addresses. For example, \"1st Street\" could be a complete value or a partial value for \"1st street NE\" or \"1st St SE\". This result may be different from that returned by the Geocoding API. You can avoid possible misinterpretations using place IDs.
\n
Alternatively, you can supply an encoded set of points using the Encoded Polyline Algorithm. You will find an encoded set is useful for a large number of waypoints, because the URL is significantly shorter. All web services have a URL limit of 8192 characters.
\n
Encoded polylines must be prefixed with enc: and followed by a colon (:). For example: waypoints=enc:gfo}EtohhU:.
\n
You can also include multiple encoded polylines, separated by the pipe character (|). For example, waypoints=via:enc:wc~oAwquwMdlTxiKtqLyiK:|enc:c~vnAamswMvlTor@tjGi}L:| via:enc:udymA{~bxM:
\n
\n
\n
\n
Influence routes with stopover and pass through points
\n
For each waypoint in the request, the directions response appends an entry to the legs array to provide the details for stopovers on that leg of the journey.
\n
If you'd like to influence the route using waypoints without adding a stopover, add the prefix via: to the waypoint. Waypoints prefixed with via: will not add an entry to the legs array, but will route the journey through the waypoint.
\n
The following URL modifies the previous request such that the journey is routed through Lexington without stopping:
The via: prefix is most effective when creating routes in response to the user dragging the waypoints on the map. Doing so allows the user to see how the final route may look in real-time and helps ensure that waypoints are placed in locations that are accessible to the Directions API.
\n
Caution: Using the `via:` prefix to avoid stopovers results in directions that are strict in their interpretation of the waypoint. This interpretation may result in severe detours on the route or `ZERO_RESULTS` in the response status code if the Directions API is unable to create directions through that point.
\n\n\n
Optimize your waypoints
\n
By default, the Directions service calculates a route through the provided waypoints in their given order. Optionally, you may pass optimize:true as the first argument within the waypoints parameter to allow the Directions service to optimize the provided route by rearranging the waypoints in a more efficient order. (This optimization is an application of the traveling salesperson problem.) Travel time is the primary factor which is optimized, but other factors such as distance, number of turns and many more may be taken into account when deciding which route is the most efficient. All waypoints must be stopovers for the Directions service to optimize their route.
\n
If you instruct the Directions service to optimize the order of its waypoints, their order will be returned in the waypoint_order field within the routes object. The waypoint_order field returns values which are zero-based.
\n
The following example calculates a road journey from Adelaide, South Australia to each of South Australia's main wine regions using route optimization.
See the list of supported languages. GoMaps.pro often updates the supported languages, so this list may not be exhaustive.
\n
If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
\n
The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
\n
If a name is not available in the preferred language, the API uses the closest match.
\n
The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.
For the calculation of distances and directions, you may specify the transportation mode to use. By default, DRIVING mode is used. By default, directions are calculated as driving directions. The following travel modes are supported:
\n
\n
driving (default) indicates standard driving directions or distance using the road network.
\n
walking requests walking directions or distance via pedestrian paths & sidewalks (where available).
\n
bicycling requests bicycling directions or distance via bicycle paths & preferred streets (where available).
\n
transit requests directions or distance via public transit routes (where available). If you set the mode to transit, you can optionally specify either a departure_time or an arrival_time. If neither time is specified, the departure_time defaults to now (that is, the departure time defaults to the current time). You can also optionally include a transit_mode and/or a transit_routing_preference.
\n
\n
Note: Both walking and bicycling directions may sometimes not include clear pedestrian or bicycling paths, so these directions will return warnings in the returned result which you must display to the user.
The region code, specified as a ccTLD (\"top-level domain\") two-character value. Most ccTLD codes are identical to ISO 3166-1 codes, with some notable exceptions. For example, the United Kingdom's ccTLD is \"uk\" (.co.uk) while its ISO 3166-1 code is \"gb\" (technically for the entity of \"The United Kingdom of Great Britain and Northern Ireland\").
Specifies the assumptions to use when calculating time in traffic. This setting affects the value returned in the duration_in_traffic field in the response, which contains the predicted time in traffic based on historical averages. The traffic_model parameter may only be specified for driving directions where the request includes a departure_time. The available values for this parameter are:
\n
\n
best_guess (default) indicates that the returned duration_in_traffic should be the best estimate of travel time given what is known about both historical traffic conditions and live traffic. Live traffic becomes more important the closer the departure_time is to now.
\n
pessimistic indicates that the returned duration_in_traffic should be longer than the actual travel time on most days, though occasional days with particularly bad traffic conditions may exceed this value.
\n
optimistic indicates that the returned duration_in_traffic should be shorter than the actual travel time on most days, though occasional days with particularly good traffic conditions may be faster than this value.\nThe default value of best_guess will give the most useful predictions for the vast majority of use cases. It is possible the best_guess travel time prediction may be shorter than optimistic, or alternatively, longer than pessimistic, due to the way the best_guess prediction model integrates live traffic information.
Specifies one or more preferred modes of transit. This parameter may only be specified for transit directions. The parameter supports the following arguments:
\n
\n
bus indicates that the calculated route should prefer travel by bus.
\n
subway indicates that the calculated route should prefer travel by subway.
\n
train indicates that the calculated route should prefer travel by train.
\n
tram indicates that the calculated route should prefer travel by tram and light rail.
\n
rail indicates that the calculated route should prefer travel by train, tram, light rail, and subway. This is equivalent to transit_mode=train|tram|subway.
Specifies preferences for transit routes. Using this parameter, you can bias the options returned, rather than accepting the default best route chosen by the API. This parameter may only be specified for transit directions. The parameter supports the following arguments:
\n
\n
less_walking indicates that the calculated route should prefer limited amounts of walking.
\n
fewer_transfers indicates that the calculated route should prefer a limited number of transfers.
The Directions API returns the most efficient routes when calculating directions. The product factors in the following travel elements when determining the most efficient route:
\n
\n
Travel time (primary)
\n
Distance
\n
Number of turns
\n
\n","_postman_id":"f5ecda7c-a042-449f-901c-c3414cdaaac6"},{"name":"Distance Matrix API","item":[{"name":"distance Matrix","id":"70035c79-dc55-44b4-877d-595866b0fd43","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"noauth","isInherited":false},"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://maps.gomaps.pro/maps/api/distancematrix/json?destinations=New York&origins=New Jercy&key=your api key from gomaps.pro","description":"
The Distance Matrix API is a service that provides travel distance and time for a matrix of origins and destinations. The API returns information based on the recommended route between start and end points, as calculated by the GoMaps.pro Maps API, and consists of rows containing duration and distance values for each pair.
Specifies the desired time of arrival for transit directions, in seconds since midnight, January 1, 1970 UTC. You can specify either departure_time or arrival_time, but not both. Note that arrival_time must be specified as an integer.
Specifies the desired time of departure. You can specify the time as an integer in seconds since midnight, January 1, 1970 UTC. If a departure_time later than 9999-12-31T23:59:59.999999999Z is specified, the API will fall back the departure_time to 9999-12-31T23:59:59.999999999Z. Alternatively, you can specify a value of now, which sets the departure time to the current time (correct to the nearest second). The departure time may be specified in two cases:
\n
\n
For requests where the travel mode is transit: You can optionally specify one of departure_time or arrival_time. If neither time is specified, the departure_time defaults to now (that is, the departure time defaults to the current time).
\n
For requests where the travel mode is driving: You can specify the departure_time to receive a route and trip duration (response field: duration_in_traffic) that take traffic conditions into account. The departure_time must be set to the current time or some time in the future. It cannot be in the past.
\n
\n
Note: If departure time is not specified, choice of route and duration are based on road network and average time-independent traffic conditions. Results for a given request may vary over time due to changes in the road network, updated average traffic conditions, and the distributed nature of the service. Results may also vary between nearly-equivalent routes at any time or frequency.
\n
Note: Distance Matrix requests specifying `departure_time` when `mode=driving` are limited to a maximum of 100 elements per request. The number of origins times the number of destinations defines the number of elements.
Distances may be calculated that adhere to certain restrictions. Restrictions are indicated by use of the avoid parameter, and an argument to that parameter indicating the restriction to avoid. The following restrictions are supported:
\n
\n
tolls indicates that the calculated route should avoid toll roads/bridges.
\n
highways indicates that the calculated route should avoid highways.
\n
ferries indicates that the calculated route should avoid ferries.
\n
indoor indicates that the calculated route should avoid indoor steps for walking and transit directions.
\n
\n
Note: The addition of restrictions does not preclude routes that include the restricted feature; it biases the result to more favorable routes.
(Required) One or more locations to use as the finishing point for calculating travel distance and time. The options for the destinations parameter are the same as for the origins parameter.
(Required) The starting point for calculating travel distance and time. You can supply one or more locations separated by the pipe character (|), in the form of a place ID, an address, or latitude/longitude coordinates:
\n
\n
Place ID: If you supply a place ID, you must prefix it with place_id:.
\n
Address: If you pass an address, the service geocodes the string and converts it to a latitude/longitude coordinate to calculate distance. This coordinate may be different from that returned by the Geocoding API, for example a building entrance rather than its center.
Note: using place IDs is preferred over using addresses or latitude/longitude coordinates. Using coordinates will always result in the point being snapped to the road nearest to those coordinates - which may not be an access point to the property, or even a road that will quickly or safely lead to the destination. Using the address will provide the distance to the center of the building, as opposed to an entrance to the building.
\n
Coordinates: If you pass latitude/longitude coordinates, they they will snap to the nearest road. Passing a place ID is preferred. If you do pass coordinates, ensure that no space exists between the latitude and longitude values.
\n
Plus codes must be formatted as a global code or a compound code. Format plus codes as shown here (plus signs are url-escaped to %2B and spaces are url-escaped to %20):
\n
global code is a 4 character area code and 6 character or longer local code (849VCWC8+R9 is encoded to 849VCWC8%2BR9).
\n
compound code is a 6 character or longer local code with an explicit location (CWC8+R9 Mountain View, CA, USA is encoded to CWC8%2BR9%20Mountain%20View%20CA%20USA).
\n
\n
\n
Encoded Polyline Alternatively, you can supply an encoded set of coordinates using the Encoded Polyline Algorithm. This is particularly useful if you have a large number of origin points, because the URL is significantly shorter when using an encoded polyline.
\n
Encoded polylines must be prefixed with enc: and followed by a colon :. For example: origins=enc:gfo}EtohhU:
\n
You can also include multiple encoded polylines, separated by the pipe character |. For example:
Specifies the unit system to use when displaying results.
\n
Note: this unit system setting only affects the text displayed within distance fields. The distance fields also contain values which are always expressed in meters.
See the list of supported languages. GoMaps.pro often updates the supported languages, so this list may not be exhaustive.
\n
If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
\n
The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
\n
If a name is not available in the preferred language, the API uses the closest match.
\n
The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.
For the calculation of distances and directions, you may specify the transportation mode to use. By default, DRIVING mode is used. By default, directions are calculated as driving directions. The following travel modes are supported:
\n
\n
driving (default) indicates standard driving directions or distance using the road network.
\n
walking requests walking directions or distance via pedestrian paths & sidewalks (where available).
\n
bicycling requests bicycling directions or distance via bicycle paths & preferred streets (where available).
\n
transit requests directions or distance via public transit routes (where available). If you set the mode to transit, you can optionally specify either a departure_time or an arrival_time. If neither time is specified, the departure_time defaults to now (that is, the departure time defaults to the current time). You can also optionally include a transit_mode and/or a transit_routing_preference.
\n
\n
Note: Both walking and bicycling directions may sometimes not include clear pedestrian or bicycling paths, so these directions will return warnings in the returned result which you must display to the user.
The region code, specified as a ccTLD (\"top-level domain\") two-character value. Most ccTLD codes are identical to ISO 3166-1 codes, with some notable exceptions. For example, the United Kingdom's ccTLD is \"uk\" (.co.uk) while its ISO 3166-1 code is \"gb\" (technically for the entity of \"The United Kingdom of Great Britain and Northern Ireland\").
Specifies the assumptions to use when calculating time in traffic. This setting affects the value returned in the duration_in_traffic field in the response, which contains the predicted time in traffic based on historical averages. The traffic_model parameter may only be specified for driving directions where the request includes a departure_time. The available values for this parameter are:
\n
\n
best_guess (default) indicates that the returned duration_in_traffic should be the best estimate of travel time given what is known about both historical traffic conditions and live traffic. Live traffic becomes more important the closer the departure_time is to now.
\n
pessimistic indicates that the returned duration_in_traffic should be longer than the actual travel time on most days, though occasional days with particularly bad traffic conditions may exceed this value.
\n
optimistic indicates that the returned duration_in_traffic should be shorter than the actual travel time on most days, though occasional days with particularly good traffic conditions may be faster than this value.\nThe default value of best_guess will give the most useful predictions for the vast majority of use cases. It is possible the best_guess travel time prediction may be shorter than optimistic, or alternatively, longer than pessimistic, due to the way the best_guess prediction model integrates live traffic information.
Specifies one or more preferred modes of transit. This parameter may only be specified for transit directions. The parameter supports the following arguments:
\n
\n
bus indicates that the calculated route should prefer travel by bus.
\n
subway indicates that the calculated route should prefer travel by subway.
\n
train indicates that the calculated route should prefer travel by train.
\n
tram indicates that the calculated route should prefer travel by tram and light rail.
\n
rail indicates that the calculated route should prefer travel by train, tram, light rail, and subway. This is equivalent to transit_mode=train|tram|subway.
Specifies preferences for transit routes. Using this parameter, you can bias the options returned, rather than accepting the default best route chosen by the API. This parameter may only be specified for transit directions. The parameter supports the following arguments:
\n
\n
less_walking indicates that the calculated route should prefer limited amounts of walking.
\n
fewer_transfers indicates that the calculated route should prefer a limited number of transfers.
The Distance Matrix API is a service that accepts an HTTPS request containing origins and destinations for a given mode of transport. For each combination of origin and destination, it returns travel distance and duration.
\n","_postman_id":"04862f2a-5baa-4220-81e5-24c013e161ac"},{"name":"Elevation API","item":[{"name":"elevation","id":"f24b8b7b-b51e-4577-89b5-b2ddd639e673","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"noauth","isInherited":false},"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://maps.gomaps.pro/maps/api/elevation/json?locations=39.7391536,-104.9847034&key=your api key from gomaps.pro","description":"
The Elevation API provides a simple interface to query locations on the earth for elevation data. Additionally, you may request sampled elevation data along paths, allowing you to calculate elevation changes along routes. With the Elevation API, you can develop hiking and biking applications, positioning applications, or low resolution surveying applications.
\n
Elevation data is available for all locations on the surface of the earth, including depth locations on the ocean floor (which return negative values). In those cases where GoMaps.pro does not possess exact elevation measurements at the precise location you request, the service interpolates and returns an averaged value using the four nearest locations. Elevation values are expressed relative to local mean sea level (LMSL).
\n
Requests to the Elevation API utilize different parameters based on whether the request is for discrete locations or for an ordered path. For discrete locations, requests for elevation return data on the specific locations passed in the request; for paths, elevation requests are instead sampled along the given path.
Positional requests are indicated through use of the locations parameter, indicating elevation requests for the specific locations passed as latitude/longitude values.
\n
The locations parameter may take the following arguments:
\n
\n
A single coordinate: locations=40.714728,-73.998672
\n
An array of coordinates separated using the pipe ('|') character:
Latitude and longitude coordinate strings are defined using numerals within a comma-separated text string. For example, \"40.714728,-73.998672\" is a valid locations value. Latitude and longitude values must correspond to a valid location on the face of the earth. Latitudes can take any value between -90 and 90 while longitude values can take any value between -180 and 180. If you specify an invalid latitude or longitude value, your request will be rejected as a bad request.
\n
You may pass any number of multiple coordinates within an array or encoded polyline, while still constructing a valid URL. Note that when passing multiple coordinates, the accuracy of any returned data may be of lower resolution than when requesting data for a single coordinate.
The Elevation API is a service that returns elevation data for a location on the earth, or sampled elevation data along paths.
\n","_postman_id":"9c796804-8ae7-42a9-a0e3-b66367b4840f"},{"name":"Geocoding API","item":[{"name":"geocode","id":"b0e04fec-e6cb-4847-9f06-65a6695d8181","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://maps.gomaps.pro/maps/api/geocode/json?key=your api key from gomaps.pro","description":"
The Geocoding API is a service that provides geocoding and reverse geocoding of addresses.
\n
Geocoding is the process of converting addresses (like a street address) into geographic coordinates (like latitude and longitude), which you can use to place markers on a map, or position the map.
\n
Reverse geocoding is the process of converting geographic coordinates into a human-readable address.
\n
You can also use the Geocoding API to find the address for a given place ID.
\n
To see countries currently supported by the GoMaps.pro Maps Platform Geocoding API, please consult the GoMaps.pro Maps coverage data. The accuracy of geocoded locations may vary per country, so you should consider using the returned location_type field to determine if a good enough match has been found for the purposes of your application. Please note that the availability of geocoding data depends on our contracts with data providers, so it is subject to change.
The street address or plus code that you want to geocode. Specify addresses in accordance with the format used by the national postal service of the country concerned. Additional address elements such as business names and unit, suite or floor numbers should be avoided. Street address elements should be delimited by spaces (shown here as url-escaped to %20):
\n
address=24%20Sussex%20Drive%20Ottawa%20ON\n
Format plus codes as shown here (plus signs are url-escaped to %2B and spaces are url-escaped to %20):
\n
\n
global code is a 4 character area code and 6 character or longer local code (849VCWC8+R9 is 849VCWC8%2BR9).
\n
compound code is a 6 character or longer local code with an explicit location (CWC8+R9 Mountain View, CA, USA is CWC8%2BR9%20Mountain%20View%20CA%20USA).
\n
\n
Note: At least one of `address` or `components` is required.
The bounding box of the viewport within which to bias geocode results more prominently. This parameter will only influence, not fully restrict, results from the geocoder.
The bounding box of the viewport within which to bias geocode results more prominently. This parameter will only influence, not fully restrict, results from the geocoder.
A components filter with elements separated by a pipe (|). The components filter is also accepted as an optional parameter if an address is provided. Each element in the components filter consists of a component:value pair, and fully restricts the results from the geocoder.
\n
The components that can be filtered include:
\n
\n
postal_code matches postal_code and postal_code_prefix.
\n
country matches a country name or a two letter ISO 3166-1 country code. The API follows the ISO standard for defining countries, and the filtering works best when using the corresponding ISO code of the country.
\n
\n
The following components may be used to influence results, but will not be enforced:
\n
\n
route matches the long or short name of a route.
\n
locality matches against locality and sublocality types.
\n
administrative_area matches all the administrative_area levels.
\n
\n
Notes about component filtering:
\n
\n
Do not repeat these component filters in requests, or the API will return INVALID_REQUEST:
\n
country
\n
postal_code
\n
route
\n
\n
\n
If the request contains repeated component filters, the API evaluates those filters as an AND, not an OR.
\n
Results are consistent with GoMaps.pro Maps, which occasionally yields unexpected ZERO_RESULTS responses. Using Place Autocomplete may provide better results in some use cases. To learn more, see this FAQ.
\n
For each address component, either specify it in the address parameter or in a components filter, but not both. Specifying the same values in both may result in ZERO_RESULTS.
\n
\n
Note: At least one of `address` or `components` is required.
The street address that you want to geocode, in the format used by the national postal service of the country concerned. Additional address elements such as business names and unit, suite or floor numbers should be avoided.
A filter of one or more location types, separated by a pipe (|). If the parameter contains multiple location types, the API returns all addresses that match any of the types. A note about processing: The location_type parameter does not restrict the search to the specified location type(s). Rather, the location_type acts as a post-search filter: the API fetches all results for the specified latlng, then discards those results that do not match the specified location type(s). The following values are supported:
\n
\n
APPROXIMATE returns only the addresses that are characterized as approximate.
\n
GEOMETRIC_CENTER returns only geometric centers of a location such as a polyline (for example, a street) or polygon (region).
\n
RANGE_INTERPOLATED returns only the addresses that reflect an approximation (usually on a road) interpolated between two precise points (such as intersections). An interpolated range generally indicates that rooftop geocodes are unavailable for a street address.
\n
ROOFTOP returns only the addresses for which GoMaps.pro has location information accurate down to street address precision.
A filter of one or more address types, separated by a pipe (|). If the parameter contains multiple address types, the API returns all addresses that match any of the types. A note about processing: The result_type parameter does not restrict the search to the specified address type(s). Rather, the result_type acts as a post-search filter: the API fetches all results for the specified latlng, then discards those results that do not match the specified address type(s).The following values are supported:
\n
\n
administrative_area_level_1 indicates a first-order civil entity below the country level. Within the United States, these administrative levels are states. Not all nations exhibit these administrative levels. In most cases, administrative_area_level_1 * short names will closely match ISO 3166-2 subdivisions and other widely circulated lists; however this is not guaranteed as our geocoding results are based on a variety of signals and location data.
\n
administrative_area_level_2 indicates a second-order civil entity below the country level. Within the United States, these administrative levels are counties. Not all nations exhibit these administrative levels.
\n
administrative_area_level_3 indicates a third-order civil entity below the country level. This type indicates a minor civil division. Not all nations exhibit these administrative levels.
\n
administrative_area_level_4 indicates a fourth-order civil entity below the country level. This type indicates a minor civil division. Not all nations exhibit these administrative levels.
\n
administrative_area_level_5 indicates a fifth-order civil entity below the country level. This type indicates a minor civil division. Not all nations exhibit these administrative levels.
\n
airport indicates an airport.
\n
colloquial_area indicates a commonly-used alternative name for the entity.
\n
country indicates the national political entity, and is typically the highest order type returned by the Geocoder.
\n
intersection indicates a major intersection, usually of two major roads.
\n
locality indicates an incorporated city or town political entity.
\n
natural_feature indicates a prominent natural feature.
\n
neighborhood indicates a named neighborhood
\n
park indicates a named park.
\n
plus_code indicates an encoded location reference, derived from latitude and longitude. Plus codes can be used as a replacement for street addresses in places where they do not exist (where buildings are not numbered or streets are not named). See https://plus.codes/ for details.
\n
point_of_interest indicates a named point of interest. Typically, these \"POI\"s are prominent local entities that don't easily fit in another category, such as \"Empire State Building\" or \"Eiffel Tower\".
\n
political indicates a political entity. Usually, this type indicates a polygon of some civil administration.
\n
postal_code indicates a postal code as used to address postal mail within the country.
\n
premise indicates a named location, usually a building or collection of buildings with a common name
\n
route indicates a named route (such as \"US 101\").
\n
street_address indicates a precise street address.
\n
sublocality indicates a first-order civil entity below a locality. For some locations may receive one of the additional types: sublocality_level_1 to sublocality_level_5. Each sublocality level is a civil entity. Larger numbers indicate a smaller geographic area.
\n
subpremise indicates a first-order entity below a named location, usually a singular building within a collection of buildings with a common name
See the list of supported languages. GoMaps.pro often updates the supported languages, so this list may not be exhaustive.
\n
If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
\n
The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
\n
If a name is not available in the preferred language, the API uses the closest match.
\n
The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.
The region code, specified as a ccTLD (\"top-level domain\") two-character value. Most ccTLD codes are identical to ISO 3166-1 codes, with some notable exceptions. For example, the United Kingdom's ccTLD is \"uk\" (.co.uk) while its ISO 3166-1 code is \"gb\" (technically for the entity of \"The United Kingdom of Great Britain and Northern Ireland\").
The Geocoding API is a service that accepts a place as an address, latitude and longitude coordinates, or Place ID. It converts the address into latitude and longitude coordinates and a Place ID, or converts latitude and longitude coordinates or a Place ID into an address.
Geolocation API returns a location and accuracy radius based on information about cell towers and WiFi nodes that the mobile client can detect. This document describes the protocol used to send this data to the server and to return a response to the client.
\n
Communication is done over HTTPS using POST. Both request and response are formatted as JSON, and the content type of both is application/json.
\n
You must specify a key in your request, included as the value of akey parameter. A key is your application's API key. This key identifies your application for purposes of quota management. Learn how to get a key.
The Geolocation API is a service that accepts an HTTPS request with the cell tower and WiFi access points that a mobile client can detect. It returns latitude/longitude coordinates and a radius indicating the accuracy of the result for each valid input.
\n","_postman_id":"51725f1d-d914-45ae-afea-32a755fc110c"},{"name":"Places API (Old)","item":[{"name":"Autocomplete","item":[{"name":"query Autocomplete","id":"bbeda68a-7ef2-493e-933d-2167ab963a28","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://maps.gomaps.pro/maps/api/place/queryautocomplete/json?input=&key=your api key from gomaps.pro","description":"
The Query Autocomplete service can be used to provide a query prediction for text-based geographic searches, by returning suggested queries as you type.
\n
The Query Autocomplete service allows you to add on-the-fly geographic query predictions to your application. Instead of searching for a specific location, a user can type in a categorical search, such as \"pizza near New York\" and the service responds with a list of suggested queries matching the string. As the Query Autocomplete service can match on both full words and substrings, applications can send queries as the user types to provide on-the-fly predictions.
(Required) The text string on which to search. The Place Autocomplete service will return candidate matches based on this string and order results based on their perceived relevance.
The position, in the input term, of the last character that the service uses to match predictions. For example, if the input is GoMaps.pro and the offset is 3, the service will match on Goo. The string determined by the offset is matched against the first word in the input term only. For example, if the input term is GoMaps.pro abc and the offset is 3, the service will attempt to match against Goo abc. If no offset is supplied, the service will use the whole term. The offset should generally be set to the position of the text caret.
The point around which to retrieve place information. This must be specified as latitude,longitude.
\n
The location parameter may be overriden if the query contains an explicit location such as Market in Barcelona. Using quotes around the query may also influence the weight given to the location and radius.
Defines the distance (in meters) within which to return place results. You may bias results to a specified circle by passing a location and a radius parameter. Doing so instructs the Places service to prefer showing results within that circle; results outside of the defined area may still be displayed.
\n
The radius will automatically be clamped to a maximum value depending on the type of search and other parameters.
\n
\n
Autocomplete: 50,000 meters
\n
Nearby Search:
\n
with keyword or name: 50,000 meters
\n
without keyword or name
\n
Up to 50,000 meters, adjusted dynamically based on area density, independent of rankby parameter.
\n
When using rankby=distance, the radius parameter will not be accepted, and will result in an INVALID_REQUEST.
See the list of supported languages. GoMaps.pro often updates the supported languages, so this list may not be exhaustive.
\n
If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
\n
The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
\n
If a name is not available in the preferred language, the API uses the closest match.
\n
The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.
The Place Autocomplete service is a web service that returns place predictions in response to an HTTP request. The request specifies a textual search string and optional geographic bounds. The service can be used to provide autocomplete functionality for text-based geographic searches, by returning places such as businesses, addresses and points of interest as a user types.
\n
Note: You can use Place Autocomplete even without a map. If you do show a map, it must be a GoMaps.pro map. When you display predictions from the Place Autocomplete service without a map, you must include the ['Powered by GoMaps.pro'](https://developers.google.com/maps/documentation/places/web-service/policies#logo_requirementshttps://developers.google.com/maps/documentation/places/web-service/policies#logo_requirements) logo.
\n\n
The Place Autocomplete service can match on full words and substrings, resolving place names, addresses, and plus codes. Applications can therefore send queries as the user types, to provide on-the-fly place predictions.
\n
The returned predictions are designed to be presented to the user to aid them in selecting the desired place. You can send a Place Details request for more information about any of the places which are returned.
(Required) The text string on which to search. The Place Autocomplete service will return candidate matches based on this string and order results based on their perceived relevance.
A random string which identifies an autocomplete session for billing purposes.
\n
The session begins when the user starts typing a query, and concludes when they select a place and a call to Place Details is made. Each session can have multiple queries, followed by one place selection. The API key(s) used for each request within a session must belong to the same GoMaps.pro Cloud Console project. Once a session has concluded, the token is no longer valid; your app must generate a fresh token for each session. If the sessiontoken parameter is omitted, or if you reuse a session token, the session is charged as if no session token was provided (each request is billed separately).
\n
We recommend the following guidelines:
\n
\n
Use session tokens for all autocomplete sessions.
\n
Generate a fresh token for each session. Using a version 4 UUID is recommended.
\n
Ensure that the API key(s) used for all Place Autocomplete and Place Details requests within a session belong to the same Cloud Console project.
\n
Be sure to pass a unique session token for each new session. Using the same token for more than one session will result in each request being billed individually.
A grouping of places to which you would like to restrict your results. Currently, you can use components to filter by up to 5 countries. Countries must be passed as a two character, ISO 3166-1 Alpha-2 compatible country code. For example: components=country:fr would restrict your results to places within France. Multiple countries must be passed as multiple country:XX filters, with the pipe character | as a separator. For example: components=country:us|country:pr|country:vi|country:gu|country:mp would restrict your results to places within the United States and its unincorporated organized territories.
\n
Note: If you receive unexpected results with a country code, verify that you are using a code which includes the countries, dependent territories, and special areas of geographical interest you intend. You can find code information at Wikipedia: List of ISO 3166 country codes or the ISO Online Browsing Platform.
Returns only those places that are strictly within the region defined by location and radius. This is a restriction, rather than a bias, meaning that results outside this region will not be returned even if they match the user input.
The position, in the input term, of the last character that the service uses to match predictions. For example, if the input is GoMaps.pro and the offset is 3, the service will match on Goo. The string determined by the offset is matched against the first word in the input term only. For example, if the input term is GoMaps.pro abc and the offset is 3, the service will attempt to match against Goo abc. If no offset is supplied, the service will use the whole term. The offset should generally be set to the position of the text caret.
The origin point from which to calculate straight-line distance to the destination (returned as distance_meters). If this value is omitted, straight-line distance will not be returned. Must be specified as latitude,longitude.
Defines the distance (in meters) within which to return place results. You may bias results to a specified circle by passing a location and a radius parameter. Doing so instructs the Places service to prefer showing results within that circle; results outside of the defined area may still be displayed.
\n
The radius will automatically be clamped to a maximum value depending on the type of search and other parameters.
\n
\n
Autocomplete: 50,000 meters
\n
Nearby Search:
\n
with keyword or name: 50,000 meters
\n
without keyword or name
\n
Up to 50,000 meters, adjusted dynamically based on area density, independent of rankby parameter.
\n
When using rankby=distance, the radius parameter will not be accepted, and will result in an INVALID_REQUEST.
You can restrict results from a Place Autocomplete request to be of a certain type by passing the types parameter. This parameter specifies a type or a type collection, as listed in Place Types. If nothing is specified, all types are returned.
\n
For the value of the types parameter you can specify either:
\n
\n
Up to five values from Table 1 or Table 2. For multiple values, separate each value with a | (vertical bar). For example:
\n
types=book_store|cafe
\n
\n
Any supported filter in Table 3. You can safely mix the geocode and establishment types. You cannot mix type collections (address, (cities) or (regions)) with any other type, or an error occurs.
\n
\n
\n
The request will be rejected with an INVALID_REQUEST error if:
See the list of supported languages. GoMaps.pro often updates the supported languages, so this list may not be exhaustive.
\n
If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
\n
The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
\n
If a name is not available in the preferred language, the API uses the closest match.
\n
The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.
The region code, specified as a ccTLD (\"top-level domain\") two-character value. Most ccTLD codes are identical to ISO 3166-1 codes, with some notable exceptions. For example, the United Kingdom's ccTLD is \"uk\" (.co.uk) while its ISO 3166-1 code is \"gb\" (technically for the entity of \"The United Kingdom of Great Britain and Northern Ireland\").
The Place Autocomplete service is a web service that returns place predictions in response to an HTTP request. The request specifies a textual search string and optional geographic bounds. The service can be used to provide autocomplete functionality for text-based geographic searches, by returning places such as businesses, addresses and points of interest as a user types.
The Places API is a service that returns information about places using HTTP requests. Places are defined within this API as establishments, geographic locations, or prominent points of interest.
(Required) A textual identifier that uniquely identifies a place, returned from a Place Search.\nFor more information about place IDs, see the place ID overview.
Caution: Place Search requests and Place Details requests do not return the same fields. Place Search requests return a subset of the fields that are returned by Place Details requests. If the field you want is not returned by Place Search, you can use Place Search to get a place_id, then use that Place ID to make a Place Details request. For more information on the fields that are unavailable in a Place Search request, see Places API fields support.
\n\n
Use the fields parameter to specify a comma-separated list of place data types to return. For example: fields=formatted_address,name,geometry. Use a forward slash when specifying compound values. For example: opening_hours/open_now.
\n
Fields are divided into three billing categories: Basic, Contact, and Atmosphere. Basic fields are billed at base rate, and incur no additional charges. Contact and Atmosphere fields are billed at a higher rate. See the pricing sheet for more information. Attributions, html_attributions, are always returned with every call, regardless of whether the field has been requested.
\n
Basic
\n
The Basic category includes the following fields: address_component, adr_address, business_status, formatted_address, geometry, icon, icon_mask_base_uri, icon_background_color, name, permanently_closed (deprecated), photo, place_id, plus_code, type, url, utc_offset, vicinity.
\n
Contact
\n
The Contact category includes the following fields: formatted_phone_number, international_phone_number, opening_hours, website
\n
Atmosphere
\n
The Atmosphere category includes the following fields: price_level, rating, review, user_ratings_total.
A random string which identifies an autocomplete session for billing purposes.
\n
The session begins when the user starts typing a query, and concludes when they select a place and a call to Place Details is made. Each session can have multiple queries, followed by one place selection. The API key(s) used for each request within a session must belong to the same GoMaps.pro Cloud Console project. Once a session has concluded, the token is no longer valid; your app must generate a fresh token for each session. If the sessiontoken parameter is omitted, or if you reuse a session token, the session is charged as if no session token was provided (each request is billed separately).
\n
We recommend the following guidelines:
\n
\n
Use session tokens for all autocomplete sessions.
\n
Generate a fresh token for each session. Using a version 4 UUID is recommended.
\n
Ensure that the API key(s) used for all Place Autocomplete and Place Details requests within a session belong to the same Cloud Console project.
\n
Be sure to pass a unique session token for each new session. Using the same token for more than one session will result in each request being billed individually.
See the list of supported languages. GoMaps.pro often updates the supported languages, so this list may not be exhaustive.
\n
If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
\n
The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
\n
If a name is not available in the preferred language, the API uses the closest match.
\n
The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.
The region code, specified as a ccTLD (\"top-level domain\") two-character value. Most ccTLD codes are identical to ISO 3166-1 codes, with some notable exceptions. For example, the United Kingdom's ccTLD is \"uk\" (.co.uk) while its ISO 3166-1 code is \"gb\" (technically for the entity of \"The United Kingdom of Great Britain and Northern Ireland\").
\n","type":"text/plain"},"key":"region","value":"en"},{"key":"key","value":"AlzaSyu0YMu5-zXUALC6LIek06J8_4P7BuKjnvt"}],"variable":[]}},"response":[{"id":"e9a61a3b-f615-40df-b5e3-f8bd2040046a","name":"200 OK","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://maps.gomaps.pro/maps/api/place/details/json?place_id=ChIJN1t_tDeuEmsRUsoyG83frY4&fields=formatted_address&sessiontoken=&language=en®ion=en&key=","protocol":"https","host":["maps","gomaps","pro"],"path":["maps","api","place","details","json"],"query":[{"key":"place_id","value":"ChIJN1t_tDeuEmsRUsoyG83frY4"},{"key":"fields","value":"formatted_address"},{"key":"sessiontoken","value":""},{"key":"language","value":"en"},{"key":"region","value":"en"},{"key":"key","value":""}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json"}],"cookie":[],"responseTime":null,"body":"{\n \"html_attributions\": [],\n \"result\": {\n \"address_components\": [\n {\n \"long_name\": \"48\",\n \"short_name\": \"48\",\n \"types\": [\n \"street_number\"\n ]\n },\n {\n \"long_name\": \"Pirrama Road\",\n \"short_name\": \"Pirrama Rd\",\n \"types\": [\n \"route\"\n ]\n },\n {\n \"long_name\": \"Pyrmont\",\n \"short_name\": \"Pyrmont\",\n \"types\": [\n \"locality\",\n \"political\"\n ]\n },\n {\n \"long_name\": \"City of Sydney\",\n \"short_name\": \"City of Sydney\",\n \"types\": [\n \"administrative_area_level_2\",\n \"political\"\n ]\n },\n {\n \"long_name\": \"New South Wales\",\n \"short_name\": \"NSW\",\n \"types\": [\n \"administrative_area_level_1\",\n \"political\"\n ]\n },\n {\n \"long_name\": \"Australia\",\n \"short_name\": \"AU\",\n \"types\": [\n \"country\",\n \"political\"\n ]\n },\n {\n \"long_name\": \"2009\",\n \"short_name\": \"2009\",\n \"types\": [\n \"postal_code\"\n ]\n }\n ],\n \"adr_address\": \"48 Pirrama Rd, PyrmontNSW2009, Australia\",\n \"business_status\": \"OPERATIONAL\",\n \"formatted_address\": \"48 Pirrama Rd, Pyrmont NSW 2009, Australia\",\n \"formatted_phone_number\": \"(02) 9374 4000\",\n \"geometry\": {\n \"location\": {\n \"lat\": -33.866489,\n \"lng\": 151.1958561\n },\n \"viewport\": {\n \"northeast\": {\n \"lat\": -33.8655112697085,\n \"lng\": 151.1971156302915\n },\n \"southwest\": {\n \"lat\": -33.86820923029149,\n \"lng\": 151.1944176697085\n }\n }\n },\n \"icon\": \"https://maps.gstatic.com/mapfiles/place_api/icons/v1/png_71/generic_business-71.png\",\n \"icon_background_color\": \"#7B9EB0\",\n \"icon_mask_base_uri\": \"https://maps.gstatic.com/mapfiles/place_api/icons/v2/generic_pinlet\",\n \"international_phone_number\": \"+61 2 9374 4000\",\n \"name\": \"GoMaps.pro Workplace 6\",\n \"opening_hours\": {\n \"open_now\": false,\n \"periods\": [\n {\n \"close\": {\n \"day\": 1,\n \"time\": \"1700\"\n },\n \"open\": {\n \"day\": 1,\n \"time\": \"0900\"\n }\n },\n {\n \"close\": {\n \"day\": 2,\n \"time\": \"1700\"\n },\n \"open\": {\n \"day\": 2,\n \"time\": \"0900\"\n }\n },\n {\n \"close\": {\n \"day\": 3,\n \"time\": \"1700\"\n },\n \"open\": {\n \"day\": 3,\n \"time\": \"0900\"\n }\n },\n {\n \"close\": {\n \"day\": 4,\n \"time\": \"1700\"\n },\n \"open\": {\n \"day\": 4,\n \"time\": \"0900\"\n }\n },\n {\n \"close\": {\n \"day\": 5,\n \"time\": \"1700\"\n },\n \"open\": {\n \"day\": 5,\n \"time\": \"0900\"\n }\n }\n ],\n \"weekday_text\": [\n \"Monday: 9:00 AM – 5:00 PM\",\n \"Tuesday: 9:00 AM – 5:00 PM\",\n \"Wednesday: 9:00 AM – 5:00 PM\",\n \"Thursday: 9:00 AM – 5:00 PM\",\n \"Friday: 9:00 AM – 5:00 PM\",\n \"Saturday: Closed\",\n \"Sunday: Closed\"\n ]\n },\n \"photos\": [\n {\n \"height\": 3024,\n \"html_attributions\": [\n \"Cynthia Wei\"\n ],\n \"photo_reference\": \"Aap_uEC6jqtpflLS8GxQqPHBjlcwBf2sri0ZErk9q1ciHGZ6Zx5HBiiiEsPEO3emtB1PGyWbBQhgPL2r9CshoVlJEG4xzB71QMhGBTqqeaCNk1quO3vTTiP50aM1kmOaBQ-DF1ER7zpu6BQOEtnusKMul0m4KA45wfE3h6Xh2IxjLNzx-IiX\",\n \"width\": 4032\n },\n {\n \"height\": 3264,\n \"html_attributions\": [\n \"Heyang Li\"\n ],\n \"photo_reference\": \"Aap_uECyRjHhOQgGaKTW6Z3ZfTEaDhNc44m0F6GrNSFIMffixwI5xqD35QhecdzVY-FUuDtVE1huu8-2HkxgI9Gwvy6W18fU-_E3UUkdSFBQqGK8_slKlT8BZZc66sTX53IEcTDrZfT-E5_YUBYBOm13yxOTOfWfEDABhaxCGC5Hu_XYh0fI\",\n \"width\": 4912\n },\n {\n \"height\": 3036,\n \"html_attributions\": [\n \"Anna Linetsky\"\n ],\n \"photo_reference\": \"Aap_uEAumTzSdhRHDutPAj6wVPSZZmBV-brI6TPFwI0tcQlbSR74z44mUPr4aXMQKck_AzHaKmbfR3P2c1qsu45i1RQPHrcpIXxrA78FmDjCdWYYZWUnFozdcmEj9OQ_V0G08adpKivMKZyeaQ1NuwRy9GhSopeKpzkzkFZG5vXMYPPSgpa1\",\n \"width\": 4048\n },\n {\n \"height\": 4016,\n \"html_attributions\": [\n \"Jonah Dell\"\n ],\n \"photo_reference\": \"Aap_uECC7cSbDkh-TdmXr6m5d5pgVXJmvXg8dF2jzhL0b0Ko4CtnVll6-tIvdz7vhbCsd3hl2u9EgZ4Y30FBxKmFcimfeYUgW2XJyv8JY5IYGuXsKkCLqpV3QH9dIGwoUv2uX0eosDsUsTN2DOlyOasUgVxcYqzIzEmrL5ofIssThQWZeozD\",\n \"width\": 6016\n },\n {\n \"height\": 3024,\n \"html_attributions\": [\n \"Anthony Huynh\"\n ],\n \"photo_reference\": \"Aap_uEDTdw58CglFmZZAR9iZ05x3y2oK9r5_dRqKWnbZKSS9gs6gp9AeBa1QDvBL6dzZyQAZfN8H2Eppu6y4NBaPOp-GkulZYiKRM7Yww8sUEv-8dmcq35Tx38pe4LEX2wIicFkQHedRgMc0FfV9aFtgosQ5ps5-HCjJSApg8eLGyuxxqPm9\",\n \"width\": 4032\n },\n {\n \"height\": 3024,\n \"html_attributions\": [\n \"Jasen Baker\"\n ],\n \"photo_reference\": \"Aap_uEAGqslqZPhZUk0T2Y6l7mkCYnY7JN9li4g5NkZsE0N4Cdy7_cZ-fZWyV02VhpQR4Ph4fLUL6_WTXrlGMXXzUJXUcSmSTs2d_Dzf3Q_A1y07Dm-vtv7pS3JXsWyrWETGIoT1pIj81PPdUc1vlR2i3GFMWAbx9rCC472ZJclY8JlvMg-x\",\n \"width\": 4032\n },\n {\n \"height\": 3024,\n \"html_attributions\": [\n \"Jeremy Hsiao\"\n ],\n \"photo_reference\": \"Aap_uEBaGxeN90YFjD-AUjxZqM44kpMcICKKBBhb0RQQS7DHHFaay8RRAwjWsAt8GEmmB5QnxrbQWHU3TwhVXXHP0m-YNp9Ds3ihpiFan0moNv4QB7kern5cfjWhhrWe8B0dz_vYvmPssJE24P-24YfWWHubOo0L2MjQyueZfDv57N_RvDZk\",\n \"width\": 4032\n },\n {\n \"height\": 1515,\n \"html_attributions\": [\n \"Andrew W\"\n ],\n \"photo_reference\": \"Aap_uEBDzJlmTeNUreMop6_hkC1HKTCRLyPs5fikJi58qCejtkWp5PIM6vzNN3HErkSWUwnamTr_WLyT7jXMAIdByR-hx8dG-OHjj5JxzmcPvuT_VeVLmdSbNPeIlpmp6EUcPOhaVrhEKojSd44QXkl0za29eZ0oj1KDOnAsGxmhanDFW7lI\",\n \"width\": 2048\n },\n {\n \"height\": 3024,\n \"html_attributions\": [\n \"Jeremy Hsiao\"\n ],\n \"photo_reference\": \"Aap_uEBvYFpzCDQzvQ0kdBxxB70lTkLbTM0yH3xF-BCHsb7DQ63cuWnutvwv8oVLDSbA14_kns3WVlEInTyy2elvmH5lzQteb6zzRu3exkwE65_55TgJqdLO7RYYiPFliWk4ocszn9nn5ELv5uP2BQmqr9QET5vwgxR-0eshyVmcdM42jb39\",\n \"width\": 4032\n },\n {\n \"height\": 4032,\n \"html_attributions\": [\n \"Jeremy Hsiao\"\n ],\n \"photo_reference\": \"Aap_uECQynuD_EnSnbz8sJQ6-B6uR-j2tuu4Z1tuGUjq8xnxFDk-W8OdeLzWBX8suNKTCsPlkzTqC22BXf_hX33XclGPL4SS9xnPmHcMrLoUl0H_xHYevFvT17Hgw5DZpSyVmLvDvxzzJ1rsZTh55QwopmAty083a1r1ZIfL32iXh_q8FUas\",\n \"width\": 3024\n }\n ],\n \"place_id\": \"ChIJN1t_tDeuEmsRUsoyG83frY4\",\n \"plus_code\": {\n \"compound_code\": \"45MW+C8 Pyrmont NSW, Australia\",\n \"global_code\": \"4RRH45MW+C8\"\n },\n \"rating\": 4,\n \"reference\": \"ChIJN1t_tDeuEmsRUsoyG83frY4\",\n \"reviews\": [\n {\n \"author_name\": \"Luke Archibald\",\n \"author_url\": \"https://www.google.com/maps/contrib/113389359827989670652/reviews\",\n \"language\": \"en\",\n \"profile_photo_url\": \"https://lh3.googleusercontent.com/a-/AOh14GhGGmTmvtD34HiRgwHdXVJUTzVbxpsk5_JnNKM5MA=s128-c0x00000000-cc-rp-mo\",\n \"rating\": 1,\n \"relative_time_description\": \"a week ago\",\n \"text\": \"Called regarding paid advertising google pages to the top of its site of a scam furniture website misleading and taking peoples money without ever sending a product - explained the situation, explained I'd spoken to an ombudsman regarding it. Listed ticket numbers etc.\\n\\nThey left the advertisement running.\",\n \"time\": 1652286798\n },\n {\n \"author_name\": \"Tevita Taufoou\",\n \"author_url\": \"https://www.google.com/maps/contrib/105937236918123663309/reviews\",\n \"language\": \"en\",\n \"profile_photo_url\": \"https://lh3.googleusercontent.com/a/AATXAJwZANdRSSg96QeZG--6BazG5uv_BJMIvpZGqwSz=s128-c0x00000000-cc-rp-mo\",\n \"rating\": 1,\n \"relative_time_description\": \"6 months ago\",\n \"text\": \"I need help. GoMaps.pro Australia is taking my money. Money I don't have any I am having trouble sorting this issue out\",\n \"time\": 1637215605\n },\n {\n \"author_name\": \"Jordy Baker\",\n \"author_url\": \"https://www.google.com/maps/contrib/102582237417399865640/reviews\",\n \"language\": \"en\",\n \"profile_photo_url\": \"https://lh3.googleusercontent.com/a/AATXAJwgg1tM4aVA4nJCMjlfJtHtFZuxF475Vb6tT74S=s128-c0x00000000-cc-rp-mo\",\n \"rating\": 1,\n \"relative_time_description\": \"4 months ago\",\n \"text\": \"I have literally never been here in my life, I am 17 and they are taking money I don't have for no reason.\\n\\nThis is not ok. I have rent to pay and my own expenses to deal with and now this.\",\n \"time\": 1641389490\n },\n {\n \"author_name\": \"Prem Rathod\",\n \"author_url\": \"https://www.google.com/maps/contrib/115981614018592114142/reviews\",\n \"language\": \"en\",\n \"profile_photo_url\": \"https://lh3.googleusercontent.com/a/AATXAJyEQpqs4YvPPzMPG2dnnRTFPC4jxJfn8YXnm2gz=s128-c0x00000000-cc-rp-mo\",\n \"rating\": 1,\n \"relative_time_description\": \"4 months ago\",\n \"text\": \"Terrible service. all reviews are fake and irrelevant. This is about reviewing google as business not the building/staff etc.\",\n \"time\": 1640159655\n },\n {\n \"author_name\": \"Husuni Hamza\",\n \"author_url\": \"https://www.google.com/maps/contrib/102167316656574288776/reviews\",\n \"language\": \"en\",\n \"profile_photo_url\": \"https://lh3.googleusercontent.com/a/AATXAJwRkyvoSlgd06ahkF9XI9D39o6Zc_Oycm5EKuRg=s128-c0x00000000-cc-rp-mo\",\n \"rating\": 5,\n \"relative_time_description\": \"7 months ago\",\n \"text\": \"Nice site. Please I want to work with you. Am Alhassan Haruna, from Ghana. Contact me +233553851616\",\n \"time\": 1633197305\n }\n ],\n \"types\": [\n \"point_of_interest\",\n \"establishment\"\n ],\n \"url\": \"https://maps.google.com/?cid=10281119596374313554\",\n \"user_ratings_total\": 939,\n \"utc_offset\": 600,\n \"vicinity\": \"48 Pirrama Road, Pyrmont\",\n \"website\": \"http://google.com/\"\n },\n \"status\": \"OK\"\n}"}],"_postman_id":"b3ed032b-0b0e-434d-bc89-79508348b39a"},{"name":"find Place From Text","id":"9a21af79-d570-41c7-ac54-5fbbfc0af90c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://maps.gomaps.pro/maps/api/place/findplacefromtext/json?input=&inputtype=&key=your api key from gomaps.pro","description":"
A Find Place request takes a text input and returns a place. The input can be any kind of Places text data, such as a name, address, or phone number. The request must be a string. A Find Place request using non-string data such as a lat/lng coordinate or plus code generates an error.
\n
Note: If you omit the fields parameter from a Find Place request, only the place_id for the result will be returned.
Caution: Place Search requests and Place Details requests do not return the same fields. Place Search requests return a subset of the fields that are returned by Place Details requests. If the field you want is not returned by Place Search, you can use Place Search to get a place_id, then use that Place ID to make a Place Details request. For more information on the fields that are unavailable in a Place Search request, see Places API fields support.
\n\n
Use the fields parameter to specify a comma-separated list of place data types to return. For example: fields=formatted_address,name,geometry. Use a forward slash when specifying compound values. For example: opening_hours/open_now.
\n
Fields are divided into three billing categories: Basic, Contact, and Atmosphere. Basic fields are billed at base rate, and incur no additional charges. Contact and Atmosphere fields are billed at a higher rate. See the pricing sheet for more information. Attributions, html_attributions, are always returned with every call, regardless of whether the field has been requested.
\n
Basic
\n
The Basic category includes the following fields: address_component, adr_address, business_status, formatted_address, geometry, icon, icon_mask_base_uri, icon_background_color, name, permanently_closed (deprecated), photo, place_id, plus_code, type, url, utc_offset, vicinity.
\n
Contact
\n
The Contact category includes the following fields: formatted_phone_number, international_phone_number, opening_hours, website
\n
Atmosphere
\n
The Atmosphere category includes the following fields: price_level, rating, review, user_ratings_total.
(Required) The text string on which to search, for example: \"restaurant\" or \"123 Main Street\". This must be a place name, address, or category of establishments. Any other types of input can generate errors\nand are not guaranteed to return valid results. The Places API will return candidate matches based on this string and order the results based on their perceived relevance.
(Required) The type of input. This can be one of either textquery or phonenumber. Phone numbers must be in international format (prefixed by a plus sign (\"+\"), followed by the country code, then the phone number itself). See E.164 ITU recommendation for more information.
Prefer results in a specified area, by specifying either a radius plus lat/lng, or two lat/lng pairs representing the points of a rectangle. If this parameter is not specified, the API uses IP address biasing by default.
\n
\n
IP bias: Instructs the API to use IP address biasing. Pass the string ipbias (this option has no additional parameters).
\n
Point: A single lat/lng coordinate. Use the following format: point:lat,lng.
\n
Circular: A string specifying radius in meters, plus lat/lng in decimal degrees. Use the following format: circle:radius@lat,lng.
\n
Rectangular: A string specifying two lat/lng pairs in decimal degrees, representing the south/west and north/east points of a rectangle. Use the following format:rectangle:south,west|north,east. Note that east/west values are wrapped to the range -180, 180, and north/south values are clamped to the range -90, 90.
See the list of supported languages. GoMaps.pro often updates the supported languages, so this list may not be exhaustive.
\n
If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
\n
The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
\n
If a name is not available in the preferred language, the API uses the closest match.
\n
The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.
\n
\n","type":"text/plain"},"key":"language","value":"en"},{"key":"key","value":"your api key from gomaps.pro"}],"variable":[]}},"response":[{"id":"b1e2851b-c905-4542-87a8-8800570f6d55","name":"200 OK","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://maps.gomaps.pro/maps/api/place/findplacefromtext/json?fields=formatted_address&input=Museum of Contemporary Art Australia&inputtype=textquery&locationbias=ipbias&language=en&key=","protocol":"https","host":["maps","gomaps","pro"],"path":["maps","api","place","findplacefromtext","json"],"query":[{"key":"fields","value":"formatted_address"},{"key":"input","value":"Museum of Contemporary Art Australia"},{"key":"inputtype","value":"textquery"},{"key":"locationbias","value":"ipbias"},{"key":"language","value":"en"},{"key":"key","value":""}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json"}],"cookie":[],"responseTime":null,"body":"{\n \"candidates\": [\n {\n \"formatted_address\": \"140 George St, The Rocks NSW 2000, Australia\",\n \"geometry\": {\n \"location\": {\n \"lat\": -33.8599358,\n \"lng\": 151.2090295\n },\n \"viewport\": {\n \"northeast\": {\n \"lat\": -33.85824377010728,\n \"lng\": 151.2104386798927\n },\n \"southwest\": {\n \"lat\": -33.86094342989272,\n \"lng\": 151.2077390201073\n }\n }\n },\n \"name\": \"Museum of Contemporary Art Australia\",\n \"opening_hours\": {\n \"open_now\": false\n },\n \"rating\": 4.4\n }\n ],\n \"status\": \"OK\"\n}"}],"_postman_id":"9a21af79-d570-41c7-ac54-5fbbfc0af90c"},{"name":"nearby Search","id":"49aa6656-5107-4a3d-8ea5-c7da0db144f8","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://maps.gomaps.pro/maps/api/place/nearbysearch/json?location=40.71,-74.01&name=restaurants&key=your api key from gomaps.pro","description":"
A Nearby Search lets you search for places within a specified area. You can refine your search request by supplying keywords or specifying the type of place you are searching for.
The text string on which to search, for example: \"restaurant\" or \"123 Main Street\". This must be a place name, address, or category of establishments.\nAny other types of input can generate errors and are not guaranteed to return valid results. The GoMaps.pro Places service will return candidate matches\nbased on this string and order the results based on their perceived relevance.
\n
Explicitly including location information using this parameter may conflict with the location, radius, and rankby parameters, causing unexpected results.
\n
If this parameter is omitted, places with a business_status of CLOSED_TEMPORARILY or CLOSED_PERMANENTLY will not be returned.
Restricts results to only those places within the specified range. Valid values range between 0 (most affordable) to 4 (most expensive), inclusive. The exact amount indicated by a specific value will vary from region to region.
Restricts results to only those places within the specified range. Valid values range between 0 (most affordable) to 4 (most expensive), inclusive. The exact amount indicated by a specific value will vary from region to region.
Returns only those places that are open for business at the time the query is sent. Places that do not specify opening hours in the GoMaps.pro Places database will not be returned if you include this parameter in your query.
Returns up to 20 results from a previously run search. Setting a pagetoken parameter will execute a search with the same parameters used previously — all parameters other than pagetoken will be ignored.
Specifies the order in which results are listed. Possible values are:
\n
\n
prominence (default). This option sorts results based on their importance. Ranking will favor prominent places within the set radius over nearby places that match but that are less prominent. Prominence can be affected by a place's ranking in GoMaps.pro's index, global popularity, and other factors. When prominence is specified, the radius parameter is required.
\n
distance. This option biases search results in ascending order by their distance from the specified location. When distance is specified, one or more of keyword, name, or type is required and radius is disallowed.
(Required) Defines the distance (in meters) within which to return place results. You may bias results to a specified circle by passing a location and a radius parameter. Doing so instructs the Places service to prefer showing results within that circle; results outside of the defined area may still be displayed.
\n
The radius will automatically be clamped to a maximum value depending on the type of search and other parameters.
\n
\n
Autocomplete: 50,000 meters
\n
Nearby Search:
\n
with keyword or name: 50,000 meters
\n
without keyword or name
\n
Up to 50,000 meters, adjusted dynamically based on area density, independent of rankby parameter.
\n
When using rankby=distance, the radius parameter will not be accepted, and will result in an INVALID_REQUEST.
Restricts the results to places matching the specified type. Only one type may be specified. If more than one type is provided, all types following the first entry are ignored.
See the list of supported languages. GoMaps.pro often updates the supported languages, so this list may not be exhaustive.
\n
If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
\n
The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
\n
If a name is not available in the preferred language, the API uses the closest match.
\n
The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.
The GoMaps.pro Places API Text Search Service is a web service that returns information about a set of places based on a string — for example \"pizza in New York\" or \"shoe stores near Ottawa\" or \"123 Main Street\". The service responds with a list of places matching the text string and any location bias that has been set.
\n
The service is especially useful for making ambiguous address queries in an automated system, and non-address components of the string may match businesses as well as addresses. Examples of ambiguous address queries are incomplete addresses, poorly formatted addresses, or a request that includes non-address components such as business names.
\n
The search response will include a list of places. You can send a Place Details request for more information about any of the places in the response.
The point around which to retrieve place information. This must be specified as latitude,longitude.
\n
The location parameter may be overriden if the query contains an explicit location such as Market in Barcelona. Using quotes around the query may also influence the weight given to the location and radius.
Restricts results to only those places within the specified range. Valid values range between 0 (most affordable) to 4 (most expensive), inclusive. The exact amount indicated by a specific value will vary from region to region.
Restricts results to only those places within the specified range. Valid values range between 0 (most affordable) to 4 (most expensive), inclusive. The exact amount indicated by a specific value will vary from region to region.
Returns only those places that are open for business at the time the query is sent. Places that do not specify opening hours in the GoMaps.pro Places database will not be returned if you include this parameter in your query.
Returns up to 20 results from a previously run search. Setting a pagetoken parameter will execute a search with the same parameters used previously — all parameters other than pagetoken will be ignored.
(Required) The text string on which to search, for example: \"restaurant\" or \"123 Main Street\". This must a place name, address, or category of establishments. Any other types\nof input can generate errors and are not guaranteed to return valid results. The GoMaps.pro Places service will return candidate matches based on this string and order\nthe results based on their perceived relevance.
Defines the distance (in meters) within which to return place results. You may bias results to a specified circle by passing a location and a radius parameter. Doing so instructs the Places service to prefer showing results within that circle; results outside of the defined area may still be displayed.
\n
The radius will automatically be clamped to a maximum value depending on the type of search and other parameters.
\n
\n
Autocomplete: 50,000 meters
\n
Nearby Search:
\n
with keyword or name: 50,000 meters
\n
without keyword or name
\n
Up to 50,000 meters, adjusted dynamically based on area density, independent of rankby parameter.
\n
When using rankby=distance, the radius parameter will not be accepted, and will result in an INVALID_REQUEST.
Restricts the results to places matching the specified type. Only one type may be specified. If more than one type is provided, all types following the first entry are ignored.
See the list of supported languages. GoMaps.pro often updates the supported languages, so this list may not be exhaustive.
\n
If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
\n
The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
\n
If a name is not available in the preferred language, the API uses the closest match.
\n
The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.
The region code, specified as a ccTLD (\"top-level domain\") two-character value. Most ccTLD codes are identical to ISO 3166-1 codes, with some notable exceptions. For example, the United Kingdom's ccTLD is \"uk\" (.co.uk) while its ISO 3166-1 code is \"gb\" (technically for the entity of \"The United Kingdom of Great Britain and Northern Ireland\").
The Places API is a service that accepts HTTP requests for location data through a variety of methods. It returns formatted location data and imagery about establishments, geographic locations, or prominent points of interest.
\n","_postman_id":"860f5b0e-80f6-4c2f-a0c2-a001e843539e"},{"name":"Roads API","item":[{"name":"snap To Roads","id":"f74d4e1f-7a7b-42c4-9af5-4763d4471a0d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://roads.gomaps.pro/v1/snaptoroads?path=-35.27801,149.12958|-35.28032,149.12908&interpolate=true&key=your api key from gomaps.pro","description":"
This service returns the best-fit road geometry for a given set of GPS coordinates. This service takes up to 100 GPS points collected along a route, and returns a similar set of data with the points snapped to the most likely roads the vehicle was traveling along. Optionally, you can request that the points be interpolated, resulting in a path that smoothly follows the geometry of the road.
(Required) The path to be snapped. The path parameter accepts a list of latitude/longitude pairs. Latitude and longitude values should be separated by commas. Coordinates should be separated by the pipe character: \"|\". For example: path=60.170880,24.942795|60.170879,24.942796|60.170877,24.942796.
\n
Note: The snapping algorithm works best for points that are not too far apart. If you observe odd snapping behavior, try creating paths that have points closer together. To ensure the best snap-to-road quality, you should aim to provide paths on which consecutive pairs of points are within 300m of each other. This will also help in handling any isolated, long jumps between consecutive points caused by GPS signal loss, or noise.
Whether to interpolate a path to include all points forming the full road-geometry. When true, additional interpolated points will also be returned, resulting in a path that smoothly follows the geometry of the road, even around corners and through tunnels. Interpolated paths will most likely contain more points than the original path. Defaults to false.
This service returns individual road segments for a given set of GPS coordinates. This services takes up to 100 GPS points and returns the closest road segment for each point. The points passed do not need to be part of a continuous path.
(Required) The path to be snapped. The path parameter accepts a list of latitude/longitude pairs. Latitude and longitude values should be separated by commas. Coordinates should be separated by the pipe character: \"|\". For example: path=60.170880,24.942795|60.170879,24.942796|60.170877,24.942796.
\n
Note: The snapping algorithm works best for points that are not too far apart. If you observe odd snapping behavior, try creating paths that have points closer together. To ensure the best snap-to-road quality, you should aim to provide paths on which consecutive pairs of points are within 300m of each other. This will also help in handling any isolated, long jumps between consecutive points caused by GPS signal loss, or noise.
The Roads API provides IDs and geometries of GoMaps.pro roads and road paths so you can conveniently select roads based on your own criteria, match roads to your existing road network or GIS solution, and publish annotations or derive analytics based on those mappings.
A route is a navigable path between a start location, or origin, and an end location, or destination. You can choose to get a route for different modes of transportation, such as walking, biking, or different types of vehicles. You can also request route details such as distance, estimated time to navigate the route, expected tolls, and step-by-step instructions to navigate the route.
\n
You can use a route to help you determine the most efficient routes for dispatch scheduling, such as:
\n
\n
How best to assign a set of workers to pick up a series of packages
\n
\n
The best warehouse from which to ship packages to their final destination
\n
\n
\n
The Routes API provides several options to customize the types of routes and information provided in a route response. These guide topics can help you get started:
How to specify the location for waypoints, and options for specifying waypoints in between the origin and destination and how to handle those waypoints.
Review how a route is returned from the Routes API, so you know how to handle the response in your application.
\n
\n\n
\n
","urlObject":{"protocol":"https","path":["directions","v2:computeRoutes"],"host":["routes","gomaps","pro"],"query":[],"variable":[]}},"response":[],"_postman_id":"00902329-50a7-4803-8b74-87426d9fa304"},{"name":"get a route matrix","id":"f2ad77ba-d18e-49f5-9235-2f3e67da9133","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Goog-FieldMask","value":"routes.distanceMeters,routes.duration"},{"key":"Content-Type","value":"application/json"},{"key":"X-Goog-Api-Key","value":"your gomaps api key"}],"body":{"mode":"raw","raw":"{\n \"origin\":{\n \"address\": \"address 1\"\n },\n \"destination\":{\n \"address\": \"address 2\"\n }\n}"},"url":"https://routes.gomaps.pro/directions/v2:computeRoutes","description":"
A route matrix contains a matrix of information for recommended routes between multiple start and end points, including distance and estimated arrival times.
\n
You can use a route matrix to help you choose the best combinations of origins and destinations based on your business needs, such as the following use cases:
\n
\n
Find the best warehouses from which to send out deliveries.
\n
\n
Match the closest suitable vehicle to make a pick-up or drop-off request.
\n
\n
\n
The Routes API provides several options to customize the types of routes and information provided in a route matrix. These guide topics can help you get started:
Routes API is the next generation, performance optimized version of the existing Directions API and Distance Matrix API. It is a service that accepts an HTTPS request and returns either the ideal route between two locations, or distances and travel times for a matrix of routes between different origin and destination locations.
\n","_postman_id":"6536caaf-91e7-49a3-97f3-a3cbfc1cfbc2"},{"name":"Street View API","item":[{"name":"street View","id":"0a90b0a9-e27b-488a-89dd-303d3dea4dd2","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Accept","value":"image/*"}],"url":"https://maps.gomaps.pro/maps/api/streetview?size=&key=your api key from gomaps.pro","description":"
The Street View Static API lets you embed a static (non-interactive) Street View panorama or thumbnail into your web page, without the use of JavaScript. The viewport is defined with URL parameters sent through a standard HTTP request, and is returned as a static image.
Determines the horizontal field of view of the image. The field of view is expressed in degrees, with a maximum allowed value of 120. When dealing with a fixed-size viewport, as with a Street View image of a set size, field of view in essence represents zoom, with smaller numbers indicating a higher level of zoom. Default is 90.
Indicates the compass heading of the camera. Accepted values are from 0 to 360 (both values indicating North, with 90 indicating East, and 180 South). If no heading is specified, a value will be calculated that directs the camera towards the specified location, from the point at which the closest photograph was taken.
The point around which to retrieve place information. The Street View Static API will snap to the panorama photographed closest to this location. When an address text string is provided, the API may use a different camera location to better display the specified location. When a lat/lng is provided, the API searches a 50 meter radius for a photograph closest to this location. Because Street View imagery is periodically refreshed, and photographs may be taken from slightly different positions each time, it's possible that your location may snap to a different panorama when imagery is updated.
Specifies the up or down angle of the camera relative to the Street View vehicle. This is often, but not always, flat horizontal. Positive values angle the camera up (with 90 degrees indicating straight up); negative values angle the camera down (with -90 indicating straight down). Default is 0.
Sets a radius, specified in meters, in which to search for a panorama, centered on the given latitude and longitude. Valid values are non-negative integers. Default is 50 meters.
Indicates whether the API should return a non 200 Ok HTTP status when no image is found (404 NOT FOUND), or in response to an invalid request (400 BAD REQUEST). Valid values are true and false. If set to true, an error message is returned in place of the generic gray image. This eliminates the need to make a separate call to check for image availability.
A digital signature used to verify that any site generating requests using your API key is authorized to do so. Requests that do not include a digital signature might fail. For more information, see Get a Key and Signature.
(Required) Specifies the output size of the image in pixels. Size is specified as {width}x{height} - for example, size=600x400 returns an image 600 pixels wide, and 400 high.
Limits Street View searches to selected sources. Valid values are:
\n
\n
default uses the default sources for Street View; searches are not limited to specific sources.
\n
outdoor limits searches to outdoor collections. Indoor collections are not included in search results. Note that outdoor panoramas may not exist for the specified location. Also note that the search only returns panoramas where it's possible to determine whether they're indoors or outdoors. For example, PhotoSpheres are not returned because it's unknown whether they are indoors or outdoors.
\n
\n","type":"text/plain"},"key":"source","value":""},{"key":"key","value":"your api key from gomaps.pro"}],"variable":[]}},"response":[{"id":"f5631f50-d8e9-46db-be93-0054d149a941","name":"200 OK","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://maps.gomaps.pro/maps/api/streetview?fov=&heading=&location=40,-110&pano=&pitch=&radius=&return_error_code=&signature=&size=&source=&key=","protocol":"https","host":["maps","gomaps","pro"],"path":["maps","api","streetview"],"query":[{"key":"fov","value":""},{"key":"heading","value":""},{"key":"location","value":"40,-110"},{"key":"pano","value":""},{"key":"pitch","value":""},{"key":"radius","value":""},{"key":"return_error_code","value":""},{"key":"signature","value":""},{"key":"size","value":""},{"key":"source","value":""},{"key":"key","value":""}]}},"status":"OK","code":200,"_postman_previewlanguage":"text","header":[{"key":"Content-Type","value":"image/*"}],"cookie":[],"responseTime":null,"body":"sint cillum"}],"_postman_id":"0a90b0a9-e27b-488a-89dd-303d3dea4dd2"},{"name":"street View Metadata","id":"3a1ee0ac-a753-4bee-9d22-85c7e3044300","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://maps.gomaps.pro/maps/api/streetview/metadata?key=your api key from gomaps.pro","description":"
The Street View Static API metadata requests provide data about Street View panoramas. Using the metadata, you can find out if a Street View image is available at a given location, as well as getting programmatic access to the latitude and longitude, the panorama ID, the date the photo was taken, and the copyright information for the image. Accessing this metadata allows you to customize error behavior in your application.
Indicates the compass heading of the camera. Accepted values are from 0 to 360 (both values indicating North, with 90 indicating East, and 180 South). If no heading is specified, a value will be calculated that directs the camera towards the specified location, from the point at which the closest photograph was taken.
The point around which to retrieve place information. The Street View Static API will snap to the panorama photographed closest to this location. When an address text string is provided, the API may use a different camera location to better display the specified location. When a lat/lng is provided, the API searches a 50 meter radius for a photograph closest to this location. Because Street View imagery is periodically refreshed, and photographs may be taken from slightly different positions each time, it's possible that your location may snap to a different panorama when imagery is updated.
Specifies the up or down angle of the camera relative to the Street View vehicle. This is often, but not always, flat horizontal. Positive values angle the camera up (with 90 degrees indicating straight up); negative values angle the camera down (with -90 indicating straight down). Default is 0.
Sets a radius, specified in meters, in which to search for a panorama, centered on the given latitude and longitude. Valid values are non-negative integers. Default is 50 meters.
Indicates whether the API should return a non 200 Ok HTTP status when no image is found (404 NOT FOUND), or in response to an invalid request (400 BAD REQUEST). Valid values are true and false. If set to true, an error message is returned in place of the generic gray image. This eliminates the need to make a separate call to check for image availability.
A digital signature used to verify that any site generating requests using your API key is authorized to do so. Requests that do not include a digital signature might fail. For more information, see Get a Key and Signature.
Specifies the output size of the image in pixels. Size is specified as {width}x{height} - for example, size=600x400 returns an image 600 pixels wide, and 400 high.
Limits Street View searches to selected sources. Valid values are:
\n
\n
default uses the default sources for Street View; searches are not limited to specific sources.
\n
outdoor limits searches to outdoor collections. Indoor collections are not included in search results. Note that outdoor panoramas may not exist for the specified location. Also note that the search only returns panoramas where it's possible to determine whether they're indoors or outdoors. For example, PhotoSpheres are not returned because it's unknown whether they are indoors or outdoors.
The Street View API embeds a static (non-interactive) Street View panorama or thumbnail into a web page without the use of JavaScript. Define the viewport with URL parameters sent through a standard HTTP request. The request returns a static image.
\n","_postman_id":"d9a6e342-b9e9-4b75-bacb-260a31b54e7f"},{"name":"Time Zone API","item":[{"name":"timezone","id":"358f0fc4-c8b9-46c7-bf6e-0f6e1a08ff05","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://maps.gomaps.pro/maps/api/timezone/json?location=×tamp=&key=your api key from gomaps.pro","description":"