ValidateAddress Service Operation - Customer Management

Determines whether or not the submitted address is valid for Microsoft Advertising accounts.

If the address is valid you can use it as the account BusinessAddress.

For Australia (AU), Canada (CA), and The United States (US), the operation validates whether or not you could ship something to the address. For all other countries or regions basic address verification (AVS) is completed.

Request Elements

The ValidateAddressRequest object defines the body and header elements of the service operation request. The elements must be in the same order as shown in the Request SOAP.

Note

Unless otherwise noted below, all request elements are required.

Request Body Elements

Element Description Data Type
Address The address to validate. Address

Request Header Elements

Element Description Data Type
AuthenticationToken The OAuth access token that represents the credentials of a user who has permissions to Microsoft Advertising accounts.

For more information see Authentication with OAuth.
string
DeveloperToken The developer token used to access the Bing Ads API.

For more information see Get a Developer Token.
string
Password This element is reserved for internal use and will be removed from a future version of the API. You must use the AuthenticationToken element to set user credentials. string
UserName This element is reserved for internal use and will be removed from a future version of the API. You must use the AuthenticationToken element to set user credentials. string

Response Elements

The ValidateAddressResponse object defines the body and header elements of the service operation response. The elements are returned in the same order as shown in the Response SOAP.

Response Body Elements

Element Description Data Type
OriginalAddress The address that was submitted for validation.

The submitted Address is always passed back here in the response, so this element is always set.
Address
Status Determines whether or not the submitted address is valid for Microsoft Advertising accounts, and whether or not any address suggestions are available via the SuggestedAddresses response element.

Possible string values are AddressValidWithoutSuggestions, AddressValidWithSuggestions, AddressInvalidWithoutSuggestions, and AddressInvalidWithSuggestions.
string
SuggestedAddresses One or more suggested addresses if the Status is either AddressValidWithSuggestions or AddressInvalidWithSuggestions.

This element will be nil if the Status is either AddressValidWithoutSuggestions or AddressInvalidWithoutSuggestions.
Address array

Response Header Elements

Element Description Data Type
TrackingId The identifier of the log entry that contains the details of the API call. string

Request SOAP

This template was generated by a tool to show the order of the body and header elements for the SOAP request. For supported types that you can use with this service operation, see the Request Body Elements reference above.

<s:Envelope xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
  <s:Header xmlns="https://bingads.microsoft.com/Customer/v13">
    <Action mustUnderstand="1">ValidateAddress</Action>
    <AuthenticationToken i:nil="false">ValueHere</AuthenticationToken>
    <DeveloperToken i:nil="false">ValueHere</DeveloperToken>
  </s:Header>
  <s:Body>
    <ValidateAddressRequest xmlns="https://bingads.microsoft.com/Customer/v13">
      <Address xmlns:e285="https://bingads.microsoft.com/Customer/v13/Entities" i:nil="false">
        <e285:City i:nil="false">ValueHere</e285:City>
        <e285:CountryCode i:nil="false">ValueHere</e285:CountryCode>
        <e285:Id i:nil="false">ValueHere</e285:Id>
        <e285:Line1 i:nil="false">ValueHere</e285:Line1>
        <e285:Line2 i:nil="false">ValueHere</e285:Line2>
        <e285:Line3 i:nil="false">ValueHere</e285:Line3>
        <e285:Line4 i:nil="false">ValueHere</e285:Line4>
        <e285:PostalCode i:nil="false">ValueHere</e285:PostalCode>
        <e285:StateOrProvince i:nil="false">ValueHere</e285:StateOrProvince>
        <e285:TimeStamp i:nil="false">ValueHere</e285:TimeStamp>
        <e285:BusinessName i:nil="false">ValueHere</e285:BusinessName>
      </Address>
    </ValidateAddressRequest>
  </s:Body>
</s:Envelope>

Response SOAP

