RespondToFeedback

Use this call to reply to feedback that has been left for a user, or to post a follow-up comment to a feedback comment a user has left for someone else. Feedback replies or follow-ups are shown on the user's feedback page on the site, and can be retrieved by using GetFeedback.

Users typically only respond to neutral or negative feedback, so your application could encourage users to only respond to those kinds of feedback, thus helping to ensure that you don't make this call more than is necessary.

Note that you cannot use this call for mutual feedback withdrawal, even though this functionality is available on the eBay site.

Usage Details

RespondToFeedback takes input values for ResponseText, ResponseType, and TargetUserID. You must also supply a combination of FeedbackID, ItemID, and TrasactionID values in order to correctly identify the order line item and user to which your feedback applies.

Testing RespondToFeedback

You can test RespondToFeedback in the Sandbox environment. To test the call, the user must have received feedback to which they can respond, or they must have left feedback to which they can post a follow-up reply.

Before you can test RespondToFeedback, an order line item must have been created. That is, an item was listed (for example, using AddItem) and successfully sold.

1. Create two test users, a seller and a buyer.
2. List an item with your test seller and purchase it using your test buyer.
3. Have the test buyer leave feedback for the seller.
4. Use RespondToFeedback to post a reply on behalf of the seller or a follow-up on behalf of the buyer.

Related Information

See also the reference documentation for this call:

• GetFeedback - Retrieves one, many, or all Feedback records for a specific eBay user.

Input

See also Samples.

The box below lists all fields that could be included in the call request. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).

See also the Deprecated Objects link above. Fields presented in this color are deprecated, and fields presented in this color are (or soon will be) non-operational.

The XML prototype does not include requester credentials. This is a documentation limitation only (see Standard Requester Credentials for Making Calls).

<?xml version="1.0" encoding="utf-8"?>
<RespondToFeedbackRequest xmlns="urn:ebay:apis:eBLBaseComponents">
  <!-- Call-specific Input Fields -->
  <FeedbackID> string </FeedbackID>
  <ItemID> ItemIDType (string) </ItemID>
  <OrderLineItemID> string </OrderLineItemID>
  <ResponseText> string </ResponseText>
  <ResponseType> FeedbackResponseCodeType </ResponseType>
  <TargetUserID> UserIDType (string) </TargetUserID>
  <TransactionID> string </TransactionID>
  <!-- Standard Input Fields -->
  <ErrorLanguage> string </ErrorLanguage>
  <MessageID> string </MessageID>
  <Version> string </Version>
  <WarningLevel> WarningLevelCodeType </WarningLevel>
</RespondToFeedbackRequest>

Output

See also Samples.

The box below lists all fields that might be returned in the response. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).

See also the Deprecated Objects link above. Fields presented in this color are deprecated, and fields presented in this color are not returned (or soon will not be returned) or are not operational (or soon will be non-operational).

<?xml version="1.0" encoding="utf-8"?>
<RespondToFeedbackResponse xmlns="urn:ebay:apis:eBLBaseComponents">
  <!-- (No call-specific Output fields) -->

  <!-- Standard Output Fields -->
  <Ack> AckCodeType </Ack>
  <Build> string </Build>
  <CorrelationID> string </CorrelationID>
  <Errors> ErrorType
    <ErrorClassification> ErrorClassificationCodeType </ErrorClassification>
    <ErrorCode> token </ErrorCode>
    <ErrorParameters ParamID="string"> ErrorParameterType
      <Value> string </Value>
    </ErrorParameters>
    <!-- ... more ErrorParameters nodes allowed here ... -->
    <LongMessage> string </LongMessage>
    <SeverityCode> SeverityCodeType </SeverityCode>
    <ShortMessage> string </ShortMessage>
  </Errors>
  <!-- ... more Errors nodes allowed here ... -->
  <HardExpirationWarning> string </HardExpirationWarning>
  <Timestamp> dateTime </Timestamp>
  <Version> string </Version>
</RespondToFeedbackResponse>

Detail Controls

DetailLevel

This call does not support varying Detail Levels. You do not need to pass DetailLevel in the request.

Samples

New to making API calls? Please see Making a Call.

Note: Some item IDs, user IDs, or other data in these samples might no longer be active on eBay. If necessary, you can substitute current eBay data in your requests.

Replies to feedback left by the buyer.

Description

The seller saw that b************r has left positive feedback for the book she bought and wants to thank her.

You need to supply an ItemID, a TargetUserID, and a TransactionID. Set TransactionID to 0 if there is no specific TransactionID.

Input

XML format.

<?xml version="1.0" encoding="utf-8"?>
<RespondToFeedbackRequest xmlns="urn:ebay:apis:eBLBaseComponents">
  <RequesterCredentials>
    <eBayAuthToken>A*******3</eBayAuthToken>
  </RequesterCredentials>
  <TargetUserID>b************r</TargetUserID>
  <ItemID>1**********4</ItemID> 
  <TransactionID>0</TransactionID>
  <ResponseType>Reply</ResponseType> 
  <ResponseText>Thanks for the positive feedback, we appreciate that!</ResponseText> 
</RespondToFeedbackRequest>

Output

XML format.
<RespondToFeedbackResponse xmlns="urn:ebay:apis:eBLBaseComponents">
  <Timestamp>2019-11-06T18:31:35.892Z</Timestamp>
  <Ack>Success</Ack>
  <Version>1119</Version>
  <Build>E1119_CORE_APIFEEDBACK_19038728_R1</Build>
</RespondToFeedbackResponse>

Change History