Just like the keys to your house or your car, it’s important to protect them to make sure they can only be used by the people and in the way you want. Restricting your API keys helps ensure your Google Maps Platform account is secure. Your API keys are the primary way we authenticate your access to Google Maps Platform APIs and SDKs. API keys are generated in the Google Cloud console, and act as unique identifiers that authenticate the calls you make to Google Maps Platform and ensure they are billed to the correct account. With the exception of Maps URLs, all Google Maps Platform APIs and SDKs require you to send an API key with all calls. Today’s topic: restricting your API keys. First up in our series is what you should do to control and prevent any unwanted or unexpected usage of your Google Maps Platform project. Part of that is helping you keep your Google Maps Platform integration efficient and secure. We know you put a lot of time and energy into creating experiences your users love, and we’re here to make sure you have the tools you need to bring Google’s knowledge about the world to everything you build. Today, Mike and his team are kicking off a three-part series on best practices for using Google Maps Platform. Editor’s Note: Today’s post comes from Mike Pegg–head of our Google Maps Platform developer relations team and longtime Maps developer (you might remember him from the Google Maps Mania blog).
0 kommentar(er)