This template was generated by a tool to show the order of the body and header elements for the SOAP response.

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
  <s:Header xmlns="https://bingads.microsoft.com/Customer/v13">
    <TrackingId d3p1:nil="false" xmlns:d3p1="http://www.w3.org/2001/XMLSchema-instance">ValueHere</TrackingId>
  </s:Header>
  <s:Body>
    <ValidateAddressResponse xmlns="https://bingads.microsoft.com/Customer/v13">
      <OriginalAddress xmlns:e286="https://bingads.microsoft.com/Customer/v13/Entities" d4p1:nil="false" xmlns:d4p1="http://www.w3.org/2001/XMLSchema-instance">
        <e286:City d4p1:nil="false">ValueHere</e286:City>
        <e286:CountryCode d4p1:nil="false">ValueHere</e286:CountryCode>
        <e286:Id d4p1:nil="false">ValueHere</e286:Id>
        <e286:Line1 d4p1:nil="false">ValueHere</e286:Line1>
        <e286:Line2 d4p1:nil="false">ValueHere</e286:Line2>
        <e286:Line3 d4p1:nil="false">ValueHere</e286:Line3>
        <e286:Line4 d4p1:nil="false">ValueHere</e286:Line4>
        <e286:PostalCode d4p1:nil="false">ValueHere</e286:PostalCode>
        <e286:StateOrProvince d4p1:nil="false">ValueHere</e286:StateOrProvince>
        <e286:TimeStamp d4p1:nil="false">ValueHere</e286:TimeStamp>
        <e286:BusinessName d4p1:nil="false">ValueHere</e286:BusinessName>
      </OriginalAddress>
      <Status d4p1:nil="false" xmlns:d4p1="http://www.w3.org/2001/XMLSchema-instance">ValueHere</Status>
      <SuggestedAddresses xmlns:e287="https://bingads.microsoft.com/Customer/v13/Entities" d4p1:nil="false" xmlns:d4p1="http://www.w3.org/2001/XMLSchema-instance">
        <e287:Address>
          <e287:City d4p1:nil="false">ValueHere</e287:City>
          <e287:CountryCode d4p1:nil="false">ValueHere</e287:CountryCode>
          <e287:Id d4p1:nil="false">ValueHere</e287:Id>
          <e287:Line1 d4p1:nil="false">ValueHere</e287:Line1>
          <e287:Line2 d4p1:nil="false">ValueHere</e287:Line2>
          <e287:Line3 d4p1:nil="false">ValueHere</e287:Line3>
          <e287:Line4 d4p1:nil="false">ValueHere</e287:Line4>
          <e287:PostalCode d4p1:nil="false">ValueHere</e287:PostalCode>
          <e287:StateOrProvince d4p1:nil="false">ValueHere</e287:StateOrProvince>
          <e287:TimeStamp d4p1:nil="false">ValueHere</e287:TimeStamp>
          <e287:BusinessName d4p1:nil="false">ValueHere</e287:BusinessName>
        </e287:Address>
      </SuggestedAddresses>
    </ValidateAddressResponse>
  </s:Body>
</s:Envelope>

Code Syntax

The example syntax can be used with Bing Ads SDKs. See Bing Ads API Code Examples for more examples.

public async Task<ValidateAddressResponse> ValidateAddressAsync(
	Address address)
{
	var request = new ValidateAddressRequest
	{
		Address = address
	};

	return (await CustomerManagementService.CallAsync((s, r) => s.ValidateAddressAsync(r), request));
}
static ValidateAddressResponse validateAddress(
	Address address) throws RemoteException, Exception
{
	ValidateAddressRequest request = new ValidateAddressRequest();

	request.setAddress(address);

	return CustomerManagementService.getService().validateAddress(request);
}
static function ValidateAddress(
	$address)
{

	$GLOBALS['Proxy'] = $GLOBALS['CustomerManagementProxy'];

	$request = new ValidateAddressRequest();

	$request->Address = $address;

	return $GLOBALS['CustomerManagementProxy']->GetService()->ValidateAddress($request);
}
response=customermanagement_service.ValidateAddress(
	Address=Address)

Requirements

Service: CustomerManagementService.svc v13
Namespace: https://bingads.microsoft.com/Customer/v13