AddClientLinks Service Operation - Customer Management

Initiates the client link process to manage the account of another customer. Sends an invitation from an agency to a potential client. For more information about the client link lifecycle, see Link to Client Accounts.


The client account must have a valid payment instrument set up for post-pay billing. Prepaid accounts are not supported for management by agencies.

Only an agency may call this service operation. For more information about becoming an agency, see the Resources for agency partners.

The role of the user calling this operation must be Super Admin. For more information, see User Roles and Available Service Operations.

There is no set limit to the amount of client accounts that can be linked to an agency.


This feature is not supported in sandbox.

Request Elements

The AddClientLinksRequest 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.

Request Body Elements

Element Description Data Type
ClientLinks The list of client links to add.

You should limit your request to 10 client links per call.
ClientLink array

Request Header Elements

Element Description Data Type
AuthenticationToken The OAuth access token that represents a Microsoft Account user who has permissions to Bing Ads accounts. string
DeveloperToken The developer token used to access the Bing Ads API. string
Password The Bing Ads managed user's sign-in password. string
UserName The Bing Ads managed user's sign-in name. You must not set this element to a Microsoft account or email address. string


The UserName and Password header elements are deprecated. In future versions of the API, Bing Ads will transition exclusively to Microsoft Account (email address) authentication. For more information, see Authentication with OAuth. UserName and Password are still required for Bing Ads managed credentials, but they are not applicable for Microsoft account authentication. To authenticate a Microsoft account, use the AuthenticationToken] header instead of UserName and Password.

Response Elements

The AddClientLinksResponse 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
OperationErrors A list of one or more reasons why the service operation failed, and no client links were added. OperationError array
PartialErrors An array of OperationError lists that contain details for any client links that were not successfully added.

Results are returned in the same order corresponding to the requested client links. The number of first dimension list elements is equal to the requested client links count. For successfully added client links, the OperationError element at the corresponding index is null.
OperationError 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

The following template shows the order of the body and header elements for the SOAP request.

<s:Envelope xmlns:i="" xmlns:s="">
  <s:Header xmlns="">
    <Action mustUnderstand="1">AddClientLinks</Action>
    <ApplicationToken i:nil="false">ValueHere</ApplicationToken>
    <AuthenticationToken i:nil="false">ValueHere</AuthenticationToken>
    <DeveloperToken i:nil="false">ValueHere</DeveloperToken>
    <Password i:nil="false">ValueHere</Password>
    <UserName i:nil="false">ValueHere</UserName>
    <AddClientLinksRequest xmlns="">
      <ClientLinks xmlns:e307="" i:nil="false">
          <e307:ClientAccountId i:nil="false">ValueHere</e307:ClientAccountId>
          <e307:ClientAccountNumber i:nil="false">ValueHere</e307:ClientAccountNumber>
          <e307:ManagingCustomerId i:nil="false">ValueHere</e307:ManagingCustomerId>
          <e307:ManagingCustomerNumber i:nil="false">ValueHere</e307:ManagingCustomerNumber>
          <e307:Note i:nil="false">ValueHere</e307:Note>
          <e307:Name i:nil="false">ValueHere</e307:Name>
          <e307:InviterEmail i:nil="false">ValueHere</e307:InviterEmail>
          <e307:InviterName i:nil="false">ValueHere</e307:InviterName>
          <e307:InviterPhone i:nil="false">ValueHere</e307:InviterPhone>
          <e307:StartDate i:nil="false">ValueHere</e307:StartDate>
          <e307:Status i:nil="false">ValueHere</e307:Status>
          <e307:Timestamp i:nil="false">ValueHere</e307:Timestamp>
          <ForwardCompatibilityMap xmlns:e308="" i:nil="false">
              <e308:key i:nil="false">ValueHere</e308:key>
              <e308:value i:nil="false">ValueHere</e308:value>

Response SOAP

The following template shows the order of the body and header elements for the SOAP response.

<s:Envelope xmlns:s="">
  <s:Header xmlns="">
    <TrackingId d3p1:nil="false" xmlns:d3p1="">ValueHere</TrackingId>
    <AddClientLinksResponse xmlns="">
      <OperationErrors xmlns:e309="" d4p1:nil="false" xmlns:d4p1="">
          <e309:Details d4p1:nil="false">ValueHere</e309:Details>
          <e309:Message d4p1:nil="false">ValueHere</e309:Message>
      <PartialErrors xmlns:e310="" d4p1:nil="false" xmlns:d4p1="">
            <e310:Details d4p1:nil="false">ValueHere</e310:Details>
            <e310:Message d4p1:nil="false">ValueHere</e310:Message>

Code Syntax

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

public async Task<AddClientLinksResponse> AddClientLinksAsync(
    IList<ClientLink> clientLinks)
    var request = new AddClientLinksRequest
        ClientLinks = clientLinks

    return (await CustomerManagementService.CallAsync((s, r) => s.AddClientLinksAsync(r), request));
static AddClientLinksResponse addClientLinks(
    ArrayOfClientLink clientLinks) throws RemoteException, Exception
    AddClientLinksRequest request = new AddClientLinksRequest();


    return CustomerManagementService.getService().addClientLinks(request);
static function AddClientLinks(

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

    $request = new AddClientLinksRequest();

    $request->ClientLinks = $clientLinks;

    return $GLOBALS['CustomerManagementProxy']->GetService()->AddClientLinks($request);


Service: CustomerManagementService.svc v11