Once the conversation ID and type are specified, the status of the specified conversation(s) can then be updated. Using these methods, either the conversation status or read status of a conversation can be changed.

The following fields can be used to update the status of a conversation: 

• conversationStatus: The status for which to update the specified conversation. The following string values are supported: 
  • ACTIVE: This string value updates the conversation to ACTIVE status, meaning that it is a currently active conversation with an eBay member or eBay itself. 
  • ARCHIVE: This string value updates the conversation to ARCHIVE status, meaning that it will be archived, but not deleted. Archived conversations are stored and can be moved back to ACTIVE status using this method if needed. 
  • DELETE:  This string value updates the conversation to DELETE status, meaning that it will be deleted. Deleted conversations cannot be recovered. 
  • READ: This string value updates the conversation to READ status, meaning that it will be shown as being read by the recipient. Note that there is a separate read boolean field in the updateConversation method that takes care of this function.
  • UNREAD: This string value updates the conversation to UNREAD status, meaning that it will be shown as unread by the recipient. Note that there is a separate read boolean field in the updateConversation method that takes care of this function.

Managing communications using the Trading API

Facilitating effective communication between buyers and sellers is crucial for smooth transactions on eBay. This use case outlines the methods available to enable message exchanges between buyer and seller, and to retrieve and manage eBay InBox messages and folders.

The API calls for managing buyer/seller communications are discussed below:

• Use AddMemberMessageAAQToPartner to enable a buyer and a seller in an order relationship to send messages to each other's My Messages Inboxes, fostering direct communication.
• Use AddMemberMessageRTQ to allow a seller to reply to a buyer's question about an active item listing, ensuring prompt responses to inquiries.
• Use AddMemberMessagesAAQToBidder to enable a seller to send up to 10 messages to bidders or users who have made offers via Best Offer, regarding an active item listing, facilitating communication with potential buyers.
• Use GetUserContactDetails to return contact information for a specified user, provided there is a bidding relationship (as either a buyer or seller) between the caller and the user, aiding in direct communication when necessary.

The API calls for retrieving and managing eBay InBox messages and folders are discussed below:

• Use GetMyMessages to retrieve information about the messages sent to a user, providing an overview of all communications received. This call has multiple filters available to control which messages are returned, including date range filters, message folder IDs, or message IDs.
• Use GetMemberMessages to retrieve a list of messages buyers have posted about your active item listings, allowing sellers to address buyer inquiries and concerns.
• Use GetMessagePreferences to return a seller's Ask Seller a Question (ASQ) subjects, each in its own Subject field, enabling sellers to view their current message preferences.
• Use SetMessagePreferences to enable a seller to add, remove, or modify custom Ask Seller a Question (ASQ) subjects, or to reset any custom subjects to their default values.
• Use ReviseMyMessages to mark messages as Read, to flag or unflag messages, and/or to move all specified messages into a different InBox folder.
• Use ReviseMyMessagesFolders to create a new folder, rename an existing folder, or delete an empty folder.
• Use DeleteMyMessages to delete selected messages for a given user.

Handling feedback

Effective feedback management builds transparency and trust between buyers and sellers on eBay. This use case explains how to retrieve, leave, and respond to feedback to keep transactions smooth, resolve issues, and maintain a positive reputation. You can use the Feedback API (REST), or the Trading API (legacy) to handle feedback.

Using the Feedback API

The Feedback API manages transaction feedback through the methods contained in the following table.

The following scenarios describe key uses:

• Get items awaiting feedback
  

  To retrieve a list of items that still require feedback, whether acting as buyer or seller, call the getItemsAwaitingFeedback method.

• Retrieve feedback
  

  Use the getFeedback method to gather feedback for a specified user, with filtering options based on transaction, item, comment type, AI-filtered topics, or feedback containing photos. This method also retrieves detailed metrics for sellers. With this in mind, this method supports various feedback retrieval scenarios:

  • All feedback for a user
  • Feedback received by the user
  • Feedback left by the user
  • Specific feedback entries
  • Feedback on a particular listing or line item
  • Feedback of a specific type
  • Feedback for the user acting as either a seller or a buyer
