Do I need a Google API key to use ProMaps?
NEW: June 11th 2018
Yes. While Google used to permit "keyless" usage in a variety of situations, starting on June 11th 2018, "you’ll need to enable billing with a credit card and have a valid API key for all projects."
Some map services will still work without an API key but not well. Here are the details from Google's announcement:
Fortunately, you'll likely never incur any actual charges on your Google Maps API key: along with requiring an API key, Google is also allowing $200 in free billing credits per month. This means most users will never incur any API charges. Here are the details of this $200 credit and how Google see it being applied: API piricing questions.
Note that having an API key was always a requirement if you wanted to route more than 8 properties at a time in ProMaps: with an API key you can create routes with 23 waypoints. More here: routing limits.
Get an API key
You'll need to enable the access to the following 3 APIs to enable all features of ProMaps:
- GeoCoding API
- Directions API
Adding a Key to ProMaps
If you're running ProMaps build 1.053 or earlier, before adding your API key to ProMaps, you'll need to make one small change to the MapSettings table; Select the "Use global storage" option under the Storage tab of the MapSettings::GoogleAPIKey field. This will allow the GeoCoding scripts to use the API key when querying Google's servers.
If you already have a maps API, add it to purchased version of ProMaps on the "General Settings" section of the Settings tab. API keys are supported in version 1.05 and higher.
If you have an older version of ProMaps, upgrade pricing is 40% off: please for an upgrade code.
With Google's new pricing on their API, it's a bit difficult to accurately predict the amount of credit that will be used for each ProMaps solution, but let's take a look at the things in ProMaps that will use the API:
Loading the map:
Loading the Route map:
GeoCoding or Constraining:
Since all of these calls to the different APIs add up, you can see why it's difficult to predict the usage based on the number of users in the solution. It's really something that would become more apparent after a few months of use.