ebay-mcp 1.4.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (205) hide show
  1. package/LICENSE +201 -0
  2. package/README.md +586 -0
  3. package/build/api/account-management/account.d.ts +216 -0
  4. package/build/api/account-management/account.js +305 -0
  5. package/build/api/analytics-and-report/analytics.d.ts +33 -0
  6. package/build/api/analytics-and-report/analytics.js +102 -0
  7. package/build/api/client.d.ts +89 -0
  8. package/build/api/client.js +343 -0
  9. package/build/api/communication/feedback.d.ts +45 -0
  10. package/build/api/communication/feedback.js +119 -0
  11. package/build/api/communication/message.d.ts +55 -0
  12. package/build/api/communication/message.js +131 -0
  13. package/build/api/communication/negotiation.d.ts +39 -0
  14. package/build/api/communication/negotiation.js +97 -0
  15. package/build/api/communication/notification.d.ts +128 -0
  16. package/build/api/communication/notification.js +373 -0
  17. package/build/api/index.d.ts +96 -0
  18. package/build/api/index.js +121 -0
  19. package/build/api/listing-management/inventory.d.ts +216 -0
  20. package/build/api/listing-management/inventory.js +633 -0
  21. package/build/api/listing-metadata/metadata.d.ts +154 -0
  22. package/build/api/listing-metadata/metadata.js +485 -0
  23. package/build/api/listing-metadata/taxonomy.d.ts +38 -0
  24. package/build/api/listing-metadata/taxonomy.js +58 -0
  25. package/build/api/marketing-and-promotions/marketing.d.ts +395 -0
  26. package/build/api/marketing-and-promotions/marketing.js +565 -0
  27. package/build/api/marketing-and-promotions/recommendation.d.ts +20 -0
  28. package/build/api/marketing-and-promotions/recommendation.js +32 -0
  29. package/build/api/order-management/dispute.d.ts +65 -0
  30. package/build/api/order-management/dispute.js +69 -0
  31. package/build/api/order-management/fulfillment.d.ts +80 -0
  32. package/build/api/order-management/fulfillment.js +89 -0
  33. package/build/api/other/compliance.d.ts +26 -0
  34. package/build/api/other/compliance.js +47 -0
  35. package/build/api/other/edelivery.d.ts +153 -0
  36. package/build/api/other/edelivery.js +219 -0
  37. package/build/api/other/identity.d.ts +17 -0
  38. package/build/api/other/identity.js +24 -0
  39. package/build/api/other/translation.d.ts +14 -0
  40. package/build/api/other/translation.js +22 -0
  41. package/build/api/other/vero.d.ts +30 -0
  42. package/build/api/other/vero.js +48 -0
  43. package/build/auth/oauth-metadata.d.ts +46 -0
  44. package/build/auth/oauth-metadata.js +59 -0
  45. package/build/auth/oauth-middleware.d.ts +35 -0
  46. package/build/auth/oauth-middleware.js +99 -0
  47. package/build/auth/oauth-types.d.ts +66 -0
  48. package/build/auth/oauth-types.js +4 -0
  49. package/build/auth/oauth.d.ts +93 -0
  50. package/build/auth/oauth.js +383 -0
  51. package/build/auth/scope-utils.d.ts +70 -0
  52. package/build/auth/scope-utils.js +304 -0
  53. package/build/auth/token-verifier.d.ts +57 -0
  54. package/build/auth/token-verifier.js +172 -0
  55. package/build/config/environment.d.ts +61 -0
  56. package/build/config/environment.js +260 -0
  57. package/build/index.d.ts +1 -0
  58. package/build/index.js +98 -0
  59. package/build/schemas/account-management/account.d.ts +5324 -0
  60. package/build/schemas/account-management/account.js +366 -0
  61. package/build/schemas/analytics/analytics.d.ts +167 -0
  62. package/build/schemas/analytics/analytics.js +191 -0
  63. package/build/schemas/communication/messages.d.ts +1872 -0
  64. package/build/schemas/communication/messages.js +348 -0
  65. package/build/schemas/fulfillment/orders.d.ts +4655 -0
  66. package/build/schemas/fulfillment/orders.js +317 -0
  67. package/build/schemas/index.d.ts +2100 -0
  68. package/build/schemas/index.js +68 -0
  69. package/build/schemas/inventory-management/inventory.d.ts +6419 -0
  70. package/build/schemas/inventory-management/inventory.js +450 -0
  71. package/build/schemas/marketing/marketing.d.ts +14181 -0
  72. package/build/schemas/marketing/marketing.js +1088 -0
  73. package/build/schemas/metadata/metadata.d.ts +5259 -0
  74. package/build/schemas/metadata/metadata.js +614 -0
  75. package/build/schemas/other/other-apis.d.ts +257 -0
  76. package/build/schemas/other/other-apis.js +372 -0
  77. package/build/schemas/taxonomy/taxonomy.d.ts +215 -0
  78. package/build/schemas/taxonomy/taxonomy.js +571 -0
  79. package/build/scripts/auto-setup.d.ts +12 -0
  80. package/build/scripts/auto-setup.js +277 -0
  81. package/build/scripts/diagnostics.d.ts +8 -0
  82. package/build/scripts/diagnostics.js +299 -0
  83. package/build/scripts/download-specs.d.ts +1 -0
  84. package/build/scripts/download-specs.js +116 -0
  85. package/build/scripts/interactive-setup.d.ts +21 -0
  86. package/build/scripts/interactive-setup.js +723 -0
  87. package/build/server-http.d.ts +11 -0
  88. package/build/server-http.js +361 -0
  89. package/build/tools/definitions/account-with-schemas.d.ts +39 -0
  90. package/build/tools/definitions/account-with-schemas.js +170 -0
  91. package/build/tools/definitions/account.d.ts +12 -0
  92. package/build/tools/definitions/account.js +428 -0
  93. package/build/tools/definitions/analytics.d.ts +25 -0
  94. package/build/tools/definitions/analytics.js +66 -0
  95. package/build/tools/definitions/communication.d.ts +12 -0
  96. package/build/tools/definitions/communication.js +151 -0
  97. package/build/tools/definitions/fulfillment.d.ts +12 -0
  98. package/build/tools/definitions/fulfillment.js +326 -0
  99. package/build/tools/definitions/index.d.ts +25 -0
  100. package/build/tools/definitions/index.js +37 -0
  101. package/build/tools/definitions/inventory.d.ts +12 -0
  102. package/build/tools/definitions/inventory.js +429 -0
  103. package/build/tools/definitions/marketing.d.ts +12 -0
  104. package/build/tools/definitions/marketing.js +1095 -0
  105. package/build/tools/definitions/metadata.d.ts +12 -0
  106. package/build/tools/definitions/metadata.js +188 -0
  107. package/build/tools/definitions/other.d.ts +13 -0
  108. package/build/tools/definitions/other.js +309 -0
  109. package/build/tools/definitions/taxonomy.d.ts +25 -0
  110. package/build/tools/definitions/taxonomy.js +64 -0
  111. package/build/tools/definitions/token-management.d.ts +35 -0
  112. package/build/tools/definitions/token-management.js +103 -0
  113. package/build/tools/index.d.ts +11 -0
  114. package/build/tools/index.js +1003 -0
  115. package/build/tools/schemas.d.ts +14764 -0
  116. package/build/tools/schemas.js +667 -0
  117. package/build/tools/tool-definitions.d.ts +35 -0
  118. package/build/tools/tool-definitions.js +3534 -0
  119. package/build/types/application-settings/developerAnalyticsV1BetaOas3.d.ts +197 -0
  120. package/build/types/application-settings/developerAnalyticsV1BetaOas3.js +5 -0
  121. package/build/types/application-settings/developerClientRegistrationV1Oas3.d.ts +155 -0
  122. package/build/types/application-settings/developerClientRegistrationV1Oas3.js +5 -0
  123. package/build/types/application-settings/developerKeyManagementV1Oas3.d.ts +246 -0
  124. package/build/types/application-settings/developerKeyManagementV1Oas3.js +5 -0
  125. package/build/types/ebay-enums.d.ts +1204 -0
  126. package/build/types/ebay-enums.js +1330 -0
  127. package/build/types/ebay.d.ts +143 -0
  128. package/build/types/ebay.js +123 -0
  129. package/build/types/index.d.ts +6 -0
  130. package/build/types/index.js +10 -0
  131. package/build/types/sell-apps/account-management/sellAccountV1Oas3.d.ts +2579 -0
  132. package/build/types/sell-apps/account-management/sellAccountV1Oas3.js +5 -0
  133. package/build/types/sell-apps/analytics-and-report/sellAnalyticsV1Oas3.d.ts +446 -0
  134. package/build/types/sell-apps/analytics-and-report/sellAnalyticsV1Oas3.js +5 -0
  135. package/build/types/sell-apps/communication/commerceFeedbackV1BetaOas3.d.ts +705 -0
  136. package/build/types/sell-apps/communication/commerceFeedbackV1BetaOas3.js +5 -0
  137. package/build/types/sell-apps/communication/commerceMessageV1Oas3.d.ts +590 -0
  138. package/build/types/sell-apps/communication/commerceMessageV1Oas3.js +5 -0
  139. package/build/types/sell-apps/communication/commerceNotificationV1Oas3.d.ts +1276 -0
  140. package/build/types/sell-apps/communication/commerceNotificationV1Oas3.js +5 -0
  141. package/build/types/sell-apps/communication/sellNegotiationV1Oas3.d.ts +277 -0
  142. package/build/types/sell-apps/communication/sellNegotiationV1Oas3.js +5 -0
  143. package/build/types/sell-apps/listing-management/sellInventoryV1Oas3.d.ts +3133 -0
  144. package/build/types/sell-apps/listing-management/sellInventoryV1Oas3.js +5 -0
  145. package/build/types/sell-apps/listing-metadata/sellMetadataV1Oas3.d.ts +2289 -0
  146. package/build/types/sell-apps/listing-metadata/sellMetadataV1Oas3.js +5 -0
  147. package/build/types/sell-apps/markeitng-and-promotions/sellMarketingV1Oas3.d.ts +6650 -0
  148. package/build/types/sell-apps/markeitng-and-promotions/sellMarketingV1Oas3.js +5 -0
  149. package/build/types/sell-apps/markeitng-and-promotions/sellRecommendationV1Oas3.d.ts +172 -0
  150. package/build/types/sell-apps/markeitng-and-promotions/sellRecommendationV1Oas3.js +5 -0
  151. package/build/types/sell-apps/order-management/sellFulfillmentV1Oas3.d.ts +1869 -0
  152. package/build/types/sell-apps/order-management/sellFulfillmentV1Oas3.js +5 -0
  153. package/build/types/sell-apps/other-apis/commerceIdentityV1Oas3.d.ts +178 -0
  154. package/build/types/sell-apps/other-apis/commerceIdentityV1Oas3.js +5 -0
  155. package/build/types/sell-apps/other-apis/commerceTranslationV1BetaOas3.d.ts +128 -0
  156. package/build/types/sell-apps/other-apis/commerceTranslationV1BetaOas3.js +5 -0
  157. package/build/types/sell-apps/other-apis/commerceVeroV1Oas3.d.ts +417 -0
  158. package/build/types/sell-apps/other-apis/commerceVeroV1Oas3.js +5 -0
  159. package/build/types/sell-apps/other-apis/sellComplianceV1Oas3.d.ts +273 -0
  160. package/build/types/sell-apps/other-apis/sellComplianceV1Oas3.js +5 -0
  161. package/build/types/sell-apps/other-apis/sellEdeliveryInternationalShippingOas3.d.ts +2537 -0
  162. package/build/types/sell-apps/other-apis/sellEdeliveryInternationalShippingOas3.js +5 -0
  163. package/build/types/sell-apps/other-apis/sellMarketingV1Oas3.d.ts +6650 -0
  164. package/build/types/sell-apps/other-apis/sellMarketingV1Oas3.js +5 -0
  165. package/build/types/sell-apps/other-apis/sellRecommendationV1Oas3.d.ts +172 -0
  166. package/build/types/sell-apps/other-apis/sellRecommendationV1Oas3.js +5 -0
  167. package/build/utils/account-management/account.d.ts +1094 -0
  168. package/build/utils/account-management/account.js +831 -0
  169. package/build/utils/communication/feedback.d.ts +152 -0
  170. package/build/utils/communication/feedback.js +216 -0
  171. package/build/utils/communication/message.d.ts +174 -0
  172. package/build/utils/communication/message.js +242 -0
  173. package/build/utils/communication/negotiation.d.ts +123 -0
  174. package/build/utils/communication/negotiation.js +150 -0
  175. package/build/utils/communication/notification.d.ts +370 -0
  176. package/build/utils/communication/notification.js +369 -0
  177. package/build/utils/date-converter.d.ts +59 -0
  178. package/build/utils/date-converter.js +160 -0
  179. package/build/utils/llm-client-detector.d.ts +54 -0
  180. package/build/utils/llm-client-detector.js +318 -0
  181. package/build/utils/oauth-helper.d.ts +37 -0
  182. package/build/utils/oauth-helper.js +315 -0
  183. package/build/utils/order-management/dispute.d.ts +346 -0
  184. package/build/utils/order-management/dispute.js +369 -0
  185. package/build/utils/order-management/fulfillment.d.ts +200 -0
  186. package/build/utils/order-management/fulfillment.js +205 -0
  187. package/build/utils/other/compliance.d.ts +49 -0
  188. package/build/utils/other/compliance.js +76 -0
  189. package/build/utils/other/edelivery.d.ts +310 -0
  190. package/build/utils/other/edelivery.js +241 -0
  191. package/build/utils/other/identity.d.ts +13 -0
  192. package/build/utils/other/identity.js +13 -0
  193. package/build/utils/other/translation.d.ts +28 -0
  194. package/build/utils/other/translation.js +41 -0
  195. package/build/utils/other/vero.d.ts +61 -0
  196. package/build/utils/other/vero.js +90 -0
  197. package/build/utils/scope-helper.d.ts +49 -0
  198. package/build/utils/scope-helper.js +207 -0
  199. package/build/utils/security-checker.d.ts +46 -0
  200. package/build/utils/security-checker.js +248 -0
  201. package/build/utils/setup-validator.d.ts +25 -0
  202. package/build/utils/setup-validator.js +305 -0
  203. package/build/utils/token-utils.d.ts +40 -0
  204. package/build/utils/token-utils.js +40 -0
  205. package/package.json +115 -0
