Google API Issue: Over Query Limit

This support ticket is created 5 years, 8 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	-
-	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	-

Supporter timezone: Europe/London (GMT+00:00)

Tagged: Toolset Maps, Views plugin

This topic contains 3 replies, has 2 voices.

Last updated by orlaF 5 years, 8 months ago.

Assisted by: Nigel.

Author

Posts

May 1, 2019 at 5:57 am #1238019

orlaF

I have added two API's both with Places, Geocoding & Geolocation enabled. The first API is restricted to the domain name for both https:// and http:// requests and the second server side API is unrestricted (See Screenshot: hidden link). However, I keep getting the following error when I try to Check API: hidden link

I have also tried leaving the restricted key unrestricted and it still gave the same error.

Is there any reason for this error and how can I fix it?

May 1, 2019 at 6:33 am #1238025

Nigel

Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi there

The error OVER_QUERY_LIMIT points to a problem with too many requests per second, but I suspect it may be a red herring.

In your screenshot you show that you are restricting the APIs that the key can call, and you are missing the Maps JavaScript API, for example.

I suggest you remove the API restrictions from your keys and re-test. If the error reported disappears then you can re-apply API restrictions but you'll need to include additional APIs, which may involve some trial and error.

Let me know what you find.

May 1, 2019 at 7:45 am #1238074

orlaF

Hi Nigel,

After a lot of trial and error - I figured out that I needed to add a billing account to each of the API's and that was what was causing the issue. They are both working perfectly now.

Kind Regards,
Orla

May 1, 2019 at 7:46 am #1238075

orlaF

My issue is resolved now. Thank you!