Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #1132771

    HI,

    I’m hoping you may be able to answer this.

    In regards to the Google Maps API key, do I need a separate API key for each and every individual website or can you you one API key to cover all?

    I inadvertently deleted the APIs I had but managed to restore them but I am now getting an error on the maps across my various websites and the API I had is not recognized. I think this is related to billing but thought I’d ask the question above.

    Cheers
    John

    #1132987

    Hey John,

    We recommend that you keep one key per site, that way you can change it for individual sites instead of having to update it for all of them if that should be needed.

    Best regards,
    Rikard

    #1133029

    the best is to have one api key for website, every api should have enabled only the api’s you really need (for enfold is Javascript api and geocoding api) and also you need to restrict the calls from your website’s url.
    Other best thing is to set a quota, so you are sure you will not paying anything.

    #1133145

    Many thanks for the input. Valued feedback. Now to go change a few things :)

    Hi Marco – For the APIs you mentioned, where do I access this. is this in the API library and I just click on one of the boxes there? Also, where do I restrict the calls from the website’s url?

    Cheers
    John

    #1134799

    Hi,

    Thank you for the update.

    You should be able to restrict the key in the console’s API & Credentials panel. CLick on the API key and look for the HTTPs restrictions. Add the site URL or use a wildcard pattern. Please refer to the documentation for more info.

    // https://kriesi.at/documentation/enfold/google-map/#add-an-api-key

    If you want to enable a particular API, follow this short tutorial.

    // https://kriesi.at/documentation/enfold/google-map/#enable-services-for-google-api

    Best regards,
    Ismael

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.