Overview #
Earlier documentation covered the browser Google Maps key used for address autocomplete. The updated plugin adds a separate Google Server API Key setting for server-side Google API work, such as bulk address auto-resolving.
This is useful because browser keys and server keys should usually be restricted differently.
Where to Find It #
Go to Huski Members > Settings and look for Google Server API Key under Integrations.
Browser Key vs. Server Key #
Google Maps API Key is used in the browser for Places autocomplete on member forms. It can be restricted by website referrer.
Google Server API Key is used behind the scenes for server-side Google API calls, such as bulk address auto-resolve. This key should usually be restricted by server IP instead of HTTP referrer.
Why This Matters #
Using separate keys is cleaner and safer. A browser key has to be usable from the visitor’s browser. A server key should stay private and only be used by the server.
Best Practices #
- Use separate Google keys for browser and server work.
- Restrict the browser key by referrer.
- Restrict the server key by server IP when possible.
- Test address resolving before using it on many members.
- Review resolved address data after bulk cleanup.
Troubleshooting #
- Autocomplete works but bulk resolving fails: Check the Google Server API Key.
- Server key errors appear: Check IP restrictions and enabled Google APIs.
- Addresses resolve incorrectly: Review the original typed address and confirm the selected Google result.
- No address metadata is saved: Make sure the address can be resolved by Google and that server-side resolving is configured.
That’s it, dawg!
