Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Developer Wilayah Ekonomi Eropa (EEA)
Pengantar
Address Validation API adalah layanan yang menerima alamat.
API ini mengidentifikasi komponen alamat dan memvalidasinya. Selain itu, Address Validation API menstandarkan alamat untuk pengiriman dan menemukan koordinat lintang/bujur yang paling akurat untuk alamat tersebut.
Secara opsional, untuk alamat di Amerika Serikat dan Puerto Riko, Anda dapat mengaktifkan
Coding Accuracy Support System (CASS™).
Alasan menggunakan Address Validation API
Dengan Address Validation API, Anda dapat meningkatkan prediktabilitas pengiriman dan mengurangi kegagalan pengiriman, sehingga memberikan pengalaman pelanggan yang lebih baik. Anda melakukannya dengan mendeteksi alamat yang salah dan mendapatkan pemahaman yang lebih baik tentang karakteristik alamat.
Geocoding API mungkin lebih sesuai dengan kebutuhan Anda jika Anda tidak perlu memvalidasi setiap komponen alamat. Geocoding API mengonversi alamat menjadi koordinat lintang dan bujur. Address Validation API memvalidasi alamat untuk kebenarannya. Lihat
Membangun kemampuan validasi lokasi menggunakan Google Maps Platform
di Pusat Arsitektur untuk perbandingan mendetail.
Yang dapat Anda lakukan dengan Address Validation API
Dengan Address Validation API, Anda dapat menentukan apakah suatu alamat merujuk ke tempat yang sebenarnya. Jika alamat tidak merujuk ke tempat
nyata, API dapat mengidentifikasi komponen yang mungkin salah yang dapat Anda tunjukkan kepada
pelanggan untuk diperbaiki. Berikut adalah contoh alur kerja menggunakan API:
Pelanggan memasukkan alamat – Gambar berikut menunjukkan formulir dasar yang memungkinkan pelanggan memasukkan alamat, mungkin sebagai bagian dari alur checkout.
Aplikasi mengirimkan alamat ke API – Aplikasi meneruskan alamat ini
sebagai input ke Address Validation API.
API memvalidasi dan menstandardisasi alamat – Dalam responsnya, Address Validation API menampilkan alamat lengkap sebagaimana ditentukan oleh API, atau menunjukkan tempat informasi tidak ada.
Pelanggan mengonfirmasi atau mengoreksi alamat – Bergantung pada
apa yang ditampilkan API, Anda dapat memberikan perintah berikut kepada pelanggan:
A. Konfirmasi alamat yang direkomendasikan. B. Berikan informasi yang belum ada.
C. Perbaiki alamat.
Cara kerja Address Validation API
Validasi alamat menerima permintaan POST dengan alamat dalam bentuk
isi JSON. Layanan ini memisahkan alamat menjadi komponen-komponennya, lalu mencoba hal berikut:
Memperbaiki—Memberikan pemeriksaan validasi tingkat komponen, termasuk
sub-tempat jika tersedia.
Melengkapi—Berupaya menyimpulkan komponen alamat yang tidak ada atau salah.
Format—Membersihkan dan menstandardisasi format untuk komponen alamat.
Resource
Tabel berikut merangkum resource yang tersedia melalui
Address Validation API beserta data yang ditampilkan. Untuk mengetahui detail spesifik, lihat
Referensi Address Validation API.
Jelajahi demo
dengan berbagai formulir alamat, baik yang benar maupun salah.
Demo ini memberikan cara yang berguna untuk menjelajahi nilai yang ditampilkan dari
layanan, serta respons API berformat JSON.
2
Periksa cakupan
Tinjau detail cakupan
untuk melihat negara dan wilayah yang didukung Address Validation API.
Mulai dengan alamat dasar, lalu untuk akurasi tambahan, Anda dapat
mengaktifkan CASS (khusus untuk alamat di AS dan PR). Lihat Meminta validasi alamat.
5
Memproses respons
Respons Address Validation API menyediakan dua properti, yang masing-masing
Anda gunakan dengan cara yang berbeda.
Lihat Memahami respons dasar.
6
Meningkatkan akurasi validasi
Anda dapat membantu meningkatkan akurasi alamat dengan memberikan masukan tentang respons Address Validation API. Lihat Menangani alamat yang diperbarui.
Library klien yang tersedia
Untuk mengetahui daftar library klien yang tersedia untuk Address Validation API, lihat
Library klien.
Tentang CASS™
United States Postal Service® (USPS®)1 mengelola
Coding Accuracy Support System (CASS™)
untuk mendukung dan mensertifikasi penyedia validasi alamat. Layanan bersertifikasi CASS Certified™, seperti Address Validation API, telah dikonfirmasi kemampuannya untuk melengkapi informasi yang tidak ada dalam alamat, menstandarkannya, dan memperbaruinya untuk memberi Anda alamat yang paling terbaru dan paling akurat.
CASS tidak diaktifkan secara default dan hanya didukung untuk wilayah "Amerika Serikat" dan "Puerto Riko". Untuk mengaktifkan CASS, tetapkan enableUspsCass ke true sebagai bagian dari permintaan validasi. Untuk mengetahui informasi selengkapnya, lihat
Memvalidasi alamat.
Sebagai bagian dari penggunaan layanan USPS, USPS mengevaluasi permintaan untuk alamat yang dibuat secara artifisial. Jika USPS mengidentifikasi alamat input dibuat secara artifisial, Google diwajibkan untuk berhenti memvalidasi alamat untuk pelanggan dan harus melaporkan informasi kontak pelanggan (nama dan alamat), alamat input yang relevan, dan data penggunaan gabungan kepada USPS. Dengan menggunakan API ini, Anda menyetujui
Persyaratan Khusus Layanan ini.
Google Maps Platform adalah Penerima Lisensi tidak eksklusif dari United States Postal Service®. Merek dagang berikut dimiliki oleh United States Postal Service® dan digunakan dengan izin: United States Postal Service®, CASS™, CASS Certified™. ↩
[[["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-08-31 UTC."],[[["\u003cp\u003eThe Address Validation API validates, standardizes, and geocodes addresses, improving delivery predictability and customer experience.\u003c/p\u003e\n"],["\u003cp\u003eIt identifies address components, validates them for correctness, and provides suggestions for corrections, unlike the Geocoding API, which only converts addresses to coordinates.\u003c/p\u003e\n"],["\u003cp\u003eAddresses are processed by correcting, completing, and formatting components, with CASS™ support for US and Puerto Rico addresses for enhanced accuracy (requires enabling).\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can access resources like a demo, coverage details, setup instructions, validation requests, response understanding, and client libraries to utilize the API effectively.\u003c/p\u003e\n"],["\u003cp\u003eUSPS evaluates requests for artificially created addresses, and Google is obligated to stop validation and report relevant information to USPS in such cases.\u003c/p\u003e\n"]]],["The Address Validation API validates and standardizes addresses, identifying components and correcting errors. It can infer missing information, and determine if an address is a real place. The API accepts an address, validates it, and returns a complete address or flags missing information. Users can confirm, correct, or provide missing details. For US and Puerto Rico addresses, CASS can be enabled for enhanced accuracy. The Geocoding API may be preferred if address component validation is not needed.\n"],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 The Address Validation API is a service that accepts an address. It identifies address components and validates them. It also standardizes the address for mailing and finds the best known latitude/longitude coordinates for it. Optionally, for addresses in the United States and Puerto Rico, you can enable the [Coding Accuracy Support System (CASS™)](https://developers.google.com/maps/documentation/address-validation/overview#about-cass).\n\nWhy use the Address Validation API\n\nWith the Address Validation API, you can improve delivery predictability and reduce\ndelivery failures, thereby providing improved customer experience. You do this\nby catching bad addresses and obtaining better awareness of address\ncharacteristics.\n\nThe Geocoding API might be a better match for your needs if you\ndon't need to validate the individual address components. The Geocoding API\n**converts** addresses into latitude and longitude coordinates. The\nAddress Validation API validates addresses for **correctness** . See\n[Building location validation capability using Google Maps Platform](https://developers.google.com/maps/architecture/geocoding-address-validation)\nin the Architecture Center for a detailed comparison.\n\nWhat you can do with the Address Validation API\n\n[inputTry the demo](/maps/documentation/address-validation/demo) [](/maps/documentation/address-validation/demo)\n\nWith the Address Validation API, you can determine if an address\nrefers to a real place. If the address does not refer to a real\nplace, the API can identify possibly wrong components that you can present to\nyour customers to correct. Here is a sample workflow using the API:\n\n1. **Customer enters an address** -- The following image shows a basic form\n that allows a customer to enter an address, possibly as part of a checkout\n flow.\n\n2. **App sends the address to the API** -- The application passes this address\n as the input to the Address Validation API.\n\n3. **API validates and standardizes the address** -- In its response, the\n Address Validation API returns the complete address as determined by the API, or\n indicates where information is missing.\n\n4. **Customer confirms or corrects the address** -- Depending on\n what the API returns, you can provide the following prompts to the customer:\n **A.** Confirm the recommended address. **B.** Provide missing information.\n **C.** Fix the address.\n\nHow the Address Validation API works\n\nThe address validation accepts a POST request with the address in the form\nof a JSON body. It separates the address into its individual components, and\nthen attempts the following:\n\n- **Corrects**---Provides component-level validation checks, including sub-premises where available.\n- **Completes**---Attempts to infer missing or incorrect address components.\n- **Formats**---Cleans up and standardizes the format for address components.\n\nResources\n\nThe following table summarizes the resources available through the\nAddress Validation API along with the data it returns. For specific details, see the\n[Address Validation API reference](./reference/rest).\n\n\u003cbr /\u003e\n\n| Data resources | Data returned |\n|-------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **Address components in JSON format.** See [Validate an address](/maps/documentation/address-validation/requests-validate-address). | Complete, validated address (if possible). Validation status of each address component. Where available for an address: - Geocode - Address precision - Postal services data, where available. See [Understand the validation response](/maps/documentation/address-validation/understand-response). |\n\n\u003cbr /\u003e\n\nHow to use the Address Validation API\n\n|---|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1 | **Try the demo** | [Explore the demo](/maps/documentation/address-validation/demo) with a variety of address forms, both correct and incorrect. The demo provides a useful way to explore both the return values from the service, as well as the JSON formatted API response. |\n| 2 | **Check coverage** | Review [coverage details](/maps/documentation/address-validation/coverage) to see which countries and regions the Address Validation API supports. |\n| 3 | **Get set up** | Start with [Set up your Google Cloud project](/maps/documentation/address-validation/cloud-setup) and complete the instructions that follow. |\n| 4 | **Request an address validation** | Start with a basic address and then, for additional accuracy, you can enable CASS (for US and PR addresses only). See [Request an address validation.](/maps/documentation/address-validation/requests-validate-address) |\n| 5 | **Process a response** | The Address Validation API response provides two properties, each of which you use in different ways. See [Understand a basic response.](/maps/documentation/address-validation/understand-response) |\n| 6 | **Improve validation accuracy** | You can help improve address accuracy by providing feedback on Address Validation API responses. See [Handle updated addresses](/maps/documentation/address-validation/handle-updated-address). |\n\nAvailable client libraries\n\nFor a list of the available client libraries for Address Validation API,\nsee\n[Client libraries](/maps/documentation/address-validation/client_libraries).\n\nAbout CASS™\n\nThe United States Postal Service® (USPS®)^[1](#fn1)^ maintains the\n[Coding Accuracy Support System (CASS™)](https://postalpro.usps.com/certifications/cass)\nto support and certify address validation providers. A CASS Certified™ service,\nsuch as the Address Validation API, has been confirmed for its\nability to fill in information missing from an address, standardize it, and\nupdate it to give you the most current and most accurate address.\n\nCASS is not enabled by default and is only supported for the \"US\" and \"PR\"\nregions. To enable CASS, set `enableUspsCass` to `true` as part of a validation\nrequest. For more information, see\n[Validate an address](/maps/documentation/address-validation/requests-validate-address#enable-cass).\n\nAs part of our use of USPS services, USPS evaluates requests for artificially\ncreated addresses. If USPS identifies an input address as being artificially\ncreated, Google is required to stop validating addresses for the customer and\nmust report the customer's contact information (name and address), the relevant\ninput address, and aggregated usage data to USPS. By using the API you consent\nto these\n[Service Specific Terms](https://cloud.google.com/maps-platform/terms/maps-service-terms).\n\nWhat's next\n\n- **Try the demo** : Go to [Demo](/maps/documentation/address-validation/demo)\n- **Review coverage areas** : Go to [Country and region coverage details](/maps/documentation/address-validation/coverage)\n- **Try your first validation request** : Go to [Send an address validation request](/maps/documentation/address-validation/requests-validate-address)\n- **Process addresses at high volume** : Go to [Use Address Validation API to process addresses at high volume](/maps/architecture/high-volume-address-validation)\n\n*** ** * ** ***\n\n1. Google Maps Platform is a non-exclusive Licensee of the United States\n Postal Service®. The following trademark(s) are owned by the United States\n Postal Service® and used with permission: United States Postal Service®,\n CASS™, CASS Certified™. [↩](#fnref1)"]]
