API 키를 애플리케이션에 필요한 API에서만 사용하도록 제한하는 것이 좋습니다. API 키를 제한하면 불필요한 요청으로부터 애플리케이션이 보호되어 애플리케이션의 보안이 강화됩니다. 제한되지 않은 API 키를 악용하여 발생한 비용에 대한 금전적 책임은 개발자에게 있습니다.
자세한 내용은 API 보안 권장사항을 참고하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-02-07(UTC)"],[[["This guide explains how to create and restrict API keys for the Places SDK for iOS, enabling authentication and billing for your application."],["You can create API keys using the Google Cloud Console or the Cloud SDK, and you need a project with a billing account and the Places SDK enabled."],["Restricting API keys to your application's needs enhances security by limiting unwarranted requests, with the recommendation to use separate keys for each app and platform."],["For iOS, restriction involves specifying bundle identifiers and enabling the Places API under API restrictions in the Google Cloud Console."],["Once you have your API key, you can proceed to set up and configure your Xcode project for integration with the Places SDK."]]],[]]