{"id":2279,"date":"2026-10-20T08:29:35","date_gmt":"2026-10-20T07:29:35","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/google-maps-request-denied\/"},"modified":"2026-10-20T08:53:20","modified_gmt":"2026-10-20T07:53:20","slug":"google-maps-request-denied","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/troubleshooting\/google-maps-request-denied\/","title":{"rendered":"Fixing Google Maps &#8220;REQUEST_DENIED&#8221; and &#8220;API project is not authorized&#8221; errors"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Both errors come from Google, not from GeoDirectory. &#8220;This API project is not authorized to use this API&#8221; means your key&#8217;s Google Cloud project does not have one of the APIs that the map needs. &#8220;Geocode was not successful for the following reason: REQUEST_DENIED&#8221; means Google refused the address lookup, usually because the Geocoding API is not enabled or the key is restricted in a way that blocks it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The quick fix: generate a new key<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to GeoDirectory &gt; Settings &gt; General and find Map Settings.<\/li>\n\n\n\n<li>Next to Google Maps API KEY, click Generate Key. It opens Google Cloud with all the APIs GeoDirectory uses already selected, including the Maps JavaScript API, Places API, Geocoding API and Time Zone API.<\/li>\n\n\n\n<li>Follow the steps in Google, copy the new key and paste it into the field.<\/li>\n\n\n\n<li>Click Verify, then save.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The full walk through is in <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/installation\/get-a-google-api-key\/\">Get a Google API key<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">If you want to keep your current key<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>In Google Cloud, open APIs &amp; Services for the key&#8217;s project and check that the Maps JavaScript API, Places API and Geocoding API are enabled.<\/li>\n\n\n\n<li>Make sure billing is enabled on the project. Google denies requests from projects without a billing account.<\/li>\n\n\n\n<li>If the key is restricted to HTTP referrers (your website address), the geocoding and time zone lookups need a separate key. Add one in the Google Geocoding API Key setting, which shows when you tick Show Advanced on the same settings screen.<\/li>\n\n\n\n<li>Changes in Google Cloud can take a few minutes to apply.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If the map stopped working on a site that used to be fine, see <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/troubleshooting\/maps-have-stopped-working-on-my-site\/\">Maps have stopped working on my site<\/a>. If you would rather not use Google, leave the key blank to use OpenStreetMap; <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/differences-between-the-google-maps-and-openstreetmap-apis\/\">this page compares the two<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Both errors come from Google, not from GeoDirectory. &#8220;This API project is not authorized to use this API&#8221; means your key&#8217;s Google Cloud project does not have one of the APIs that the map needs. &#8220;Geocode was not successful for the following reason: REQUEST_DENIED&#8221; means Google refused the address lookup, usually because the Geocoding API [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[211,437],"class_list":["post-2279","gd_place","type-gd_place","status-publish","hentry","gd_placecategory-tips-tricks-more","gd_placecategory-troubleshooting"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2279","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/types\/gd_place"}],"author":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/comments?post=2279"}],"version-history":[{"count":1,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2279\/revisions"}],"predecessor-version":[{"id":2290,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2279\/revisions\/2290"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2279"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2279"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2279"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}