Skip Navigation

[Resolved] Toolset Maps and Google Maps API restrictions

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.

Our next available supporter will start replying to tickets in about 6.35 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 3 replies, has 2 voices.

Last updated by Minesh 9 months, 1 week ago.

Assisted by: Minesh.


Google has started sending notifications to API key owners when credentials are publicly exposed on sites and not sufficiently restricted. Toolset has always had this problem and it has, at times, cost me and my clients a fair amount of money in API usage fees when credentials get stolen and abused.

Is Toolset ever going to enhance Maps so that we can use http referrer restrictions on the front-end Google Maps API Key credentials?



Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Dont you able to restrict the google map site key from your google map API settings page?

More info:
- hidden link


Hi Minesh, I know how to restrict Maps API keys. Toolset's documentation says that we cannot use http referrer restrictions. My question is whether that will ever change?

I have the browser keys restricted to javascript api and places api but I'd also like to restrict them to requests referred from the web server as I'm still seeing some abuse of the APIs with the restrictions that work with Toolset Maps and my clients are now getting emails from Google saying their API keys aren't well enough protected.



Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Here is the related ticket where one of the user solved the issue about http referer:

Can you please try to follow that and check if that helps?

Another source that might help:

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.