Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En algunos casos, es posible que realices varias llamadas a la API de Address Validation para una sola dirección. Por ejemplo, el cliente podría cambiar su dirección después de ver los resultados de la primera validación. Luego, realiza una segunda validación en la dirección actualizada.
En este documento, se describen dos acciones clave que puedes realizar cuando envías una serie de solicitudes para la misma dirección a la API de Address Validation. Estas acciones no son un requisito de uso estricto, sino una acción útil de tu parte para mejorar la calidad general de los datos y la respuesta del sistema.
Envía una solicitud al extremo provideValidationFeedback
Configura el campo previousResponseID
Envía una solicitud provideValidationFeedback
Al final de una serie de validaciones, Google recomienda hacer una llamada a la API de Provide Validation Feedback para indicar el resultado final de todas las validaciones. La solicitud establece dos campos:
conclusion: Indica la versión de validación que usaste en tu servicio, ya sea la que proporcionó el usuario o la que devolvió la API de Address Validation.
El campo conclusion identifica una de las siguientes acciones de tu parte:
VALIDATED_VERSION_USED: Es la versión validada de la dirección de la API de Address Validation.
USER_VERSION_USED: Es la versión original que proporcionó el usuario.
UNVALIDATED_VERSION_USED: Es una versión que fue el resultado de una instrucción para el usuario, pero no se volvió a validar con la API de Address Validation.
El campo responseId especifica para qué resultados de validación de direcciones proporcionas comentarios. Este valor debe ser el mismo que el valor de responseId que devolvió la primera llamada al método validateAddress.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Falta la información que necesito","missingTheInformationINeed","thumb-down"],["Muy complicado o demasiados pasos","tooComplicatedTooManySteps","thumb-down"],["Desactualizado","outOfDate","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Problema con las muestras o los códigos","samplesCodeIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-31 (UTC)"],[[["\u003cp\u003eWhen validating an address multiple times, use the \u003ccode\u003eprovideValidationFeedback\u003c/code\u003e endpoint to inform Google of the final address version used.\u003c/p\u003e\n"],["\u003cp\u003eInclude the original response ID in the \u003ccode\u003eprovideValidationFeedback\u003c/code\u003e request and set the \u003ccode\u003epreviousResponseId\u003c/code\u003e for subsequent validation calls to improve data quality and response time.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003econclusion\u003c/code\u003e field in the feedback request indicates whether the user's original, a validated, or another address version was ultimately used.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003epreviousResponseId\u003c/code\u003e helps the API understand the context of the address validation sequence and potentially optimize results.\u003c/p\u003e\n"]]],[],null,["In some cases, you might make multiple calls to the\nAddress Validation API for a single address. For example, the customer might make\nchanges to their address after seeing the results of the first\nvalidation. You then perform a second validation on the updated address.\n\nThis document describes two key actions you can take when you issue a series of\nrequests for the same address to the Address Validation API. These actions are\nnot a strict usage requirement, but a helpful action on your part to improve\noverall data quality and system response.\n\n- Send a request to the `provideValidationFeedback` endpoint\n- Set the `previousResponseID` field\n\nSend a `provideValidationFeedback` request\n\nAt the end of a series of validations, Google recommends making a call to the\nProvide Validation Feedback API to indicate the final outcome of\nall the validations. The request sets two fields:\n\n- `conclusion` --- Indicates the validation version you used in your service, whether it was the one provided by the user, or the one returned from the Address Validation API.\n- `responseId` --- Indicates the response ID of the **first** response from the Address Validation API. See [Set the previousResponseId field](#followup-requests) below.\n\nUse either the\n[provideValidationFeedback](/maps/documentation/address-validation/reference/rest/v1/TopLevel/provideValidationFeedback)\nmethod (REST) or\n[ProvideValidationFeedback](/maps/documentation/address-validationreference/rpc/google.maps.addressvalidation.v1#google.maps.addressvalidation.v1.AddressValidation.ProvideValidationFeedback)\nmethod (gRPC).\n\nThe following example passes a [JSON body](/maps/documentation/address-validation/reference/rest/v1/TopLevel/validateAddress#request-body) to the request defining the\nconclusion: \n\n```json\ncurl -X POST -d '{\n \"conclusion\": \"VALIDATED_VERSION_USED\",\n \"responseId\": \"de22bed8-7f52-44cb-8526-faceac57150a\"\n}' \\\n-H 'Content-Type: application/json' \\\n\"https://addressvalidation.googleapis.com/v1:provideValidationFeedback?key=\u003cvar translate=\"no\"\u003eAPI_KEY\u003c/var\u003e\"\n```\n\n- The `conclusion` field identifies one of the following actions from your side:\n - `VALIDATED_VERSION_USED`: the validated version of the address from the Address Validation API.\n - `USER_VERSION_USED`: the original version provided by the user.\n - `UNVALIDATED_VERSION_USED`: a version that was a result of a prompt to the user, but did not re-validate it with the Address Validation API.\n - `UNUSED`: abandoned the transaction.\n\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| See [Validation Conclusion](/maps/documentation/address-validation/reference/rest/v1/TopLevel/provideValidationFeedback#validationconclusion) in the reference guide. |\n\n- The `responseId` field specifies which address validation results you are providing feedback for. This value must be the same as the `responseId` value returned by the **first** call to the [validateAddress](/maps/documentation/address-validation/reference/rest/v1/TopLevel/validateAddress) method.\n\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| See [Request Body](/maps/documentation/address-validation/reference/rest/v1/TopLevel/provideValidationFeedback#request-body) in the validation feedback reference guide. |\n\nSet the `previousResponseID` field\n\nWhen issuing a follow-up request the Address Validation API for a given address, set\nthe `previousResponseId` field.\n\n- For the value of the `previousResponseId`, use the value from the `responseId` returned by API after the **first** validation request.\n- Use this same value for any and all followup requests until the series completes.\n\nThis sequence diagram shows the preferred flow:"]]