Google Maps API errors & quotas

Most “broken map” reports are Google Cloud configuration — not Ultimate itself. Open the browser console (F12) on the map page and read the exact error.

Common console errors

Error Meaning Fix
InvalidKeyMapError Key invalid or wrong Create/paste the correct key in Progress Map settings
RefererNotAllowedMapError Domain not allowed on the key Add https://yoursite.com/* and https://www.yoursite.com/* (and staging) under Application restrictions → HTTP referrers
ApiNotActivatedMapError Required API not enabled Enable Maps JavaScript API (plus Geocoding, Places, Directions as needed)
BillingNotEnabledMapError Billing off Enable billing on the Google Cloud project
Gray map “Oops! Something went wrong” See console Usually one of the above

Setup walkthrough: Google Maps API key.

Quota set to 0 (API looks enabled but fails)

Google has a known class of issues where a daily quota override of 0 disables an API even though it appears enabled in the console.

Reference: Google Issue Tracker 113046037

Symptoms

  • Console: ApiNotActivatedMapError or “project is not authorized to use this API”
  • Dashboard shows the API as enabled
  • Sometimes billing was enabled after a zero quota was set

Fix

  1. Google Cloud Console → select the project that owns your key.
  2. APIs & Services → Dashboard → open the affected API (e.g. Maps JavaScript API).
  3. Open the Quotas tab.
  4. Find daily quotas such as Map loads per day / Requests per day.
  5. If any limit is 0, edit it to a sensible non-zero value and save.
  6. Confirm billing is linked to the project.
  7. Wait 5–15 minutes, then reload the map.

REQUEST_DENIED on Places / web services

If Nearby / Places features fail with REQUEST_DENIED:

  1. Enable the Places API (and related APIs your module needs).
  2. Ensure the same key is allowed to call those APIs (API restrictions on the key).
  3. Check Google’s Places FAQ for denied requests.

Checklist after changing Google settings

  1. Key pasted in Progress Map settings and saved
  2. Referrers include every public hostname you use
  3. Needed APIs enabled
  4. Billing on; no zero daily quotas
  5. Caches purged

Related

Top