@@ -0,0 +1,705 @@
1
+ /**
2
+ * This file was auto-generated by openapi-typescript.
3
+ * Do not make direct changes to the file.
4
+ */
5
+ export interface paths {
6
+ '/awaiting_feedback': {
7
+ parameters: {
8
+ query?: never;
9
+ header?: never;
10
+ path?: never;
11
+ cookie?: never;
12
+ };
13
+ /** @description This method retrieves line items awaiting feedback from the user's order partner. You can refine the results using optional filter query parameters, such as item ID, user name, or user role in the transaction. Sorting and pagination features help organize and navigate returned items efficiently.<p>For sellers, only sold items that have not yet received feedback are included. For buyers, only purchased items for which feedback is still pending are included. If the user is both a buyer and a seller, this API returns items awaiting feedback for transactions where the user acted as either. Applying filters can limit results to either buyer-only or seller-only transactions. </p><p>The response provides an overview of feedback yet to be left for completed transactions (as filtered), with counts for both the buyer and seller roles. It includes an array of line items, each containing the listing ID, title, price (with currency and value). For each line item, the response offers feedback templates specifying which ratings are available.</p><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>Detailed seller ratings are for sellers only, and are created from buyer feedback.</span></p> */
14
+ get: operations['getItemsAwaitingFeedback'];
15
+ put?: never;
16
+ post?: never;
17
+ delete?: never;
18
+ options?: never;
19
+ head?: never;
20
+ patch?: never;
21
+ trace?: never;
22
+ };
23
+ '/feedback': {
24
+ parameters: {
25
+ query?: never;
26
+ header?: never;
27
+ path?: never;
28
+ cookie?: never;
29
+ };
30
+ /** @description This method enables users to retrieve feedback for any specified user ID and feedback type (sent or received). You can refine the results using optional query parameters such as its feedback ID, listing ID, or order line item ID, or applying one or more filters.<p>Applying filters can narrow results using criteria such as comment type, photos, or topics identified through AI-based analysis. When filtering for feedback with photos (<code>filterImage:true</code>), only entries with images (entries that include image URLs) are returned. Additionally, feedback can be refined for the number of days to look back, the role of the user providing the feedback, and whether to include automated feedback entries left by eBay.</p><p>Sorting and pagination features help organize and navigate returned items efficiently.</p><p>Returned data includes feedback details (such as comment text and type), feedback ratings (covering criteria like overall experience, and for sellers item description, shipping time, and communication), role and attributes of the feedback giver, line item and transaction summaries, images, and any available topics. See <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#uri.filter" >filter</a> for additional information. Privacy is safeguarded by restricting the amount of detail visible to users, depending on their context. When accessing another user's feedback without logging in, buyer names are masked and seller names are shown. Logged-in users viewing their own feedback see all names, while those viewing other users' feedback will encounter some masking.</p> */
31
+ get: operations['getFeedback'];
32
+ put?: never;
33
+ /** @description This method creates and submits feedback to the user's order partner for a line item in the order. For each order, the order partner is the other participant in the transaction, either the buyer or seller, depending on the eBay user associated with the user token. This method allows users to provide detailed information about the transaction, including the feedback rating, comments, and seller delivery. You can also add images to your feedback.<p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>A seller can only provide a comment for a buyer, but a buyer can provide a comment plus provides ratings on a number of metrics for a seller.</span></p> <p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>The feedback must adhere to community guidelines and be relevant to the transaction.</span></p> <p>When leaving feedback, keep the following in mind:<ul><li>Your feedback score is not affected when you leave feedback</li><li>Feedback can only be revised once after it is submitted</li></ul></p><p>For additional information on leaving feedback, see the following:<ul><li><a href="https://www.ebay.com/help/buying/leaving-feedback-sellers/leaving-feedback-sellers?id=4007" target="_blank">Leaving feedback for sellers</a></li><li><a href="https://www.ebay.com/help/selling/leaving-feedback-buyers/leaving-feedback-buyers?id=4078" target="_blank">Leaving feedback for buyers</a></li></ul></p><p>A successful call to this method returns a feedback ID, which is a unique identifier for the newly created feedback and allows for reference and tracking. </p> */
34
+ post: operations['leaveFeedback'];
35
+ delete?: never;
36
+ options?: never;
37
+ head?: never;
38
+ patch?: never;
39
+ trace?: never;
40
+ };
41
+ '/feedback_rating_summary': {
42
+ parameters: {
43
+ query?: never;
44
+ header?: never;
45
+ path?: never;
46
+ cookie?: never;
47
+ };
48
+ /** @description This method provides a detailed overview of feedback ratings associated with a user in the eBay marketplace. Specify a user ID and apply filters to retrieve summarized feedback data categorized by rating types and user roles. These returned metrics are aggregated, which offers insight into user experiences and performance. <p class="msgbox_tipInDiv" ><div class="msgbox_tip"><span><b><span style="color: #478415;">Tip:</span></b></span></span> You can use this method to help sellers and buyers understand their marketplace reputation and identify areas for improvement.</div></p><p>Returned data provides a summary of feedback ratings for a user by rating type (such as overall experience, communication, or delivery timeliness) for both buyer and seller roles. Each type of rating includes aggregated metrics like averages, counts, unique feedback givers, and the percentage of positive ratings (excluding neutrals). The response also details the distribution of specific rating values, their frequency, and time period (with period units like days or months) over which these metrics were calculated.</p> */
49
+ get: operations['getFeedbackRatingSummary'];
50
+ put?: never;
51
+ post?: never;
52
+ delete?: never;
53
+ options?: never;
54
+ head?: never;
55
+ patch?: never;
56
+ trace?: never;
57
+ };
58
+ '/respond_to_feedback': {
59
+ parameters: {
60
+ query?: never;
61
+ header?: never;
62
+ path?: never;
63
+ cookie?: never;
64
+ };
65
+ get?: never;
66
+ put?: never;
67
+ /** @description This method allows users to respond to feedback provided by the order partner for a specific line item in an order. For each order, the order partner is the other participant in the transaction, either the buyer or seller, depending on the eBay user associated with the user token. This method allows the user to provide additional context or address the order partner's feedback.<p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>The feedback response must adhere to community guidelines and be relevant to the transaction.</span></p><p>You can only use this method if feedback has been provided by the order partner and you have not yet responded to it. </p> <p>When responding to feedback, your feedback score is not affected when you respond to feedback.</p><p>For additional information on leaving feedback, see the following:<ul><li><a href="https://www.ebay.com/help/buying/leaving-feedback-sellers/leaving-feedback-sellers?id=4007" target="_blank">Leaving feedback for sellers</a></li><li><a href="https://www.ebay.com/help/selling/leaving-feedback-buyers/leaving-feedback-buyers?id=4078" target="_blank">Leaving feedback for buyers</a></li></ul></p><p>A successful call returns an HTTP status of <b>200 Success</b>.</p> */
68
+ post: operations['respondToFeedback'];
69
+ delete?: never;
70
+ options?: never;
71
+ head?: never;
72
+ patch?: never;
73
+ trace?: never;
74
+ };
75
+ }
76
+ export type webhooks = Record<string, never>;
77
+ export interface components {
78
+ schemas: {
79
+ /** @description This type contains the details for each line item awaiting feedback. */
80
+ AwaitingFeedback: {
81
+ /** @description This is the unique identifier for the listing associated with the line item. It is used to reference the specific listing for which feedback is being awaited. */
82
+ listingId?: string;
83
+ /** @description This container shows the sales price of the listing. */
84
+ listingPrice?: components['schemas']['ListingPrice'];
85
+ /** @description The title of the listing. */
86
+ listingTitle?: string;
87
+ /** @description The unique identifier for the eBay order line item associated with the listing. It is used to pinpoint the exact line item for which feedback is being awaited. */
88
+ orderLineItemId?: string;
89
+ /** @description This array contains a list of available values for use in a particular rating, and whether the value is enabled. This is dependent on what seller ratings the buyer's order partner qualifies.<br><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>Rating templates should only be returned to the user in their role as a buyer; only sellers have Detailed Seller Ratings (DSRs). </span></p><p>Use the metadata returned here when leaving DSR ratings through the <b>leaveFeedback</b> method. The key field in this container is the <b>ratingKey</b> field. See <a href="/api-docs/commerce/feedback/types/fdb:FeedbackRatingTypeEnum" >FeedbackRatingTypeEnum</a> for its values. The other metadata returned in this container apply to each <b>ratingKey</b> value that is returned.</p> */
90
+ ratingTemplates?: components['schemas']['FeedbackRatingTemplateType'][];
91
+ /** @description The unique identifier of the sales transaction. */
92
+ transactionId?: string;
93
+ };
94
+ /** @description This type defines the fields for the <b>getItemsAwaitingFeedback</b> response. */
95
+ AwaitingFeedbackResponse: {
96
+ /** @description This container returns the number of line items awaiting feedback. The <b>asSeller</b> and <b>asBuyer</b> fields return the total count of items awaiting feedback as seller and buyer and are not affected by the <b>userRole</b> filter. */
97
+ itemsAwaitingFeedbackCount?: components['schemas']['ItemsAwaitingFeedbackCount'];
98
+ /** @description This array contains the details for each line item awaiting feedback. An empty array is returned if no line items are awaiting feedback or that match the filter criteria. */
99
+ lineItems?: components['schemas']['AwaitingFeedback'][];
100
+ /** @description This container provides pagination information for the returned line items awaiting feedback (as filtered). */
101
+ pagination?: components['schemas']['Pagination'];
102
+ };
103
+ /** @description This type provides the details of the feedback comment left by the user. */
104
+ Comment: {
105
+ /** @description This container indicates the timing of a feedback comment based on when it was left. It is only returned if a comment was provided. Possible values are 30 days, 90 days, 180 days, 365 days, or 5 years: <br><ul><li>Less than 30 days: 30 DAY</li> <li>Over 30 but less than 90 days: 90 DAY</li> <li>Over 90 but less than 180 days: 180 DAY</li> <li>Over 180 but less than 365 days: 365 DAY</li> <li>More than 365 days: 5 YEAR</li></ul> */
106
+ commentPeriod?: components['schemas']['CommentCommentPeriod'];
107
+ /** @description The text of the feedback comment, follow-up, or reply. HTML formatting and personal information (for example, phone numbers) are not allowed. This field is returned if a comment was provided for the feedback entry. If the comment was removed due to eBay policy, this field will contain '<code>--</code>' and the <b>commentTextRemovedPerPolicy</b> field will return <code>true</code>. */
108
+ commentText?: string;
109
+ /** @description If <code>true</code>, this boolean indicates the feedback follow-up or reply comment text was removed per eBay policy. This field is only returned when a <b>followupComment</b> container is returned. */
110
+ commentTextRemovedPerPolicy?: boolean;
111
+ /** @description This enumerated value indicates the state of the feedback (for example, <code>ENTERED</code>). This can be the state of the feedback comment, the follow-up comment, or the reply comment. For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:FeedbackCommentStateEnum'>eBay API documentation</a> */
112
+ state?: string;
113
+ };
114
+ /** @description This type provides fields that descrbes timing associated with the comment. */
115
+ CommentCommentPeriod: {
116
+ /** @description Unit of time for the <b>value</b>. Supported values: <code>DAY</code>, or <code>YEAR</code>. */
117
+ unit?: string;
118
+ /**
119
+ * Format: int32
120
+ * @description Value of the time period expressed in the period contained in the <b>unit</b>. Supported values: <code>30</code>, <code>60</code>, or <code>365</code>. <p>See the <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#response.feedbackEntries.feedbackComment.commentPeriod">commentPeriod</a> container for more information.</p>
121
+ */
122
+ value?: number;
123
+ };
124
+ /** @description This type defines the fields that can be returned in an error. */
125
+ Error: {
126
+ /** @description Identifies the type of erro. */
127
+ category?: string;
128
+ /** @description Name for the primary system where the error occurred. This is relevant for application errors. */
129
+ domain?: string;
130
+ /**
131
+ * Format: int32
132
+ * @description A unique number to identify the error.
133
+ */
134
+ errorId?: number;
135
+ /** @description An array of request elements most closely associated to the error. */
136
+ inputRefIds?: string[];
137
+ /** @description A more detailed explanation of the error. */
138
+ longMessage?: string;
139
+ /** @description Information on how to correct the problem, in the end user's terms and language where applicable. */
140
+ message?: string;
141
+ /** @description An array of request elements most closely associated to the error. */
142
+ outputRefIds?: string[];
143
+ /** @description An array of name/value pairs that describe details the error condition. These are useful when multiple errors are returned. */
144
+ parameters?: components['schemas']['ErrorParameter'][];
145
+ /** @description Further helps indicate which subsystem the error is coming from. System subcategories include: Initialization, Serialization, Security, Monitoring, Rate Limiting, etc. */
146
+ subdomain?: string;
147
+ };
148
+ ErrorParameter: {
149
+ /** @description The object of the error. */
150
+ name?: string;
151
+ /** @description The value of the object. */
152
+ value?: string;
153
+ };
154
+ /** @description This type provides attributes for returned feedback entries. */
155
+ FeedbackDetail: {
156
+ /** @description If the returned value is <code>true</code>, feedback was generated and added automatically by eBay. If a seller has a feedback score 10 or less, eBay automatically leaves feedback. The buyer can choose to override the eBay feedback and leave feedback normally. <br><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>Detailed Seller Ratings (DSRs) are not provided by ebay, only a predefined comment and a positive rating.</span></p> */
157
+ automatedFeedback?: boolean;
158
+ /** @description This enumerated value indicates the type of feedback: <code>POSITIVE</code>, <code>NEUTRAL</code>, <code>NEGATIVE</code>. <br><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>Sellers can only leave positive feedback for buyers.</span></p> For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:FeedbackRatingValuesEnum'>eBay API documentation</a> */
159
+ commentType?: string;
160
+ /** @description This boolean indicates whether the feedback is eligible for revision. If returned as <code>true</code>, it means the feedback can be modified. Feedback that is older than 30 days or has already been revised once cannot be erased or further revised. */
161
+ eligibleForRevision?: boolean;
162
+ /** @description This container provides the feedback comment left by a user when submitting feedback for a seller or buyer. */
163
+ feedbackComment?: components['schemas']['Comment'];
164
+ /** @description The timestamp when the feedback was submitted. */
165
+ feedbackEnteredDate?: string;
166
+ /** @description This container represents the duration since feedback was entered, expressed as a numeric value and a unit of time in days. */
167
+ feedbackEnteredPeriod?: components['schemas']['FeedbackEnteredPeriod'];
168
+ /** @description The unique identifier of the feedback entry. */
169
+ feedbackId?: string;
170
+ /** @description This array contains a list of ratings attached to feedback.<br><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>This array only applies to buyers feedback for sellers (sellers can only give positive feedback to buyers).</span></p> */
171
+ feedbackRatings?: components['schemas']['FeedbackRating'][];
172
+ /**
173
+ * Format: int32
174
+ * @description The feedback receiver's feedback score after receiving this specific feedback.
175
+ */
176
+ feedbackScore?: number;
177
+ /** @description This enumerated value indicates the current state of the feedback entry (for example, <code>ENTERED</code>). For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:FeedbackStateEnum'>eBay API documentation</a> */
178
+ feedbackState?: string;
179
+ /** @description This container provides the details of any follow-up comment left. <br><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>A buyer leaves followup comments, and a seller leaves reply comments.</span></p> */
180
+ followupComment?: components['schemas']['Comment'];
181
+ /** @description If returned as <code>true</code>, this boolean indicates that the feedback entry has one or more images attached. If <code>false</code>, there are no images attached. */
182
+ hasImages?: boolean;
183
+ /** @description This array contains the list of attached images. */
184
+ images?: components['schemas']['Image'][];
185
+ /** @description This container provides a summary of the line item associated with the feedback entry. <p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>Certain fields within this container are returned only when the request uses the <b>Authorization code grant flow</b> (user access token) and the <b>user_id</b> matches the authenticated user. These fields are not returned when accessing a different <b>user_id</b> or when using the <b>Client credentials grant flow</b> (application access token). See <a href="#h3-oauth-scope">OAuth scope</a> for for details on the flows and required permissions.</span></p> */
186
+ orderLineItemSummary?: components['schemas']['OrderLineItemSummary'];
187
+ /** @description This container details the attributes of the user who provided the feedback. */
188
+ providerUserDetail?: components['schemas']['ProviderUserDetail'];
189
+ /** @description If returned as <code>true</code>, this boolean indicates the feedback reply was given by the seller before the follow-up comment was given buy the buyer. */
190
+ repliedBeforeFollowup?: boolean;
191
+ /** @description This container provides the details of any reply to the feedback.<br><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>A buyer leaves followup comments, and a seller leaves reply comments.</span></p> */
192
+ replyComment?: components['schemas']['Comment'];
193
+ /** @description This array provides descriptions of AI-generated insights related to a feedback entry for the specified <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#uri.filter" >filter</a> topic. The feedback provided is considered relevant to the requested <b>topic</b>. For example, when using the request parameter filter of <code>topics:product-satisfaction</code>, the returned array might be: <p><pre>{<br> "coarseTopic" : "product-satisfaction",<br> "highlightedTexts" : [<br> "This machine is amazing",<br> "Very happy with this purchase"<br> ],<br> "sentiment" : "Positive"<br>}</pre></p><p>If no topics exist for that feedback, an empty array is returned.</p> */
194
+ topics?: components['schemas']['Topic'][];
195
+ };
196
+ /** @description This type specifies the amount of time elapsed associated with a feedback entry. */
197
+ FeedbackEnteredPeriod: {
198
+ /** @description The unit for the feedback entry period's <b>value</b>. Supported value: <code>DAY</code>. */
199
+ unit?: string;
200
+ /**
201
+ * Format: int32
202
+ * @description The value for the feedback entry period, specified in units of <b>unit</b>. Supported values: <code>7</code>, <code>30</code>, <code>90</code>, <code>180</code>, or <code>365</code>.
203
+ */
204
+ value?: number;
205
+ };
206
+ /** @description This type provides fields for the array of metrics associated with feedback aggregation. */
207
+ FeedbackMetrics: {
208
+ /** @description This enumerated value specifies the type of feedback aggregation. For example, <code>AVG</code> would indicate the feedback returned represents the average value of the feedback. See <b>metricValue</b> for the value of the returned feedback. For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:FeedbackAggregationTypeEnum'>eBay API documentation</a> */
209
+ metricName?: string;
210
+ /** @description The decimal value of the specified metric. For example, 55.8 would represent a value associated with the <b>metricName</b> (see <b>metricName</b> for interpretation and units). */
211
+ metricValue?: number;
212
+ };
213
+ /** @description This type provides for fields in ratings attached to feedback. */
214
+ FeedbackRating: {
215
+ /** @description This enumerated value indicates the type of rating (for example, <code>OVERALL_EXPERIENCE</code>, <code>DSR_ITEM_AS_DESCRIBED</code>). For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:FeedbackRatingTypeEnum'>eBay API documentation</a> */
216
+ ratingType?: string;
217
+ /** @description The value assigned to the rating, specified as a string representing a number from <code>1</code> to <code>5</code>, with <code>1</code> representing the lowest rating and <code>5</code> representing the highest rating. */
218
+ value?: string;
219
+ };
220
+ /** @description This type provides fields for available values for use in a particular rating, and whether the value is enabled. */
221
+ FeedbackRatingAcceptableValue: {
222
+ /** @description If <code>true</code>, this boolean indicates that this value is enabled and selectable. */
223
+ enabled?: boolean;
224
+ /** @description The value that can be selected for feedback. For most <b>ratingType</b> values, this is <code>1</code> through <code>5</code>, with <code>1</code> representing the lowest rating and <code>5</code> representing the highest rating. For <b>ratingType</b> of <code>OVERALL_EXPERIENCE</code>, this can be <code>POSITIVE</code>, <code>NEGATIVE</code>, and <code>NEUTRAL</code>. These are the same values as used with the <b>leaveFeedback</b> methods. */
225
+ value?: string;
226
+ /** @description This field provides information about the corresponding <b>value</b>. */
227
+ valueLabel?: string;
228
+ };
229
+ /** @description This type provides fields for an array containing a summary of feedback ratings. Each element provides detailed metrics and distributions for specific rating types. */
230
+ FeedbackRatingSummary: {
231
+ /** @description An array that includes metrics and distributions for each rating type. */
232
+ ratingSummaryByRatingType?: components['schemas']['RatingSummaryByRatingType'][];
233
+ /** @description This enumerated value indicates the type of rating being summarized. For example, <code>OVERALL_EXPERIENCE</code> indicates the rating applies to the overall transaction experience. For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:FeedbackRatingTypeEnum'>eBay API documentation</a> */
234
+ ratingType?: string;
235
+ };
236
+ /** @description This type defines fields for user feedback collection, including acceptable values, a default preselection value, and an early feedback message. It also provides fields to enable the template, and limits and options for freetext character, multi-value rating, and other similar features. */
237
+ FeedbackRatingTemplateType: {
238
+ /** @description This array contains a list of available values for use in a particular rating, and whether the value is enabled. Provided if <b>ratingValueType</b> is <code>RANGE</code> or <code>PREDEFINED</code>.<p>The following is an example of a predefined list:<pre>[<br> {<br> "value": "POSITIVE",<br> "valueLabel": "Positive",<br> "enabled": true<br> },<br> {<br> "value": "NEUTRAL",<br> "valueLabel": "Neutral",<br> "enabled": true<br> },<br> {<br> "value": "NEGATIVE",<br> "valueLabel": "Negative",<br> "enabled": true<br> }</br>]</pre>For other examples, see the <a href="/develop/guides-v2/communications/sell-communications-guide#using-rating-templates" target="_blank">Using rating templates</a>. */
239
+ acceptableValues?: components['schemas']['FeedbackRatingAcceptableValue'][];
240
+ /** @description The default value preselected for the rating, if set. */
241
+ defaultValue?: string;
242
+ /** @description For eligible sellers, a message may be shown requiring a wait period before you can leave neutral or negative feedback. */
243
+ earlyFeedbackMessage?: string;
244
+ /** @description If returned as <code>true</code>, this boolean indicates that the corresponding feedback rating template is enabled for the user to provide feedback for this line item. This value will generally be <code>true</code> when the user role is a buyer, but <code>false</code> when the user role is a seller because buyers do not have Detailed Seller Ratings (DSRs). */
245
+ enabled?: boolean;
246
+ /**
247
+ * Format: int32
248
+ * @description The maximum number of characters allowed to be used for a rating that uses free text. It is only applicable for a rating whose <b>ratingValueType</b> is <code>FREETEXT</code>. <p><b>Maximum: </b>500</p>
249
+ */
250
+ maximumCharactersAllowed?: number;
251
+ /** @description If returned as <code>true</code>, multiple values can be specified for the rating. */
252
+ multiValueRating?: boolean;
253
+ /** @description This enumerated value indicates the type of rating that is tracked for the seller. All of the metadata returned under each node for the <b>ratingTemplates</b> array will apply to this rating type. For example, the value <code>OVERALL_EXPERIENCE</code> indicates the rating is for the overall transaction experience. For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:FeedbackRatingTypeEnum'>eBay API documentation</a> */
254
+ ratingKey?: string;
255
+ /** @description This field provides more details about and/or provides guidance on the corresponding rating type. For example, the rating label of <b>Rate this transaction</b> describes the feedback for the user to enter for an <code>OVERALL_EXPERIENCE</code> <b>ratingKey</b>. */
256
+ ratingLabel?: string;
257
+ /** @description This enumerated value indicates the type of data used to provide the specific feedback rating.<br><p>If set to <code>PREDEFINED</code> or <code>RANGE</code>, is returned here, more information on the supported values will be returned under the <b>acceptableValues</b> array. If <code>FREETEXT</code> is returned here, the maximum number of characters supported can be seen in the <b>maximumCharactersAllowed</b> field.</p> For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:FeedbackRatingValueTypeEnum'>eBay API documentation</a> */
258
+ ratingValueType?: string;
259
+ /** @description If returned as <code>true</code>, this rating type is required when leaving feedback. */
260
+ required?: boolean;
261
+ };
262
+ /** @description This type provides field for an array listing the distribution values of the feedback ratings. */
263
+ FeedbackRatingValueDistribution: {
264
+ /**
265
+ * Format: int32
266
+ * @description An integer representing the number of occurrences for a specific feedback rating <b>value</b>. For example, for the <code>POSITIVE</code> <b>value</b>, a <code>3</code> returned as the <b>count</b> represents three positive ratings were returned.
267
+ */
268
+ count?: number;
269
+ /** @description A string indicating the specific feedback rating value. Supported values include: <code>POSITIVE</code>, <code>NEUTRAL</code>, <code>NEGATIVE</code>, <code>1</code>, <code>2</code>, <code>3</code>, <code>4</code>, and <code>5</code>. */
270
+ value?: string;
271
+ };
272
+ /** @description This type defines the fields for the <b>getFeedbackRatingSummary</b> response. */
273
+ GetFeedbackRatingSummaryResponse: {
274
+ /** @description An array containing a summary of feedback ratings. Each element provides detailed metrics and distributions for specific rating types. */
275
+ feedbackRatingSummary?: components['schemas']['FeedbackRatingSummary'][];
276
+ };
277
+ /** @description This type defines the fields for the <b>getFeedback</b> response. */
278
+ GetFeedbackResponse: {
279
+ /** @description This array contains a list of feedback entries that meet the specified criteria. */
280
+ feedbackEntries?: components['schemas']['FeedbackDetail'][];
281
+ /** @description This container provides pagination information for the returned feedback response (as filtered). */
282
+ pagination?: components['schemas']['Pagination'];
283
+ };
284
+ /** @description This type provides a field for image URLs. */
285
+ Image: {
286
+ /** @description This field provides the URL of an attached image and is included in the response whenever an image is attached. */
287
+ url?: string;
288
+ };
289
+ /** @description This type returns the number of line items awaiting feedback. */
290
+ ItemsAwaitingFeedbackCount: {
291
+ /**
292
+ * Format: int32
293
+ * @description The number of line items for which feedback is pending from the user in the buyer role.
294
+ */
295
+ asBuyer?: number;
296
+ /**
297
+ * Format: int32
298
+ * @description The number of line items for which feedback is pending from the user in the seller role.
299
+ */
300
+ asSeller?: number;
301
+ };
302
+ /** @description This type provides fields available to leave feedback in the <b>leaveFeedback</b> request. */
303
+ LeaveFeedbackRequest: {
304
+ /** @description Use this field to provide the feedback left by the user, describing their experience with the line item of the transaction. No HTML formatting or personal information (such as phone numbers) is permitted.<br><p><b>Maximum length:</b> 500 characters</p> */
305
+ commentText?: string;
306
+ /** @description Set this enumerated value to indicate the overall rating of the transaction: <code>POSITIVE</code>, <code>NEUTRAL</code>, or <code>NEGATIVE</code>.<br><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>Sellers can only provide positive feedback.</span></p> For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:FeedbackRatingValuesEnum'>eBay API documentation</a> */
307
+ commentType?: string;
308
+ /** @description Use this array to optionally list up to 5 images attached to the feedback. */
309
+ images?: components['schemas']['Image'][];
310
+ /** @description Use this field to provide the listing ID related to the transaction. */
311
+ listingId?: string;
312
+ /** @description Use this field to provide the unique identifier of the line item for this feedback. */
313
+ orderLineItemId?: string;
314
+ /** @description Use this array to list ratings for specific aspects of the seller's performance. */
315
+ sellerRatings?: components['schemas']['SellerRating'][];
316
+ /** @description Use this field to provide the unique identifier of the transaction for this feedback. */
317
+ transactionId?: string;
318
+ };
319
+ /** @description This type defines the fields for the <b>leaveFeedback</b> response for feedback that has been left. */
320
+ LeaveFeedbackResponse: {
321
+ /** @description The unique ID assigned to the submitted feedback. */
322
+ feedbackId?: string;
323
+ };
324
+ /** @description This type provides details about the price of the listing awaiting feedback. */
325
+ ListingPrice: {
326
+ /** @description This field provides the three-letter <a href="https://www.iso.org/iso-4217-currency-codes.html" target="_blank">ISO 4217</a> code that represents the currency of the amount in the value field. Both the <b>value</b> and <b>currency</b> fields are always returned when expressing prices. */
327
+ currency?: string;
328
+ /** @description This field contains the numerical value of the listing price in the currency specified in the <b>currency</b> field. Both the <b>value</b> and <b>currency</b> fields are always returned when expressing prices. */
329
+ value?: number;
330
+ };
331
+ /** @description This type describes line item attributes. */
332
+ OrderLineItemAttribute: {
333
+ /** @description This enumerated value indicates an attribute of the line item. The <b>value</b> field indicates if the attribute applies. For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:OrderLineItemAttributesEnum'>eBay API documentation</a> */
334
+ name?: string;
335
+ /** @description If returned as <code>true</code>, the line item attribute <b>name</b> applies; if returned as <code>false</code>, the attribute does not apply. */
336
+ value?: string;
337
+ };
338
+ /** @description This type provides fields for a summary of the line item related to feedback. */
339
+ OrderLineItemSummary: {
340
+ /** @description This field provides the unique identifier for the listing associated with the feedback entry. Conditionally returned based on the authorization flow and user context. See <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#response.feedbackEntries.orderLineItemSummary">orderLineItemSummary</a> for details on when this field is included. */
341
+ listingId?: string;
342
+ /** @description This container provides the sale price of the listing. Conditionally returned based on the authorization flow and user context. See <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#response.feedbackEntries.orderLineItemSummary">orderLineItemSummary</a> for details on when this field is included. */
343
+ listingPrice?: components['schemas']['ListingPrice'];
344
+ /** @description This field contains the title of the listing. Conditionally returned based on the authorization flow and user context. See <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#response.feedbackEntries.orderLineItemSummary">orderLineItemSummary</a> for details on when this field is included. */
345
+ listingTitle?: string;
346
+ /** @description This array describes order line attributes including names and values of a transaction. */
347
+ orderLineItemAttributes?: components['schemas']['OrderLineItemAttribute'][];
348
+ /** @description The unique identifier of the line item for this feedback. Conditionally returned based on the authorization flow and user context. See <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#response.feedbackEntries.orderLineItemSummary">orderLineItemSummary</a> for details on when this field is included. */
349
+ orderLineItemId?: string;
350
+ /** @description This container indicates if the time since the item was bought on ebay is less than, more than, or equal to 90 days */
351
+ transactionPeriod?: components['schemas']['TransactionPeriod'];
352
+ };
353
+ /** @description This type provides pagination information for the returned line items. */
354
+ Pagination: {
355
+ /**
356
+ * Format: int32
357
+ * @description This value indicates the number of feedback entries on the current response page.
358
+ */
359
+ count?: number;
360
+ /**
361
+ * Format: int32
362
+ * @description The value of the <b>limit</b> parameter submitted in the request. This is the maximum number of line items, as filtered, awaiting feedback to return per page from the result set. This field indicates the number of line items returned per page of data. <p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>If this is the last or only page of the result set, the page may contain fewer line items than the <b>limit</b> value. </span></p><p>If a <b>limit</b> parameter was not included in the request, this value will default to <code>25</code>, returning up to 25 line items on each page.</p><p><b>Default: </b>25</p>
363
+ */
364
+ limit?: number;
365
+ /** @description The relative URI for the next page of results starting with the resource name. This URI is returned if there is an additional page of results in the result set. */
366
+ next?: string;
367
+ /**
368
+ * Format: int32
369
+ * @description The value of the <b>offset</b> parameter submitted in the request. This field indicates how many results were skipped in the response. If an <b>offset</b> parameter was not included in the request, this value will default to <code>0</code>, returning the first page of results.<p><b>Default: </b>0</p>
370
+ */
371
+ offset?: number;
372
+ /** @description The relative URI for the previous page of results starting with the resource name. This URI is returned if there is a previous page of results in the result set.</p> */
373
+ prev?: string;
374
+ /**
375
+ * Format: int32
376
+ * @description The total number of line items available that match the filter criteria. <p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>If the total value exceeds the limit value, there are multiple pages of results.</span></p>
377
+ */
378
+ total?: number;
379
+ };
380
+ /** @description This type provides fields for the time period on which the feedback summary is calculated. */
381
+ Period: {
382
+ /** @description The unit of the period's <b>value</b>. Supported value: <code>DAY</code>. */
383
+ unit?: string;
384
+ /**
385
+ * Format: int32
386
+ * @description The value for the feedback period, specified in units of <b>unit</b>. Supported value: <code>90</code>.
387
+ */
388
+ value?: number;
389
+ };
390
+ /** @description This type provides the details of the user who provided the feedback of a <b>getFeedback</b> response. */
391
+ ProviderUserDetail: {
392
+ /**
393
+ * Format: int32
394
+ * @description This integer indicates the feedback score of the feedback provider at the time of providing this specific feedback.
395
+ */
396
+ feedbackScore?: number;
397
+ /** @description This enumerated value provides the visual star representation of the feedback score (for example, <code>YELLOW_STAR</code>). For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:FeedbackStarTypeEnum'>eBay API documentation</a> */
398
+ feedbackStar?: string;
399
+ /** @description This enumerated value indicates the user's role in the transaction (<code>BUYER</code> or <code>SELLER</code>). For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:UserRoleEnum'>eBay API documentation</a> */
400
+ role?: string;
401
+ /** @description This array lists additional attributes that relate to the user (such as verification status). */
402
+ userAttributes?: components['schemas']['ProviderUserDetailUserAttributes'][];
403
+ /** @description This field indicates the unique identifier of the user who gave the feedback.<br><br><span class="tablenote"><b>Note:</b> Select developers will not receive username data for U.S. users through this field. Instead, an immutable user ID will be returned in its place. For more information, please refer to <a href="/api-docs/static/data-handling-update.html" target="_blank">Data Handling Compliance</a>.</span> */
404
+ userId?: string;
405
+ };
406
+ /** @description This type defines the attributes of the user who provided the feedback of a <b>getFeedback</b> response. */
407
+ ProviderUserDetailUserAttributes: {
408
+ /** @description This enumerated value indicates an attribute of the user (for example, <code>USER_VERIFIED</code>). The <b>value</b> field indicates if the attribute applies. For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:UserAttributeEnum'>eBay API documentation</a> */
409
+ name?: string;
410
+ /** @description If returned as <code>true</code>, the user attribute <b>name</b> applies; if returned as <code>false</code>, the attribute does not apply. */
411
+ value?: string;
412
+ };
413
+ /** @description This type provides fields for an array that includes metrics and distributions for each rating type. */
414
+ RatingSummaryByRatingType: {
415
+ /** @description An array of metrics associated with feedback aggregation. */
416
+ feedbackMetrics?: components['schemas']['FeedbackMetrics'][];
417
+ /** @description An array listing the distribution values of the feedback ratings. */
418
+ feedbackRatingValueDistribution?: components['schemas']['FeedbackRatingValueDistribution'][];
419
+ /** @description The time period on which the feedback summary is calculated. */
420
+ period?: components['schemas']['Period'];
421
+ /** @description This enumerated value indicates the user's role in the feedback (<code>BUYER</code> or <code>SELLER</code>). For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:UserRoleEnum'>eBay API documentation</a> */
422
+ userRoleType?: string;
423
+ };
424
+ /** @description The type that defines the fields for the <b>respondToFeedback</b> request. */
425
+ RespondToFeedbackRequest: {
426
+ /** @description Use this field to provide the unique identifier for the feedback being responded to, used to specify the feedback entry associated with the feedback response. This value can be returned using the <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback" target="_blank">getFeedback</a> method (<a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#response.feedbackEntries.feedbackId" target="_blank">feedbackId</a> field). */
427
+ feedbackId?: string;
428
+ /** @description Use this field to provide the identifier of the user who provided the original feedback. This value can be returned using the <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback" target="_blank">getFeedback</a> method (<a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#response.feedbackEntries.providerUserDetail.userId" target="_blank">userId</a> field).<br><br><span class="tablenote"><b>Note:</b> Both usernames and public user IDs will be accepted in this field. For more information, please refer to <a href="/api-docs/static/data-handling-update.html" target="_blank">Data Handling Compliance</a>.</span> */
429
+ recipientUserId?: string;
430
+ /** @description Use this field to provide the text content of the response. This field is used to provide additional context or address the feedback given by the order partner. No HTML formatting or personal information (such as phone numbers) is permitted.<br><br><b>Maximum length:</b> 500 characters. */
431
+ responseText?: string;
432
+ /** @description Set this enumerated value to describe the type of response being submitted (for example, a <code>REPLY</code> or a <code>FOLLOW_UP</code>). For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/api:ResponseTypeEnum'>eBay API documentation</a> */
433
+ responseType?: string;
434
+ };
435
+ /** @description This type provides fields for specific aspects of the seller's performance. */
436
+ SellerRating: {
437
+ /** @description The enumerated value of the category being rated, such as delivery timeliness (<code>ON_TIME_DELIVERY</code>). For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/api:KeyEnum'>eBay API documentation</a> */
438
+ key?: string;
439
+ /** @description The value assigned for the selected category. Use a value of <code>1</code> through <code>5</code>, with the <code>1</code> being the lowest rating and <code>5</code> being the highest. */
440
+ value?: string;
441
+ };
442
+ /** @description This type provides subject-based fields derived from feedback. */
443
+ Topic: {
444
+ /** @description The main topic (or category) detected in the comment. See the available <b>topics</b> in <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#uri.filter">filter</a>. */
445
+ coarseTopic?: string;
446
+ /** @description <p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>Fine topics are not currently supported.</span></p>A more specific detail or subtopic related to the coarse topic. */
447
+ fineTopic?: string;
448
+ /** @description This array lists any text snippets, phrases, or examples, from the feedback that supports the detected topic. */
449
+ highlightedTexts?: string[];
450
+ /** @description This field indicates a classification of the feedback, whether the feedback is <code>Positive</code>, <code>Negative</code>, or <code>Neutral</code>. */
451
+ sentiment?: string;
452
+ };
453
+ /** @description This type specifies the amount of time elapsed and the threshold associated with a transaction. */
454
+ TransactionPeriod: {
455
+ /** @description This container indicates if the time since the item was bought on ebay is less than, more than, or equal to 90 days. */
456
+ period?: components['schemas']['Period'];
457
+ /** @description This enumerated value indicates whether a transaction <a href="/api-docs/commerce/feedback/resources/feedback/methods/getFeedback#response.feedbackEntries.orderLineItemSummary.transactionPeriod.period" >period</a> exceeds, falls short, or matches the threshold. You can use this field to trigger specific logic or actions based on whether a transaction period exceeds, falls short, or matches the threshold. For implementation help, refer to <a href='https://developer.ebay.com/api-docs/commerce/feedback/types/fdb:ThresholdTypeEnum'>eBay API documentation</a> */
458
+ thresholdType?: string;
459
+ };
460
+ };
461
+ responses: never;
462
+ parameters: never;
463
+ requestBodies: never;
464
+ headers: never;
465
+ pathItems: never;
466
+ }
467
+ export type $defs = Record<string, never>;
468
+ export interface operations {
469
+ getItemsAwaitingFeedback: {
470
+ parameters: {
471
+ query?: {
472
+ /** @description Use this parameter to limit the response based on the specified filter parameters. Supported filter parameters include:<br><p><ul><li><b>listingId</b>: Filter results by the specific listing ID</li><li><b>receiverName</b>: Filter results by the user's order partner name involved in the transaction</li><li><b>userRole</b>: Use this filter to only retrieve feedback due from the user in role as a seller or a buyer. If this filter is not used, all feedback due in both user roles is retrieved (<code>BUYER</code> or <code>SELLER</code>)</li></ul></p><p>Send the filter as a query parameter in a comma-separated <em>name</em>:<em>value</em> list. For example: <br><code>filter=listingId:123,receiverName:user,userRole:BUYER</code><p> */
473
+ filter?: string;
474
+ /** @description This parameter sets the maximum number of line items to return per page of data.<br><p>Use this parameter in conjunction with the <b>offset</b> parameter to control the pagination of the output. For example, with offset set to <code>20</code> and limit set to <code>10</code>, the call retrieves entries 21 through 30 from the result set.</p><p> Although this field is optional, if omitted the default value of <code>25</code> is used.</p><p><b>Default: </b>25</p><p><b>Minimum: </b>25</p><p><b>Maximum: </b>200</p> */
475
+ limit?: string;
476
+ /** @description Use this parameter to specify the number of items to skip in the result set. This is used with the <code>limit</code> field to control the pagination of the output. For example:<br><ul><li>If <b>offset</b> is <code>0</code> and <b>limit</b> is <code>10</code>, the method will retrieve items 1-10 from the list of line items returned</li><li>If <b>offset</b> is <code>10</code> and <b>limit</b> is <code>10</code>, the method will retrieve items 11-20 from the list of line items returned.</li></ul><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>This feature employs a zero-based list, where the first line item in the list has an offset of 0.</span></p><p>If this parameter is not set, its value defaults to <code>0</code> which returns the first page of records.</p><p><b>Default:</b> 0</p> */
477
+ offset?: string;
478
+ /** @description Use this parameter to configure the order of the returned listings. The time is based on when the buyer paid for the line item. Acceptable values:<br><ul><li><b>END_TIME_ASC:</b> Sorts listings by end time from oldest to newest</li><li><b>END_TIME_DESC:</b> Sorts listings by end time from newest to oldest (default)</li></ul><p>If this parameter is omitted, its value defaults to <b>END_TIME_DESC</b>.</p><p><b>Default: </b><code>END_TIME_DESC</code></p> */
479
+ sort?: string;
480
+ };
481
+ header?: never;
482
+ path?: never;
483
+ cookie?: never;
484
+ };
485
+ requestBody?: never;
486
+ responses: {
487
+ /** @description Success */
488
+ 200: {
489
+ headers: Record<string, unknown>;
490
+ content: {
491
+ 'application/json': components['schemas']['AwaitingFeedbackResponse'];
492
+ };
493
+ };
494
+ /** @description Bad Request */
495
+ 400: {
496
+ headers: Record<string, unknown>;
497
+ content?: never;
498
+ };
499
+ /** @description Not Authorized */
500
+ 401: {
501
+ headers: Record<string, unknown>;
502
+ content?: never;
503
+ };
504
+ /** @description Internal Server Error */
505
+ 500: {
506
+ headers: Record<string, unknown>;
507
+ content?: never;
508
+ };
509
+ };
510
+ };
511
+ getFeedback: {
512
+ parameters: {
513
+ query: {
514
+ /** @description Use this field to only return a specific feedback record by its feedback ID. <br><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>If this query parameter is used, no other filters will be applicable.</span></p> */
515
+ feedback_id?: string;
516
+ /** @description Use this field to specify the type of feedback records to return. Acceptable values: <br><ul><li><b>FEEDBACK_RECEIVED</b>: Retrieve feedback received by the specified user.</li><li><b>FEEDBACK_SENT</b>: Retrieve feedback sent by the specified user.</li></ul><p>If not specified, both feedback received and feedback left for the user shall be retrieved.</p><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>When using <b>FEEDBACK_SENT</b>, it is recommended to also filter <b>feedback_id</b> to target results accurately.</span></p> */
517
+ feedback_type: string;
518
+ /** @description Use this parameter to limit the response based on the specified filter parameters as follows: <br><ul><li><b>commentType</b>: Return only feedback with the set type of comments. Comment types available: <code>POSITIVE</code>, <code>NEUTRAL</code>, or <code>NEGATIVE</code> <p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>Sellers can only provide positive feedback.</span></p> </li><li><b>filterImage</b>: Return feedback dependent on if images are included. Filter values available:<ul><li><code>true</code>: Return only feedback with images</li><li><code>false</code>: Return feedback with or without images</li></ul></li><li><b>topics</b>: Use AI to generate items returned that are associated to the set topic. For example, if you set <code>topics:shipping</code>, only feedback comments about shipping are returned. Topics available: <code>shipping</code>, <code>service</code>, <code>packaging</code>, <code>description</code>, <code>seller-satisfaction</code>, <code>overall-satisfaction</code>, <code>refund</code>, <code>inventory</code>, <code>customer loyalty</code>, <code>seller-other</code>, <code>quality</code>, <code>price</code>, <code>condition</code>, <code>fit</code>, <code>appearance</code>, <code>dimensions</code>, <code>usage</code>, <code>product-satisfaction</code>, <code>product-other</code>, <code>extras</code><br><br>See <a href="/develop/guides-v2/communications/sell-communications-guide#retrieve-ai-filtered-items" target="_blank">Retrieve AI-filtered feedback</a> for an example.</li><li><b>period</b>: Filter results by the number of days to look back for feedback. If not set, lifetime results are returned. Supported values available: <code>7</code>, <code>30</code>, <code>90</code>, <code>180</code>, or <code>365</code></li><li><b>role</b>: Filter results by the role of the user providing feedback. Roles available: <code>BUYER </code>or <code>SELLER</code></li><li><b>showAutomatedFeedback</b>: Filter results to include automated feedback left by eBay entries. For sellers with less than a 10 feedback score, an automated feedback message on behalf of eBay is returned.<ul><li><code>true</code>: Return automated feedback including both user and eBay generated feedback</li><li><code>false</code>: Do not return eBay's automatic feedback for seller in response (default)</li></ul></li></ul>Send the filter as a query parameter in a comma-separated <em>name</em>:<em>value</em> list. For example: <br><br><code>filter=commentType:POSITIVE,filterImage:true,topics:fit,period:30,role:SELLER,showAutomatedFeedback:true</code></p> */
519
+ filter?: string;
520
+ /** @description Use this parameter to set the maximum number of items to return per page of data.<br><p>Use this parameter in conjunction with the <b>offset</b> parameter to control the pagination of the output. For example, with offset set to <code>20</code> and limit set to <code>10</code>, the call retrieves entries 21 through 30 from the result set.</p><p> Although this field is optional, if omitted the default value of <code>25</code> is used.</p><p><b>Default: </b>25</p><p><b>Minimum: </b>25</p><p><b>Maximum: </b>200</p> */
521
+ limit?: string;
522
+ /** @description Use this field to limit feedback entries to those associated with a specified listing. */
523
+ listing_id?: string;
524
+ /** @description Use this field to specify the number of line items to skip in the result set. This is used with the <code>limit</code> field to control the pagination of the output. For example:<br><ul><li>If <b>offset</b> is <code>0</code> and <b>limit</b> is <code>10</code>, the method will retrieve items 1-10 from the list of line items returned</li><li>If <b>offset</b> is <code>10</code> and <b>limit</b> is <code>10</code>, the method will retrieve items 11-20 from the list of line items returned.</li></ul><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>This feature employs a zero-based list, where the first line item in the list has an offset of 0.</span></p><p>If this parameter is not set, its value defaults to <code>0</code> which returns the first page of records.</p><p><b>Default:</b> 0</p> */
525
+ offset?: string;
526
+ /** @description Use this field to retrieve specific feedback entries related to an order line item ID. A maximum of two entries may be retrieved: feedback left by the buyer and feedback left by the seller. <br><p><span class="tablenote"><span style="color:#004680"><strong>Note: </strong>If this query parameter is set, no other filters will be applicable.</span></p> */
527
+ order_line_item_id?: string;
528
+ /** @description Use this parameter to configure the order of the returned items. The time is based on when the buyer paid for the line item. Acceptable values:<br><ul><li><b>RELEVANCE</b>: Sorts items by relevance (default). This sort takes into account any available factors such as a comment score, comment type (positive, negative, neutral), how long ago the comment was left, or the length of the comment</li><li><b>TIME</b>: Sorts items by end time from newest to oldest.</li></ul><p>If this parameter is omitted, its value defaults to <b>RELEVANCE</b>.</p><p><b>Default: </b><code>RELEVANCE</code></p> */
529
+ sort?: string;
530
+ /** @description Use this field to limit feedback entries to those associated with the specified transaction ID. */
531
+ transaction_id?: string;
532
+ /** @description Use this field to specify the unique identifier user ID (eBay username of the user) of the account for which feedback is being retrieved.<br><br><span class="tablenote"><b>Note:</b> Both usernames and public user IDs will be accepted in this field. For more information, please refer to <a href="/api-docs/static/data-handling-update.html" target="_blank">Data Handling Compliance</a>.</span> */
533
+ user_id: string;
534
+ };
535
+ header?: never;
536
+ path?: never;
537
+ cookie?: never;
538
+ };
539
+ requestBody?: never;
540
+ responses: {
541
+ /** @description Success */
542
+ 200: {
543
+ headers: Record<string, unknown>;
544
+ content: {
545
+ 'application/json': components['schemas']['GetFeedbackResponse'];
546
+ };
547
+ };
548
+ /** @description Bad Request */
549
+ 400: {
550
+ headers: Record<string, unknown>;
551
+ content?: never;
552
+ };
553
+ /** @description Not Authorized */
554
+ 401: {
555
+ headers: Record<string, unknown>;
556
+ content?: never;
557
+ };
558
+ /** @description Internal Server Error */
559
+ 500: {
560
+ headers: Record<string, unknown>;
561
+ content?: never;
562
+ };
563
+ };
564
+ };
565
+ leaveFeedback: {
566
+ parameters: {
567
+ query?: never;
568
+ header: {
569
+ /** @description This header indicates the format of the request body provided by the client. Its value should be set to <b>application/json</b>. <br><br> For more information, refer to <a href="/api-docs/static/rest-request-components.html#HTTP" target="_blank ">HTTP request headers</a>. */
570
+ 'Content-Type': string;
571
+ };
572
+ path?: never;
573
+ cookie?: never;
574
+ };
575
+ /** @description Request body for leaving feedback. Required fields: commentText (the text of the feedback comment), commentType (acceptable values - [POSITIVE, NEUTRAL, NEGATIVE]), listingId (the listingId of the item the feedback is being left for), transactionId (the transactionId for the order), orderLineItemId (Search by order line item ID. order line item id is a concatenation of listing ID and transaction ID, joined by `-`. Ex `listing_id-transaction_id`), sellerRatings (array of ratings with keys - [ON_TIME_DELIVERY, ITEM_AS_DESCRIBED, COMMUNICATION, SHIPPING_CHARGES, SHIPPING_TIME]), images (array of images with url field, can add upto 5 images) */
576
+ requestBody?: {
577
+ content: {
578
+ 'application/json': components['schemas']['LeaveFeedbackRequest'];
579
+ };
580
+ };
581
+ responses: {
582
+ /** @description Success */
583
+ 200: {
584
+ headers: Record<string, unknown>;
585
+ content: {
586
+ 'application/json': components['schemas']['LeaveFeedbackResponse'];
587
+ };
588
+ };
589
+ /** @description Bad Request */
590
+ 400: {
591
+ headers: Record<string, unknown>;
592
+ content?: never;
593
+ };
594
+ /** @description Not Authorized */
595
+ 401: {
596
+ headers: Record<string, unknown>;
597
+ content?: never;
598
+ };
599
+ /** @description Conflict */
600
+ 409: {
601
+ headers: Record<string, unknown>;
602
+ content?: never;
603
+ };
604
+ /** @description Internal Server Error */
605
+ 500: {
606
+ headers: Record<string, unknown>;
607
+ content?: never;
608
+ };
609
+ };
610
+ };
611
+ getFeedbackRatingSummary: {
612
+ parameters: {
613
+ query: {
614
+ /** @description Use this parameter to limit the response based on specified filter values:<br><ul><li><b>ratingType</b>: Specifies the type of rating being summarized and returned <b>(Required)</b>. Available values: <code>OVERALL_EXPERIENCE</code>, <code>OVERALL_EXPERIENCE_COMMENT</code>, <code>ON_TIME_DELIVERY</code>, <code>DSR_ITEM_AS_DESCRIBED</code>, <code>DSR_COMMUNICATION</code>, <code>DSR_SHIPPING_CHARGES</code>, <code>DSR_SHIPPING_TIME</code>, <code>ITEM_RATING</code><br>See <a href="/api-docs/commerce/feedback/types/fdb:FeedbackRatingTypeEnum" >FeedbackRatingTypeEnum</a> for descriptions of values. </li><li><b>excludeRepeatFeedback</b>: Set to <code>true</code> to exclude repeat feedback.</li><li><b>lookbackPeriodInDays</b>: Limit the response to a previous period of days. Available values: <code>7</code>, <code>30</code>, <code>90</code>, <code>180</code>, or <code>365</code></li></ul><p>You can send the filter as a query parameter, either with the required <b>ratingType</b> only, or combining the filter values with a comma-separated <em>name</em><b>:</b><em>value</em> list. For example:</p><p><code>filter=ratingType:OVERALL_EXPERIENCE,excludeRepeatFeedback:true,period:365</code></p> */
615
+ filter: string;
616
+ /** @description Use this parameter to specify the unique identifier (the eBay username associated with the account) for the eBay user whose feedback summary is being retrieved. */
617
+ user_id: string;
618
+ };
619
+ header?: never;
620
+ path?: never;
621
+ cookie?: never;
622
+ };
623
+ requestBody?: never;
624
+ responses: {
625
+ /** @description Success */
626
+ 200: {
627
+ headers: Record<string, unknown>;
628
+ content: {
629
+ 'application/json': components['schemas']['GetFeedbackRatingSummaryResponse'];
630
+ };
631
+ };
632
+ /** @description Bad Request */
633
+ 400: {
634
+ headers: Record<string, unknown>;
635
+ content?: never;
636
+ };
637
+ /** @description Not Authorized */
638
+ 401: {
639
+ headers: Record<string, unknown>;
640
+ content?: never;
641
+ };
642
+ /** @description Not Found */
643
+ 404: {
644
+ headers: Record<string, unknown>;
645
+ content?: never;
646
+ };
647
+ /** @description Internal Server Error */
648
+ 500: {
649
+ headers: Record<string, unknown>;
650
+ content?: never;
651
+ };
652
+ };
653
+ };
654
+ respondToFeedback: {
655
+ parameters: {
656
+ query?: never;
657
+ header: {
658
+ /** @description This header indicates the format of the request body provided by the client. Its value should be set to <b>application/json</b>. <br><br> For more information, refer to <a href="/api-docs/static/rest-request-components.html#HTTP" target="_blank ">HTTP request headers</a>. */
659
+ 'Content-Type': string;
660
+ };
661
+ path?: never;
662
+ cookie?: never;
663
+ };
664
+ /** @description This provides the request body for responding to feedback. */
665
+ requestBody?: {
666
+ content: {
667
+ 'application/json': components['schemas']['RespondToFeedbackRequest'];
668
+ };
669
+ };
670
+ responses: {
671
+ /** @description Success */
672
+ 200: {
673
+ headers: Record<string, unknown>;
674
+ content: {
675
+ 'application/json': Record<string, never>;
676
+ };
677
+ };
678
+ /** @description Bad Request */
679
+ 400: {
680
+ headers: Record<string, unknown>;
681
+ content?: never;
682
+ };
683
+ /** @description Not Authorized */
684
+ 401: {
685
+ headers: Record<string, unknown>;
686
+ content?: never;
687
+ };
688
+ /** @description Forbidden */
689
+ 403: {
690
+ headers: Record<string, unknown>;
691
+ content?: never;
692
+ };
693
+ /** @description Conflict */
694
+ 409: {
695
+ headers: Record<string, unknown>;
696
+ content?: never;
697
+ };
698
+ /** @description Internal Server Error */
699
+ 500: {
700
+ headers: Record<string, unknown>;
701
+ content?: never;
702
+ };
703
+ };
704
+ };
705
+ }