openapi: 3.0.0
info:
title: eBay Account Advertising_eligibility Payment_dispute API
description: The <b>Account API</b> gives sellers the ability to configure their eBay seller accounts, including the seller's policies (eBay business policies and seller-defined custom policies), opt in and out of eBay seller programs, configure sales tax tables, and get account information. <br><br>For details on the availability of the methods in this API, see <a href="/api-docs/sell/account/overview.html#requirements">Account API requirements and restrictions</a>.
contact:
name: eBay Inc,
license:
name: eBay API License Agreement
url: https://go.developer.ebay.com/api-license-agreement
version: v1.9.2
servers:
- url: https://api.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/account/v1
tags:
- name: Payment_dispute
paths:
/payment_dispute/{payment_dispute_id}:
servers:
- url: https://apiz.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/fulfillment/v1
get:
tags:
- Payment_dispute
summary: eBay Get Payment Dispute Details
description: This method retrieves detailed information on a specific payment dispute. The payment dispute identifier is passed in as path parameter at the end of the call URI.<br><br>Below is a summary of the information that is retrieved:<ul><li>Current status of payment dispute</li><li>Amount of the payment dispute</li><li>Reason the payment dispute was opened</li><li>Order and line items associated with the payment dispute</li><li>Seller response options if an action is currently required on the payment dispute</li><li>Details on the results of the payment dispute if it has been closed</li><li>Details on any evidence that was provided by the seller to fight the payment dispute</li></ul>
operationId: getPaymentDispute
parameters:
- name: payment_dispute_id
in: path
description: This parameter is used to specify the unique identifier of the payment dispute being retrieved.<br><br> Use the <a href="/api-docs/sell/fulfillment/resources/payment_dispute/methods/getPaymentDisputeSummaries" target="_blank ">getPaymentDisputeSummaries</a> method to retrieve payment dispute IDs.
required: true
schema:
type: string
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentDispute'
'400':
description: Bad Request
'404':
description: Invalid Payment Dispute Id
x-response-codes:
errors:
'33001':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid Payment Dispute Id
'500':
description: Internal Server Error
x-response-codes:
errors:
'33000':
domain: API_FULFILLMENT
category: APPLICATION
description: There was a problem with an eBay internal system or process. Contact eBay developer support for assistance.
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.payment.dispute
/payment_dispute/{payment_dispute_id}/fetch_evidence_content:
servers:
- url: https://apiz.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/fulfillment/v1
get:
tags:
- Payment_dispute
summary: eBay Get Payment Dispute Evidence File
description: 'This call retrieves a specific evidence file for a payment dispute. The following three identifying parameters are needed in the call URI:<ul><li><strong>payment_dispute_id</strong>: the identifier of the payment dispute. The identifier of each payment dispute is returned in the <strong>getPaymentDisputeSummaries</strong> response.</li><li><strong>evidence_id</strong>: the identifier of the evidential file set. The identifier of an evidential file set for a payment dispute is returned under the <strong>evidence</strong> array in the <strong>getPaymentDispute</strong> response.</li><li><strong>file_id</strong>: the identifier of an evidential file. This file must belong to the evidential file set identified through the <strong>evidence_id</strong> query parameter. The identifier of each evidential file is returned under the <strong>evidence.files</strong> array in the <strong>getPaymentDispute</strong> response.</li></ul><p>An actual binary file is returned if the call is successful. An error will occur if any of three identifiers are invalid.</p>'
operationId: fetchEvidenceContent
parameters:
- name: payment_dispute_id
in: path
description: This path parameter is used to specify the unique identifier of the payment dispute associated with the evidence file being retrieved.<br><br> Use the <a href="/api-docs/sell/fulfillment/resources/payment_dispute/methods/getPaymentDisputeSummaries" target="_blank ">getPaymentDisputeSummaries</a> method to retrieve payment dispute IDs.
required: true
schema:
type: string
- name: evidence_id
in: query
description: This query parameter is used to specify the unique identifier of the evidential file set.<br><br>The identifier of an evidential file set for a payment dispute is returned under the <strong>evidence</strong> array in the <a href="/api-docs/sell/fulfillment/resources/payment_dispute/methods/getPaymentDispute" target="_blank ">getPaymentDispute</a> response.
required: true
schema:
type: string
- name: file_id
in: query
description: This query parameter is used to specify the unique identifier of an evidential file. This file must belong to the evidential file set identified through the <strong>evidence_id</strong> query parameter.<br><br>The identifier of each evidential file is returned under the <strong>evidence.files</strong> array in the <a href="/api-docs/sell/fulfillment/resources/payment_dispute/methods/getPaymentDispute" target="_blank ">getPaymentDispute</a> response.
required: true
schema:
type: string
responses:
'200':
description: Success
content:
application/octet-stream:
schema:
type: array
items:
type: string
'400':
description: Bad Request
x-response-codes:
errors:
'33002':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid Evidence Id
'33003':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid Evidence File Id
'404':
description: Invalid Payment Dispute Id
x-response-codes:
errors:
'33001':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid Payment Dispute Id
'500':
description: Internal Server Error
x-response-codes:
errors:
'33000':
domain: API_FULFILLMENT
category: APPLICATION
description: There was a problem with an eBay internal system or process. Contact eBay developer support for assistance.
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.payment.dispute
/payment_dispute/{payment_dispute_id}/activity:
servers:
- url: https://apiz.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/fulfillment/v1
get:
tags:
- Payment_dispute
summary: eBay Get Payment Dispute Activity
description: This method retrieve a log of activity for a payment dispute. The identifier of the payment dispute is passed in as a path parameter. The output includes a timestamp for each action of the payment dispute, from creation to resolution, and all steps in between.
operationId: getActivities
parameters:
- name: payment_dispute_id
in: path
description: This parameter is used to specify the unique identifier of the payment dispute associated with the activity log being retrieved.<br><br> Use the <a href="/api-docs/sell/fulfillment/resources/payment_dispute/methods/getPaymentDisputeSummaries" target="_blank ">getPaymentDisputeSummaries</a> method to retrieve payment dispute IDs.
required: true
schema:
type: string
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentDisputeActivityHistory'
'400':
description: Bad Request
'404':
description: Invalid Payment Dispute Id
x-response-codes:
errors:
'33001':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid Payment Dispute Id
'500':
description: Internal Server Error
x-response-codes:
errors:
'33000':
domain: API_FULFILLMENT
category: APPLICATION
description: There was a problem with an eBay internal system or process. Contact eBay developer support for assistance.
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.payment.dispute
/payment_dispute_summary:
servers:
- url: https://apiz.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/fulfillment/v1
get:
tags:
- Payment_dispute
summary: eBay Search Payment Dispute by Filters
description: This method is used retrieve one or more payment disputes filed against the seller. These payment disputes can be open or recently closed. The following filter types are available in the request payload to control the payment disputes that are returned:<ul><li>Dispute filed against a specific order (<b>order_id</b> parameter is used)</li><li>Dispute(s) filed by a specific buyer (<b>buyer_username</b> parameter is used)</li><li>Dispute(s) filed within a specific date range (<b>open_date_from</b> and/or <b>open_date_to</b> parameters are used)</li><li>Disputes in a specific state (<b>payment_dispute_status</b> parameter is used)</li></ul>More than one of these filter types can be used together. See the request payload request fields for more information about how each filter is used.<br><br>If none of the filters are used, all open and recently closed payment disputes are returned.<br><br>Pagination is also available. See the <b>limit</b> and <b>offset</b> fields for more information on how pagination is used for this method.
operationId: getPaymentDisputeSummaries
parameters:
- name: order_id
in: query
description: This filter is used if the seller wishes to retrieve one or more payment disputes filed against a specific order. It is possible that there can be more than one dispute filed against an order if the order has multiple line items. If this filter is used, any other filters are ignored.<br><br>Use the <a href="/api-docs/sell/fulfillment/resources/order/methods/getOrders" target="_blank ">getOrders</a> method to retrieve order IDs. Order ID values are also shown in My eBay/Seller Hub.
required: false
schema:
type: string
- name: buyer_username
in: query
description: This filter is used if the seller wishes to retrieve one or more payment disputes opened by a specific buyer. The string that is passed in to this query parameter is the eBay user ID of the buyer.
required: false
schema:
type: string
- name: open_date_from
in: query
description: 'The <b>open_date_from</b> and/or <b>open_date_to</b> date filters are used if the seller wishes to retrieve payment disputes opened within a specific date range. A maximum date range that may be set with the <b>open_date_from</b> and/or <b>open_date_to</b> filters is 90 days. These date filters use the ISO-8601 24-hour date and time format, and time zone used is Universal Coordinated Time (UTC), also known as Greenwich Mean Time (GMT), or Zulu.<br><br>The <b>open_date_from</b> field sets the beginning date of the date range, and can be set as far back as 18 months from the present time. If a <b>open_date_from</b> field is used, but a <b>open_date_to</b> field is not used, the <b>open_date_to</b> value will default to 90 days after the date specified in the <b>open_date_from</b> field, or to the present time if less than 90 days in the past.<br><br>The ISO-8601 format looks like this: <em>yyyy-MM-ddThh:mm.ss.sssZ</em>. An example would be <code>2019-08-04T19:09:02.768Z</code>.'
required: false
schema:
type: string
- name: open_date_to
in: query
description: 'The <b>open_date_from</b> and/or <b>open_date_to</b> date filters are used if the seller wishes to retrieve payment disputes opened within a specific date range. A maximum date range that may be set with the <b>open_date_from</b> and/or <b>open_date_to</b> filters is 90 days. These date filters use the ISO-8601 24-hour date and time format, and the time zone used is Universal Coordinated Time (UTC), also known as Greenwich Mean Time (GMT), or Zulu.<br><br>The <b>open_date_to</b> field sets the ending date of the date range, and can be set up to 90 days from the date set in the <b>open_date_from</b> field. <br><br>The ISO-8601 format looks like this: <em>yyyy-MM-ddThh:mm.ss.sssZ</em>. An example would be <code>2019-08-04T19:09:02.768Z</code>.'
required: false
schema:
type: string
- name: payment_dispute_status
in: query
description: This filter is used if the seller wishes to only retrieve payment disputes in one or more specific states. To filter by more than one status value, a separate <b>payment_dispute_status</b> filter must be used for each value, as shown below:<br><br><i>https://apiz.ebay.com/sell/fulfillment/v1/payment_dispute_summary?payment_dispute_status=OPEN&payment_dispute_status=ACTION_NEEDED</i> <br><br>If no <b>payment_dispute_status</b> filter is used, payment disputes in all states are returned in the response.<br><br>See <a href="/api-docs/sell/fulfillment/types/api:DisputeStateEnum" target="_blank ">DisputeStatusEnum</a> type for supported values.
required: false
schema:
type: string
- name: limit
in: query
description: 'The value passed in this query parameter sets the maximum number of payment disputes to return per page of data. The value passed in this field should be an integer from 1 to 200. If this query parameter is not set, up to 200 records will be returned on each page of results.<br><br><b>Min</b>: 1<br><br> <b>Max</b>: 200<br><br><b>Default</b>: 200'
required: false
schema:
type: string
- name: offset
in: query
description: 'This field is used to specify the number of records to skip in the result set before returning the first payment dispute in the paginated response. A zero-based index is used, so if you set the <b>offset</b> value to <code>0</code> (default value), the first payment dispute in the result set appears at the top of the response. <br><br>Combine <b>offset</b> with the <b>limit</b> parameter to control the payment disputes returned in the response. For example, if you supply an <b>offset</b> value of <code>0</code> and a <b>limit</b> value of <code>10</code>, the response will contain the first 10 payment disputes from the result set that matches the input criteria. If you supply an <b>offset</b> value of <code>10</code> and a <b>limit</b> value of <code>20</code>, the response will contain payment disputes 11-30 from the result set that matches the input criteria.<br><br><b>Min</b>: 0 <br><br><b>Default</b>: 0'
required: false
schema:
type: string
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/DisputeSummaryResponse'
'400':
description: Bad Request
x-response-codes:
errors:
'33001':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid input request
'500':
description: Internal Server Error
x-response-codes:
errors:
'33000':
domain: API_FULFILLMENT
category: APPLICATION
description: There was a problem with an eBay internal system or process. Contact eBay developer support for assistance.
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.payment.dispute
/payment_dispute/{payment_dispute_id}/contest:
servers:
- url: https://apiz.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/fulfillment/v1
post:
tags:
- Payment_dispute
summary: eBay Contest Payment Dispute
description: This method is used if the seller wishes to contest a payment dispute initiated by the buyer. The unique identifier of the payment dispute is passed in as a path parameter, and unique identifiers for payment disputes can be retrieved with the <strong>getPaymentDisputeSummaries</strong> method.<br><br><span class="tablenote"><strong>Note:</strong> Before contesting a payment dispute, the seller must upload all supporting files using the <strong>addEvidence</strong> and <strong>updateEvidence</strong> methods. Once the seller has officially contested the dispute (using <strong>contestPaymentDispute</strong>), the <strong>addEvidence</strong> and <strong>updateEvidence</strong> methods can no longer be used. In the <strong>evidenceRequests</strong> array of the <strong>getPaymentDispute</strong> response, eBay prompts the seller with the type of supporting file(s) that will be needed to contest the payment dispute.</span><br><br>If a seller decides to contest a payment dispute, that seller should be prepared to provide supporting documents such as proof of delivery, proof of authentication, or other documents. The type of supporting documents that the seller will provide will depend on why the buyer filed the payment dispute.<br><br>The <strong>revision</strong> field in the request payload is required, and the <strong>returnAddress</strong> field should be supplied if the seller is expecting the buyer to return the item. See the Request Payload section for more information on these fields.
operationId: contestPaymentDispute
parameters:
- name: payment_dispute_id
in: path
description: This parameter is used to specify the unique identifier of the payment dispute being contested. <br><br> Use the <a href="/api-docs/sell/fulfillment/resources/payment_dispute/methods/getPaymentDisputeSummaries" target="_blank ">getPaymentDisputeSummaries</a> method to retrieve payment dispute IDs.
required: true
schema:
type: string
- name: Content-Type
in: header
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>.
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/ContestPaymentDisputeRequest'
required: false
responses:
'204':
description: Success
'400':
description: Bad Request
x-response-codes:
errors:
'33100':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid input request
'404':
description: Not Found
'409':
description: Conflict
x-response-codes:
errors:
'33011':
domain: API_FULFILLMENT
category: REQUEST
description: There was a change in payment dispute attributes. Please use get payment dispute api to get latest details.
'33101':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid payment dispute state
'33102':
domain: API_FULFILLMENT
category: REQUEST
description: No evidence available for contest
'500':
description: Internal Server Error
x-response-codes:
errors:
'33000':
domain: API_FULFILLMENT
category: APPLICATION
description: There was a problem with an eBay internal system or process. Contact eBay developer support for assistance.
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.payment.dispute
/payment_dispute/{payment_dispute_id}/accept:
servers:
- url: https://apiz.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/fulfillment/v1
post:
tags:
- Payment_dispute
summary: eBay Accept Payment Dispute
description: This method is used if the seller wishes to accept a payment dispute. The unique identifier of the payment dispute is passed in as a path parameter, and unique identifiers for payment disputes can be retrieved with the <strong>getPaymentDisputeSummaries</strong> method.<br><br>The <strong>revision</strong> field in the request payload is required, and the <strong>returnAddress</strong> field should be supplied if the seller is expecting the buyer to return the item. See the Request Payload section for more information on theste fields.
operationId: acceptPaymentDispute
parameters:
- name: payment_dispute_id
in: path
description: This parameter is used to specify the unique identifier of the payment dispute being accepted. <br><br> Use the <a href="/api-docs/sell/fulfillment/resources/payment_dispute/methods/getPaymentDisputeSummaries" target="_blank ">getPaymentDisputeSummaries</a> method to retrieve payment dispute IDs.
required: true
schema:
type: string
- name: Content-Type
in: header
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>.
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/AcceptPaymentDisputeRequest'
required: false
responses:
'204':
description: Success
'400':
description: Bad Request
x-response-codes:
errors:
'33100':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid input request
'404':
description: Not Found
'409':
description: Conflict
x-response-codes:
errors:
'33011':
domain: API_FULFILLMENT
category: REQUEST
description: There was a change in payment dispute attributes. Please use get payment dispute api to get latest details.
'500':
description: Internal Server Error
x-response-codes:
errors:
'33000':
domain: API_FULFILLMENT
category: APPLICATION
description: There was a problem with an eBay internal system or process. Contact eBay developer support for assistance.
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.payment.dispute
/payment_dispute/{payment_dispute_id}/upload_evidence_file:
servers:
- url: https://apiz.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/fulfillment/v1
post:
tags:
- Payment_dispute
summary: eBay Upload an Evidence File
description: This method is used to upload an evidence file for a contested payment dispute. The unique identifier of the payment dispute is passed in as a path parameter, and unique identifiers for payment disputes can be retrieved with the <strong>getPaymentDisputeSummaries</strong> method.<br><br><span class="tablenote"><strong>Note:</strong> The <strong>uploadEvidenceFile</strong> only uploads an encrypted, binary image file (using <strong>multipart/form-data</strong> HTTP request header), and does not have a JSON-based request payload.<br><br>Use 'file' as the name of the key that you use to upload the image file. The upload will not be successful if a different key name is used.<br><br>The three image formats supported at this time are <strong>.JPEG</strong>, <strong>.JPG</strong>, and <strong>.PNG</strong>.</span><br><br>After the file is successfully uploaded, the seller will need to grab the <strong>fileId</strong> value in the response payload to add this file to a new evidence set using the <strong>addEvidence</strong> method, or to add this file to an existing evidence set using the <strong>updateEvidence</strong> method.
operationId: uploadEvidenceFile
parameters:
- name: payment_dispute_id
in: path
description: This parameter is used to specify the unique identifier of the contested payment dispute for which the user intends to upload an evidence file.<br><br> Use the <a href="/api-docs/sell/fulfillment/resources/payment_dispute/methods/getPaymentDisputeSummaries" target="_blank ">getPaymentDisputeSummaries</a> method to retrieve payment dispute IDs.
required: true
schema:
type: string
- name: Content-Type
in: header
description: This header indicates the format of the request body provided by the client. Its value should be set to <b>multipart/form-data</b>. <br><br> For more information, refer to <a href="/api-docs/static/rest-request-components.html#HTTP" target="_blank ">HTTP request headers</a>.
required: true
schema:
type: string
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/FileEvidence'
'400':
description: Bad Request
x-response-codes:
errors:
'33005':
domain: API_FULFILLMENT
category: REQUEST
description: File type is invalid.
'33006':
domain: API_FULFILLMENT
category: REQUEST
description: File size should be 1.5 MB or less.
'33106':
domain: API_FULFILLMENT
category: REQUEST
description: The file name should not be empty and should not exceed 255 characters.
'33107':
domain: API_FULFILLMENT
category: REQUEST
description: Only one file can be uploaded per request.
'404':
description: Not Found
x-response-codes:
errors:
'33001':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid Payment Dispute Id
'409':
description: Conflict
x-response-codes:
errors:
'33004':
domain: API_FULFILLMENT
category: REQUEST
description: Upload file for evidence is not permitted for given payment dispute state.
'33105':
domain: API_FULFILLMENT
category: REQUEST
description: You reached the maximum number of files you can upload.
'500':
description: Internal Server Error
x-response-codes:
errors:
'33000':
domain: API_FULFILLMENT
category: APPLICATION
description: There was a problem with an eBay internal system or process. Contact eBay developer support for assistance.
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.payment.dispute
/payment_dispute/{payment_dispute_id}/add_evidence:
servers:
- url: https://apiz.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/fulfillment/v1
post:
tags:
- Payment_dispute
summary: eBay Add an Evidence File
description: This method is used by the seller to add one or more evidence files to address a payment dispute initiated by the buyer. The unique identifier of the payment dispute is passed in as a path parameter, and unique identifiers for payment disputes can be retrieved with the <strong>getPaymentDisputeSummaries</strong> method.<br><br><span class="tablenote"><strong>Note:</strong> All evidence files should be uploaded using <strong>addEvidence</strong> and <strong>updateEvidence</strong> before the seller decides to contest the payment dispute. Once the seller has officially contested the dispute (using <strong>contestPaymentDispute</strong> or through My eBay), the <strong>addEvidence</strong> and <strong>updateEvidence</strong> methods can no longer be used. In the <strong>evidenceRequests</strong> array of the <strong>getPaymentDispute</strong> response, eBay prompts the seller with the type of evidence file(s) that will be needed to contest the payment dispute.</span><br><br>The file(s) to add are identified through the <strong>files</strong> array in the request payload. Adding one or more new evidence files for a payment dispute triggers the creation of an evidence file, and the unique identifier for the new evidence file is automatically generated and returned in the <strong>evidenceId</strong> field of the <strong>addEvidence</strong> response payload upon a successful call.<br><br>The type of evidence being added should be specified in the <strong>evidenceType</strong> field. All files being added (if more than one) should correspond to this evidence type.<br><br>Upon a successful call, an <strong>evidenceId</strong> value is returned in the response. This indicates that a new evidence set has been created for the payment dispute, and this evidence set includes the evidence file(s) that were passed in to the <strong>fileId</strong> array. The <strong>evidenceId</strong> value will be needed if the seller wishes to add to the evidence set by using the <strong>updateEvidence</strong> method, or if they want to retrieve a specific evidence file within the evidence set by using the <strong>fetchEvidenceContent</strong> method.
operationId: addEvidence
parameters:
- name: payment_dispute_id
in: path
description: This parameter is used to specify the unique identifier of the contested payment dispute for which the seller wishes to add evidence files. <br><br> Use the <a href="/api-docs/sell/fulfillment/resources/payment_dispute/methods/getPaymentDisputeSummaries" target="_blank ">getPaymentDisputeSummaries</a> method to retrieve payment dispute IDs.
required: true
schema:
type: string
- name: Content-Type
in: header
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>.
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
# --- truncated at 32 KB (83 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/ebay/refs/heads/main/openapi/ebay-payment-dispute-api-openapi.yml