Autocomplete (Baru) menggunakan permintaan HTTP POST. Teruskan parameter dalam isi permintaan atau di header sebagai bagian dari permintaan POST HTTP. Sebaliknya,
dengan API lama, Anda meneruskan parameter URL menggunakan
permintaan HTTP GET.
Pelengkapan Otomatis (Baru) mendukung kunci API
dan token OAuth sebagai mekanisme autentikasi.
Hanya JSON yang didukung sebagai format respons di Pelengkapan Otomatis (Baru).
Tabel berikut mencantumkan parameter di Place Autocomplete (Lama) dan Query Autocomplete (Lama) yang telah diganti namanya atau diubah untuk Autocomplete (Baru), atau parameter yang tidak lagi didukung.
Parameter saat ini
Parameter baru
Catatan
components
includedRegionCodes
language
languageCode
location
locationBias
ipbias
Jika Anda tidak menyertakan locationBias dan locationRestriction, API akan menggunakan bias IP secara default.
offset
inputOffset
radius
locationBias atau locationRestriction
region
regionCode
stricbounds
locationRestriction
sessiontoken
sessionToken
types
includedPrimaryTypes
Contoh permintaan
Contoh permintaan GET berikut menggunakan Place Autocomplete (Lama). Dalam
contoh ini, Anda meminta respons JSON yang berisi informasi tentang tempat bernama
"Amoeba" yang berjenis establishment dan meneruskan semua parameter sebagai parameter
URL:
curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=amoeba&types=establishment&location=37.76999%2C-122.44696&radius=500&key=YOUR_API_KEY'
Dengan Autocomplete (Baru), Anda membuat permintaan POST dan meneruskan semua parameter
di isi permintaan JSON atau di header sebagai bagian dari permintaan POST.
Mask kolom tidak diperlukan untuk permintaan Pelengkapan Otomatis (Baru), tetapi dapat digunakan untuk memfilter hasil tertentu dalam respons. Misalnya, permintaan berikut menggunakan mask kolom sehingga respons hanya menyertakan suggestions.placePrediction.text saran:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[],[],null,["**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\nPlaces API supports the\n[Place Autocomplete (Legacy)](/maps/documentation/places/web-service/autocomplete)\nand [Query Autocomplete (Legacy)](/maps/documentation/places/web-service/query) APIs.\nIf you are familiar with these APIs, Autocomplete (New) makes the following changes:\n\n- Autocomplete (New) uses HTTP POST requests. Pass parameters in the request body or in headers as part of an HTTP POST request. In contrast, with the legacy APIs, you pass URL parameters using an HTTP GET request.\n- Autocomplete (New) supports 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 in Autocomplete (New).\n\nThe following table lists parameters in Place Autocomplete (Legacy) and Query Autocomplete (Legacy) that have been renamed or modified for Autocomplete (New), or parameters that are no longer supported.\n\n| Current parameter | New parameter | Notes |\n|-------------------|-----------------------------------------|-----------------------------------------------------------------------------------------------------|\n| `components` | `includedRegionCodes` | |\n| `language` | `languageCode` | |\n| `location` | `locationBias` | |\n| `ipbias` | | If you omit both `locationBias` and `locationRestriction`, then the API uses IP biasing by default. |\n| `offset` | `inputOffset` | |\n| `radius` | `locationBias` or `locationRestriction` | |\n| `region` | `regionCode` | |\n| `stricbounds` | `locationRestriction` | |\n| `sessiontoken` | `sessionToken` | |\n| `types` | `includedPrimaryTypes` | |\n\nExample request\n\nThe following example GET request uses Place Autocomplete (Legacy). In this\nexample, you request a JSON response containing information about places called\n\"Amoeba\" that are of type `establishment` and pass all parameters as URL\nparameters: \n\n```curl\ncurl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=amoeba&types=establishment&location=37.76999%2C-122.44696&radius=500&key=YOUR_API_KEY'\n```\n\nWith Autocomplete (New), you make a POST request and pass all parameters\nin the JSON request body or in headers as part of the POST request.\n\nField masks are not required for Autocomplete (New) requests, but they can\nbe used to filter for specific results in the response. For example, the\nfollowing request uses a field mask so the response only includes the\n`suggestions.placePrediction.text` of the suggestion: \n\n```curl\ncurl -X POST -d '{\n \"input\": \"Amoeba\",\n \"locationBias\": {\n \"circle\": {\n \"center\": {\n \"latitude\": 37.76999,\n \"longitude\": -122.44696\n },\n \"radius\": 500.0\n }\n }\n}' \\\n-H 'Content-Type: application/json' -H 'X-Goog-Api-Key: API_KEY' \\\n-H 'X-Goog-FieldMask: suggestions.placePrediction.text' \\\nhttps://places.googleapis.com/v1/places:autocomplete\n```\n\nTo learn more about using field masks, see\n[Place Details (New)](/maps/documentation/places/web-service/place-details#fieldmask)."]]
