GetEditorialReasonsByIds Service Operation - Campaign Management

Article
03/20/2023

Gets the reasons why the specified entities failed editorial review and whether the issue 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.

Note

Unless otherwise noted below, all request elements are required.

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. The supported entity type values are Ad and Keyword.	EntityType

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
CustomerAccountId	The identifier of the ad account that owns or is associated with the entities in the request. This header element must have the same value as the AccountId body element when both are required. This element is required for most service operations, and as a best practice you should always set it. For more information see Get Your Account and Customer IDs.	string
CustomerId	The identifier of the manager account (customer) the user is accessing or operating from. A user can have access to multiple manager accounts. This element is required for most service operations, and as a best practice you should always set it. For more information see Get Your Account and Customer IDs.	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 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

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/CampaignManagement/v13">
    <Action mustUnderstand="1">GetEditorialReasonsByIds</Action>
    <AuthenticationToken i:nil="false">ValueHere</AuthenticationToken>
    <CustomerAccountId i:nil="false">ValueHere</CustomerAccountId>
    <CustomerId i:nil="false">ValueHere</CustomerId>
    <DeveloperToken i:nil="false">ValueHere</DeveloperToken>
  </s:Header>
  <s:Body>
    <GetEditorialReasonsByIdsRequest xmlns="https://bingads.microsoft.com/CampaignManagement/v13">
      <AccountId>ValueHere</AccountId>
      <EntityIdToParentIdAssociations i:nil="false">
        <EntityIdToParentIdAssociation>
          <EntityId>ValueHere</EntityId>
          <ParentId>ValueHere</ParentId>
        </EntityIdToParentIdAssociation>
      </EntityIdToParentIdAssociations>
      <EntityType>ValueHere</EntityType>
    </GetEditorialReasonsByIdsRequest>
  </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/CampaignManagement/v13">
    <TrackingId d3p1:nil="false" xmlns:d3p1="http://www.w3.org/2001/XMLSchema-instance">ValueHere</TrackingId>
  </s:Header>
  <s:Body>
    <GetEditorialReasonsByIdsResponse xmlns="https://bingads.microsoft.com/CampaignManagement/v13">
      <EditorialReasons d4p1:nil="false" xmlns:d4p1="http://www.w3.org/2001/XMLSchema-instance">
        <EditorialReasonCollection>
          <AdGroupId>ValueHere</AdGroupId>
          <AdOrKeywordId>ValueHere</AdOrKeywordId>
          <AppealStatus>ValueHere</AppealStatus>
          <Reasons d4p1:nil="false">
            <EditorialReason>
              <Location d4p1:nil="false">ValueHere</Location>
              <PublisherCountries d4p1:nil="false" xmlns:a1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
                <a1:string>ValueHere</a1:string>
              </PublisherCountries>
              <ReasonCode>ValueHere</ReasonCode>
              <Term d4p1:nil="false">ValueHere</Term>
            </EditorialReason>
          </Reasons>
        </EditorialReasonCollection>
      </EditorialReasons>
      <PartialErrors d4p1:nil="false" xmlns:d4p1="http://www.w3.org/2001/XMLSchema-instance">
        <BatchError d4p1:type="-- derived type specified here with the appropriate prefix --">
          <Code>ValueHere</Code>
          <Details d4p1:nil="false">ValueHere</Details>
          <ErrorCode d4p1:nil="false">ValueHere</ErrorCode>
          <FieldPath d4p1:nil="false">ValueHere</FieldPath>
          <ForwardCompatibilityMap xmlns:e143="http://schemas.datacontract.org/2004/07/System.Collections.Generic" d4p1:nil="false">
            <e143:KeyValuePairOfstringstring>
              <e143:key d4p1:nil="false">ValueHere</e143:key>
              <e143:value d4p1:nil="false">ValueHere</e143:value>
            </e143:KeyValuePairOfstringstring>
          </ForwardCompatibilityMap>
          <Index>ValueHere</Index>
          <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>
          <ReasonCode>ValueHere</ReasonCode>
        </BatchError>
      </PartialErrors>
    </GetEditorialReasonsByIdsResponse>
  </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<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();

	request.setAccountId(accountId);
	request.setEntityIdToParentIdAssociations(entityIdToParentIdAssociations);
	request.setEntityType(entityType);

	return CampaignManagementService.getService().getEditorialReasonsByIds(request);
}

static function GetEditorialReasonsByIds(
	$accountId,
	$entityIdToParentIdAssociations,
	$entityType)
{

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

	$request = new GetEditorialReasonsByIdsRequest();

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

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

response=campaignmanagement_service.GetEditorialReasonsByIds(
	AccountId=AccountId,
	EntityIdToParentIdAssociations=EntityIdToParentIdAssociations,
	EntityType=EntityType)

Requirements

Service: CampaignManagementService.svc v13
Namespace: https://bingads.microsoft.com/CampaignManagement/v13

Share via