API 驗證並標準化地址：在回應中，Address Validation API 會傳回 API 判定的完整地址，或是指出缺少資訊的位置。
客戶確認或更正地址：視 API 傳回的內容而定，您可以向客戶提供以下提示：
確認建議地址。
提供缺少的資訊。
修正地址。
Maps JavaScript API 中的 Address Validation 運作方式
呼叫 fetchAddressValidation 時，API 會嘗試執行以下操作：
Corrects：提供元件層級的驗證檢查，包括可用的子前提條件。
Completes：嘗試推斷缺少或不正確的地址元件。
格式：清理並標準化地址元件的格式。
關於 CASS™
United States Postal Service® (USPS®)1
維護
Coding Accuracy Support System (CASS™)
，以支援及認證地址驗證服務供應商。已確認 CASS Certified™ 服務 (例如 Address Validation API) 可填入地址中缺少的資訊、將資訊標準化並更新，以提供最新且最準確的地址。
Google 地圖平台是 United States Postal Service® 的非專屬授權使用者。以下商標由 United States Postal Service® 所有，並經過授權使用：United States Postal Service®、CASS™、CASS Certified™。
↩
[null,null,["上次更新時間：2025-08-31 (世界標準時間)。"],[],[],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| This product or feature is in Preview (pre-GA). Pre-GA products and features might have limited support, and changes to pre-GA products and features might not be compatible with other pre-GA versions. Pre-GA Offerings are covered by the [Google\n| Maps Platform Service Specific Terms](https://cloud.google.com/maps-platform/terms/maps-service-terms). For more information, see the [launch stage\n| descriptions](/maps/launch-stages).\n\nWhy use Address Validation in Maps JavaScript API? \n\nThe Address Validation library takes an address as input to identify and validate address\ncomponents. It also standardizes the address for mailing and finds the best known\nlatitude/longitude coordinates for it. Optionally, for addresses in the United States and\nPuerto Rico, you can enable the\n[Coding Accuracy Support System (CASS™)](https://developers.google.com/maps/documentation/address-validation/overview#about-cass).\n\nWith Address Validation API, you can improve delivery\npredictability and reduce delivery failures, thereby providing improved customer experience.\nYou do this by catching bad addresses and obtaining better awareness of address\ncharacteristics.\n| The Geocoding API might be a better match for your needs if you don't need to validate the individual address components. The Geocoding API **converts** addresses into latitude and longitude coordinates. The Address Validation API validates addresses for **correctness** . See [Building location validation capability using Google Maps Platform](https://developers.google.com/maps/architecture/geocoding-address-validation) in the Architecture Center for a detailed comparison.\n\nWhat you can do with Address Validation in Maps JavaScript API\n\nWith Address Validation in Maps JavaScript API, you can determine if an address refers to a\nreal place. If the address does not refer to a real place, the API can identify possibly wrong\ncomponents that you can present to your customers to correct. Here is a sample workflow:\n\n1.\n **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 flow.\n\n2.\n **App sends the address to the API** --- The application passes this\n address using the `fetchAddressValidation` method.\n\n3.\n **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.\n **Customer confirms or corrects the address** --- Depending on what the\n API returns, you can provide the following prompts to the customer:\n\n 1. Confirm the recommended address.\n 2. Provide missing information.\n 3. Fix the address.\n\nHow Address Validation in Maps JavaScript API works\n\nWhen a call to `fetchAddressValidation` is made the API attempts the following:\n\n- **Corrects** --- Provides component-level vaidation 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\nAbout CASS™\n\nThe United States Postal Service® (USPS®)^[1](#fn1)^\nmaintains the [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 [Validate an address](/maps/documentation/javascript/address-validation/TBD).\n\nAs part of our use of USPS services, USPS evaluates requests for artificially created\naddresses. If USPS identifies an input address as being artificially created, Google is\nrequired to stop validating addresses for the customer and must report the customer's\ncontact information (name and address), the relevant input address, and aggregated usage\ndata to USPS. By using the API you consent to these\n[Service Specific Terms](https://cloud.google.com/maps-platform/terms/maps-service-terms).\n\nNext steps\n\n- [Get started with Address Validation in Maps JavaScript API](/maps/documentation/javascript/address-validation/start)\n\n*** ** * ** ***\n\n1. Google Maps Platform is a non-exclusive Licensee of the United States Postal Service®. The following trademark(s) are owned by the United States Postal Service® and used with permission: United States Postal Service®, CASS™, CASS Certified™. [↩](#fnref1)"]]