• Retrieve AI-filtered feedback
  

  You can specify a topic and have AI generate any associated applicable feedback items through the getFeedback method. Specify the topic and then only feedback for those listings are returned. For example, to have AI generate and return the last 30 days of positive feedback items associated with shipping as a seller, use: filter=commentType:POSITIVE,topics:shipping,period:30,role:SELLER
  See the topics value in the filter query parameter for specific topics available.

• Leave feedback
  

  Buyers and sellers submit feedback for completed line items by calling the leaveFeedback method.

• Get feedback rating summary
  

  To return aggregated feedback metrics for review, call the getFeedbackRatingSummary method. These ratings are only for sellers and can return metrics like on time delivery, shipping costs, and communication.

• Respond to feedback received
  

  Buyers and sellers can reply to feedback left by their order partner by calling the respondToFeedback method.

• Using rating templates
  

  Rating templates, if used, define the feedback rating options available for transactions, covering key aspects like on-time delivery and overall experience (two examples of detailed seller ratings), and open comments. Detailed seller ratings (DSRs) are only applicable when buyers leave feedback for sellers. Each rating specifies the label presented to users, whether the field is required, the enabled status, and the format of accepted input (predefined choices, range, or free text). Call the getItemsAwaitingFeedback method to return any available rating templates. See the following for examples of rating templates returned.

  
  

  PREDEFINED yes/no rating type for ON_TIME_DELIVERY

  {
    "ratingKey": "ON_TIME_DELIVERY",
    "ratingLabel": "Did this item arrive on time?",
    "required": false,
    "ratingValueType": "PREDEFINED",
    "enabled": true,
    "acceptableValues": [
      {
        "value": "2",
        "valueLabel": "Yes",
        "enabled": true
      },
      {
        "value": "3",
        "valueLabel": "No",
        "enabled": true
        }
    ]
  }

  
  

  PREDEFINED with positive, neutral, and negative feedback for OVERALL_EXPERIENCE

  {
    "ratingKey": "OVERALL_EXPERIENCE",
    "ratingLabel": "How was your experience?",
    "required": true,
    "ratingValueType": "PREDEFINED",
    "enabled": true,
    "acceptableValues": 
    [
      {
        "value": "POSITIVE",
        "valueLabel": "Positive",
        "enabled": true
      },
      {
        "value": "NEUTRAL",
        "valueLabel": "Neutral",
        "enabled": true
      },
      {
        "value": "NEGATIVE",
        "valueLabel": "Negative",
        "enabled": true
      }
    ]
  }

  
  

  Freetext rating type for OVERALL_EXPERIENCE_COMMENT

  {
    "ratingKey": "OVERALL_EXPERIENCE_COMMENT",
    "ratingLabel": "What else would you add?",
    "maximumCharactersAllowed": 500,
    "required": true,
    "ratingValueType": "FREETEXT",
    "enabled": true
  }

  
  

  RANGE rating type that takes values between 1 and 5 for DSR_ITEM_AS_DESCRIBED

  {
    "ratingKey": "DSR_ITEM_AS_DESCRIBED",
    "ratingLabel": "Item description",
    "required": false,
    "ratingValueType": "RANGE",
    "enabled": true,
    "acceptableValues": [
      {
        "value": "1",
        "valueLabel": "Very inaccurate",
        "enabled": true
      },
      {
        "value": "2",
        "valueLabel": "Inaccurate",
        "enabled": true
      },
      {
        "value": "3",
        "valueLabel": "Neither inaccurate nor accurate",
        "enabled": true
      },
      {
        "value": "4",
        "valueLabel": "Accurate",
        "enabled": true
      },
      {
        "value": "5",
        "valueLabel": "Very accurate",
        "enabled": true
      } 
    ]
  }

Using the Trading API to manage feedback

The following API calls manage transaction feedback through the Trading API:

• A seller can use GetFeedback to retrieve Feedback entries they received from a buyer or Feedback entries they left for a buyer. This call also retrieves detailed Feedback ratings and metrics for the seller.
• The GetItemsAwaitingFeedback call will return all sales transactions where the seller has yet to leave Feedback for the buyer.
• A seller uses LeaveFeedback to provide Feedback to the buyer for a specific sales transaction.
• Use RespondToFeedback to address feedback or include follow-up remarks. This allows sellers to clarify any issues or express appreciation, further enhancing buyer-seller relationships.