GetEditorialReasonsByIds Service Operation - Campaign Management

Gets the reasons why the specified entities failed editorial review and whether the rejection is appealable.

Request Elements

The GetEditorialReasonsByIdsRequest 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
AccountId The identifier of the account that contains the specified entities. long
EntityIdToParentIdAssociations A list of EntityIdToParentIdAssociation objects that each contain the unique system identifier of an entity such as ad or keyword, and the identifier of its parent. An ad group is the parent of an ad or keyword.

The list must include all ads or all keywords which failed editorial review. The list cannot include a mix ads and keywords. The list can contain a maximum of 1,000 identifiers.
EntityIdToParentIdAssociation array
EntityType The type of entities that the entity list contains. EntityType

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
CustomerAccountId The identifier of the account that owns the entities in the request. This header element must have the same value as the AccountId body element when both are required. string
CustomerId The identifier of the customer that contains and owns the account. If you manage an account of another customer, you should use that customer ID instead of your own customer ID. 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.


The CustomerAccountId and CustomerId are required for most service operations, and as a best practice you should always specify them in the request.

Response Elements

The GetEditorialReasonsByIdsResponse 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
EditorialReasons An array of EditorialReasonCollection objects that corresponds directly to the EntityIdToParentIdAssociation objects that you specified in the request. Each object identifies the reason for the failure and whether it is appealable. Items of the list may be returned as null. For each list index where an EditorialReasonCollection was not retrieved, the corresponding element will be null.

If the entity had not failed editorial review, the corresponding item in this collection is NULL. In addition, the item will be NULL if the specified ad or keyword identifier is not valid.
EditorialReasonCollection array
PartialErrors An array of BatchError objects that contain details for any request items that were not successful.

The list of errors do not correspond directly to the list of items in the request. The list can be empty if there were no errors, or can include one or more error objects corresponding to each unsuccessful list item in the request.
BatchError 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">GetEditorialReasonsByIds</Action>
    <ApplicationToken i:nil="false">ValueHere</ApplicationToken>
    <AuthenticationToken i:nil="false">ValueHere</AuthenticationToken>
    <CustomerAccountId i:nil="false">ValueHere</CustomerAccountId>
    <CustomerId i:nil="false">ValueHere</CustomerId>
    <DeveloperToken i:nil="false">ValueHere</DeveloperToken>
    <Password i:nil="false">ValueHere</Password>
    <UserName i:nil="false">ValueHere</UserName>
    <GetEditorialReasonsByIdsRequest xmlns="">
      <EntityIdToParentIdAssociations xmlns:e233="" i:nil="false">

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>
    <GetEditorialReasonsByIdsResponse xmlns="">
      <EditorialReasons d4p1:nil="false" xmlns:d4p1="">
          <Reasons d4p1:nil="false">
              <Location d4p1:nil="false">ValueHere</Location>
              <PublisherCountries d4p1:nil="false" xmlns:a1="">
              <Term d4p1:nil="false">ValueHere</Term>
      <PartialErrors d4p1:nil="false" xmlns:d4p1="">
        <BatchError d4p1:type="-- derived type specified here with the appropriate prefix --">
          <Details d4p1:nil="false">ValueHere</Details>
          <ErrorCode d4p1:nil="false">ValueHere</ErrorCode>
          <FieldPath d4p1:nil="false">ValueHere</FieldPath>
          <ForwardCompatibilityMap xmlns:e234="" d4p1:nil="false">
              <e234:key d4p1:nil="false">ValueHere</e234:key>
              <e234:value d4p1:nil="false">ValueHere</e234:value>
          <Message d4p1:nil="false">ValueHere</Message>
          <Type d4p1:nil="false">ValueHere</Type>
          <!--These fields are applicable if the derived type attribute is set to EditorialError-->
          <Appealable d4p1:nil="false">ValueHere</Appealable>
          <DisapprovedText d4p1:nil="false">ValueHere</DisapprovedText>
          <Location d4p1:nil="false">ValueHere</Location>
          <PublisherCountry d4p1:nil="false">ValueHere</PublisherCountry>

Code Syntax

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

public async Task<GetEditorialReasonsByIdsResponse> GetEditorialReasonsByIdsAsync(
    long accountId,
    IList<EntityIdToParentIdAssociation> entityIdToParentIdAssociations,
    EntityType entityType)
    var request = new GetEditorialReasonsByIdsRequest
        AccountId = accountId,
        EntityIdToParentIdAssociations = entityIdToParentIdAssociations,
        EntityType = entityType

    return (await CampaignManagementService.CallAsync((s, r) => s.GetEditorialReasonsByIdsAsync(r), request));
static GetEditorialReasonsByIdsResponse getEditorialReasonsByIds(
    java.lang.Long accountId,
    ArrayOfEntityIdToParentIdAssociation entityIdToParentIdAssociations,
    EntityType entityType) throws RemoteException, Exception
    GetEditorialReasonsByIdsRequest request = new GetEditorialReasonsByIdsRequest();


    return CampaignManagementService.getService().getEditorialReasonsByIds(request);
static function GetEditorialReasonsByIds(

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

    $request = new GetEditorialReasonsByIdsRequest();

    $request->AccountId = $accountId;
    $request->EntityIdToParentIdAssociations = $entityIdToParentIdAssociations;
    $request->EntityType = $entityType;

    return $GLOBALS['CampaignManagementProxy']->GetService()->GetEditorialReasonsByIds($request);


Service: CampaignManagementService.svc v11