Assigned
Status Update
Comments
ca...@google.com <ca...@google.com>
ca...@google.com <ca...@google.com> #2
Thank you for posting.
Kindly provide more information regarding your issue so we can further investigate.
Complete sample request
of the API you are using that encounters issueswith all the values of the parameters used
.- The
actual
andyour expected
results with theofficial source of information
(like any government approved resources or latest Street view signage) that can confirm. - Error message.
- Screenshots in a standard image format (e.g. PNG or JPEG) or screen recordings and steps to reproduce the issue.
Description
========================================================================
#REMINDER: Please do not disclose any PII. Some examples of PII are email address, IP, contact number, any part of name, project numbers and billing accounts. Comments or attachments that include PII will be removed and restricted from public viewing as it may violate our security and privacy policies.
Please refrain from emailing a reply to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but _not_ API keys or client ID credentials.
To learn more about personal data, visit
========================================================================
Issue report
----------------
If you are seeing an incorrect address interpretation, validation or geocode result from the Address Validation API, please include the full request in JSON format and explain which sections of the API response are incorrect (and why).
Hi Team,
When we use Address Validation API for validating Australian addresses it does not confirmed the subpremise part of the address. Could you please help us fix this issue?
Thank you!