Places API (신규)는 성능이 개선되었으며 새로운 가격 모델을 제공하므로 Places API (기존)를 사용하는 앱을 업데이트할 가치가 있습니다. 기능 비교에 대한 자세한 내용은 API 선택을 참고하세요.
이 가이드를 통해 Places API (신규)와 Places API (기존)의 주요 차이점과 필요한 변경사항을 처리하는 방법을 알아보세요.
마이그레이션 결제 권장사항
warning_amber
이 안내는 API 사용량이 2단계 요금으로 전환될 만큼 많은 경우에 적용됩니다. API의 최신 버전으로 이전하면 다른 SKU에 대한 요금도 청구됩니다. 전환하는 달에 비용이 증가하지 않도록 하려면 가능한 한 달 초에 프로덕션에서 새 API로 전환하는 것이 좋습니다. 이렇게 하면 이전 달에 가장 비용 효율적인 월간 요금 등급에 도달할 수 있습니다. 가격 등급에 대한 자세한 내용은 가격 페이지 및 가격 FAQ를 참고하세요.
Places API (신규) 사용 설정
Places API (신규)의 기능을 사용하려면 먼저 Google Cloud 프로젝트에서 Places API (신규)를 사용 설정해야 합니다. 자세한 내용은 Google Cloud 프로젝트 설정을 참고하세요.
그런 다음 앱에서 사용하는 API 키에 Places API (New)를 추가해야 합니다. 자세한 내용은 API 키 사용을 참고하세요.
[null,null,["최종 업데이트: 2025-08-29(UTC)"],[],[],null,["# Migration overview\n\n**European Economic Area (EEA) developers** If your billing address is in the European Economic Area, effective on 8 July 2025, the [Google Maps Platform EEA Terms of Service](https://cloud.google.com/terms/maps-platform/eea) will apply to your use of the Services. Functionality varies by region. [Learn more](/maps/comms/eea/faq).\n\nIntroduction\n------------\n\nPlaces API (New) provides improved performance and a new pricing model,\nmaking it worthwhile to update apps that use the Places API (Legacy). For more\ndetails on comparing features, see [Choose your\nAPI](/maps/documentation/places/web-service/choose-api).\n\nUse this guide to understand key differences between Places API (New)\ncompared to Places API (Legacy), along with how to handle necessary changes.\n\n\nBilling best practices for migration\n------------------------------------\n\nwarning_amber\n\nThis guidance applies if your API usage is high enough to\nmove into second-tier pricing. When migrating to a newer version of an API,\nyou're also being billed for a different SKU. To avoid increased costs during the month of\nyour transition, we recommend switching to the new APIs in production as close to the\nbeginning of the month as possible. This will ensure that you reach the most cost-effective\nmonthly pricing tiers during the migration month. For information about pricing tiers,\nsee the [pricing page](/maps/billing-and-pricing/pricing)\nand the [pricing FAQ](/maps/billing-and-pricing/faq).\n\n\u003cbr /\u003e\n\nEnable Places API (New)\n-----------------------\n\nTo use the features of Places API (New), you must first enable\n**Places API (New)** in your Google Cloud project. For more\ninformation, see [Set up your Google Cloud\nproject](/maps/documentation/places/web-service/cloud-setup).\n\nYou then must ensure that you have added **Places API (New)** to the API\nkey used by your app. For more information, see [Use API\nKeys](/maps/documentation/places/web-service/get-api-key).\n| **Note:** If you are using both Places API (Legacy) and Places API (New), we recommend that you create a separate API key for each API version.\n\nGeneral changes\n---------------\n\nSome general changes that apply to multiple APIs include:\n\n- All new APIs support both [API keys](/maps/documentation/places/web-service/get-api-key) and [OAuth](/maps/documentation/places/web-service/oauth-token) tokens as the authentication mechanism.\n- Only JSON is supported as a response format.\n- Field masking is required by Place Details (New), Nearby Search (New), and Text Search (New) to specify which fields you want returned in the response. For more information, see [FieldMask](/maps/documentation/places/web-service/choose-fields).\n- The [Nearby Search (New)](/maps/documentation/places/web-service/nearby-search) and [Text Search (New)](/maps/documentation/places/web-service/text-search) APIs now return the full place details to match the place details returned by [Place Details (New)](/maps/documentation/places/web-service/place-details).\n- The JSON response format for the [Place Details (New)](/maps/documentation/places/web-service/place-details), [Nearby Search (New)](/maps/documentation/places/web-service/nearby-search), and [Text Search (New)](/maps/documentation/places/web-service/text-search) APIs has changed from the format of the existing APIs. For more details, see [Migrate the Places API response](/maps/documentation/places/web-service/migrate-response).\n\nAPI-specific changes\n--------------------\n\nThis section includes the following migration guides for each API:\n\n- [Migrate to Nearby Search (New)](/maps/documentation/places/web-service/migrate-nearby)\n- [Migrate to Text Search (New)](/maps/documentation/places/web-service/migrate-text)\n- [Migrate to Place Details (New)](/maps/documentation/places/web-service/migrate-details)\n- [Migrate to Place Photos (New)](/maps/documentation/places/web-service/migrate-photo)\n- [Migrate to Autocomplete (New)](/maps/documentation/places/web-service/migrate-autocomplete)"]]
