eBay Fulfillment API
The eBay Fulfillment API helps sellers manage post-purchase order fulfillment, shipments, tracking, and refunds.
OpenAPI Specification
openapi: 3.0.0
info:
title: eBay Fulfillment API
description: Use the Fulfillment API to complete the process of packaging, addressing, handling, and shipping each order on behalf of the seller, in accordance with the payment method and timing specified at checkout.
contact:
name: eBay Inc.
license:
name: eBay API License Agreement
url: https://go.developer.ebay.com/api-license-agreement
version: v1.20.4
servers:
- url: https://api.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/fulfillment/v1
- url: https://apiz.ebay.com{basePath}
description: Production
variables:
basePath:
default: /sell/fulfillment/v1
paths:
/order/{orderId}:
get:
tags:
- Order
description: 'Use this call to retrieve the contents of an order based on its unique identifier, <i>orderId</i>. This value was returned in the <b> getOrders</b> call''s <b>orders.orderId</b> field when you searched for orders by creation date, modification date, or fulfillment status. Include the optional <b>fieldGroups</b> query parameter set to <code>TAX_BREAKDOWN</code> to return a breakdown of the taxes and fees. <br><br> The returned <b>Order</b> object contains information you can use to create and process fulfillments, including: <ul> <li>Information about the buyer and seller</li> <li>Information about the order''s line items</li> <li> The plans for packaging, addressing and shipping the order</li> <li>The status of payment, packaging, addressing, and shipping the order</li> <li>A summary of monetary amounts specific to the order such as pricing, payments, and shipping costs</li> <li>A summary of applied taxes and fees, and optionally a breakdown of each </li></ul>'
operationId: getOrder
parameters:
- name: fieldGroups
in: query
description: This parameter lets you control what is returned in the response.<br><br><span class="tablenote"><b>Note:</b> The only presently supported value is <code>TAX_BREAKDOWN</code>. This field group adds addition fields to the response that return a breakdown of taxes and fees.</span>
required: false
schema:
type: string
- name: orderId
in: path
description: This path parameter is used to specify the unique identifier of the order being retrieved.<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.<br><br><span class="tablenote"><strong>Note:</strong> <b>getOrders</b> can return orders up to two years old. Do not provide the <b>orderId</b> for an order created more than two years in the past.</span>
required: true
schema:
type: string
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/Order'
'400':
description: Bad Request
x-response-codes:
errors:
'32100':
domain: API_FULFILLMENT
category: REQUEST
description: 'Invalid order ID: {orderId}'
'32800':
domain: API_FULFILLMENT
category: REQUEST
description: 'Invalid field group: {fieldGroup}'
'404':
description: Not Found
'500':
description: Internal Server Error
x-response-codes:
errors:
'30500':
domain: API_FULFILLMENT
category: APPLICATION
description: System error
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.fulfillment
- https://api.ebay.com/oauth/api_scope/sell.fulfillment.readonly
/order:
get:
tags:
- Order
description: 'Use this method to search for and retrieve one or more orders based on their creation date, last modification date, or fulfillment status using the <b>filter</b> parameter. You can alternatively specify a list of orders using the <b>orderIds</b> parameter. Include the optional <b>fieldGroups</b> query parameter set to <code>TAX_BREAKDOWN</code> to return a breakdown of the taxes and fees. By default, when no filters are used this call returns all orders created within the last 90 days. <br><br> The returned <b>Order</b> objects contain information you can use to create and process fulfillments, including: <ul> <li>Information about the buyer and seller</li> <li>Information about the order''s line items</li> <li>The plans for packaging, addressing and shipping the order</li> <li>The status of payment, packaging, addressing, and shipping the order</li> <li>A summary of monetary amounts specific to the order such as pricing, payments, and shipping costs</li> <li>A summary of applied taxes and fees, and optionally a breakdown of each </li></ul> <br><br> <span class="tablenote"><strong>Important:</strong> In this call, the <b>cancelStatus.cancelRequests</b> array is returned but is always empty. Use the <b>getOrder</b> call instead, which returns this array fully populated with information about any cancellation requests.</span>'
operationId: getOrders
parameters:
- name: fieldGroups
in: query
description: This parameter lets you control what is returned in the response.<br><br><span class="tablenote"><b>Note:</b> The only presently supported value is <code>TAX_BREAKDOWN</code>. This field group adds addition fields to the response that return a breakdown of taxes and fees.</span>
required: false
schema:
type: string
- name: filter
in: query
description: 'One or more comma-separated criteria for narrowing down the collection of orders returned by this call. These criteria correspond to specific fields in the response payload. Multiple filter criteria combine to further restrict the results. <br><br><span class="tablenote"><strong>Note:</strong> <b>getOrders</b> can return orders up to two years old. Do not set the <code>creationdate</code> filter to a date beyond two years in the past.</span><br><span class="tablenote"><strong>Note:</strong> If the <b>orderIds</b> parameter is included in the request, the <b>filter</b> parameter will be ignored.</span><br>The available criteria are as follows: <dl> <dt><code><b>creationdate</b></code></dt> <dd>The time period during which qualifying orders were created (the <b>orders.creationDate</b> field). In the URI, this is expressed as a starting timestamp, with or without an ending timestamp (in brackets). The timestamps are in ISO 8601 format, which uses the 24-hour Universal Coordinated Time (UTC) clock.For example: <ul> <li><code>creationdate:[2016-02-21T08:25:43.511Z..]</code> identifies orders created on or after the given timestamp.</li> <li><code>creationdate:[2016-02-21T08:25:43.511Z..2016-04-21T08:25:43.511Z]</code> identifies orders created between the given timestamps, inclusive.</li> </ul> </dd> <dt><code><b>lastmodifieddate</b></code></dt> <dd>The time period during which qualifying orders were last modified (the <b>orders.modifiedDate</b> field). In the URI, this is expressed as a starting timestamp, with or without an ending timestamp (in brackets). The timestamps are in ISO 8601 format, which uses the 24-hour Universal Coordinated Time (UTC) clock.For example: <ul> <li><code>lastmodifieddate:[2016-05-15T08:25:43.511Z..]</code> identifies orders modified on or after the given timestamp.</li> <li><code>lastmodifieddate:[2016-05-15T08:25:43.511Z..2016-05-31T08:25:43.511Z]</code> identifies orders modified between the given timestamps, inclusive.</li> </ul> <span class="tablenote"><strong>Note:</strong> If <b>creationdate</b> and <b>lastmodifieddate</b> are both included, only <b>creationdate</b> is used.</span> <br><br></dd> <dt><code><b>orderfulfillmentstatus</b></code></dt> <dd>The degree to which qualifying orders have been shipped (the <b>orders.orderFulfillmentStatus</b> field). In the URI, this is expressed as one of the following value combinations: <ul> <li><code>orderfulfillmentstatus:{NOT_STARTED|IN_PROGRESS}</code> specifies orders for which no shipping fulfillments have been started, plus orders for which at least one shipping fulfillment has been started but not completed.</li> <li><code>orderfulfillmentstatus:{FULFILLED|IN_PROGRESS}</code> specifies orders for which all shipping fulfillments have been completed, plus orders for which at least one shipping fulfillment has been started but not completed.</li> </ul> <span class="tablenote"><strong>Note:</strong> The values <code>NOT_STARTED</code>, <code>IN_PROGRESS</code>, and <code>FULFILLED</code> can be used in various combinations, but only the combinations shown here are currently supported.</span> </dd> </dl> Here is an example of a <b>getOrders</b> call using all of these filters: <br><br> <code>GET https://api.ebay.com/sell/v1/order?<br>filter=<b>creationdate</b>:%5B2016-03-21T08:25:43.511Z..2016-04-21T08:25:43.511Z%5D,<br><b>lastmodifieddate</b>:%5B2016-05-15T08:25:43.511Z..%5D,<br><b>orderfulfillmentstatus</b>:%7BNOT_STARTED%7CIN_PROGRESS%7D</code> <br><br> <span class="tablenote"><strong>Note:</strong> This call requires that certain special characters in the URI query string be percent-encoded: <br> <code>[</code> = <code>%5B</code> <code>]</code> = <code>%5D</code> <code>{</code> = <code>%7B</code> <code>|</code> = <code>%7C</code> <code>}</code> = <code>%7D</code> <br> This query filter example uses these codes.</span> For implementation help, refer to eBay
API documentation at https://developer.ebay.com/api-docs/sell/fulfillment/types/api:FilterField'
required: false
schema:
type: string
- name: limit
in: query
description: The number of orders to return per page of the result set. Use this parameter in conjunction with the <b>offset</b> parameter to control the pagination of the output. <br><br>For example, if <b>offset</b> is set to <code>10</code> and <b>limit</b> is set to <code>10</code>, the call retrieves orders 11 thru 20 from the result set. <br><br> If a limit is not set, the <b>limit</b> defaults to 50 and returns up to 50 orders. If a requested limit is more than 200, the call fails and returns an error.<br ><br> <span class="tablenote"><strong>Note:</strong> This feature employs a zero-based list, where the first item in the list has an offset of <code>0</code>. If the <b>orderIds</b> parameter is included in the request, this parameter will be ignored.</span> <br><br> <b>Maximum:</b> <code>200</code> <br> <b>Default:</b> <code>50</code>
required: false
schema:
type: string
- name: offset
in: query
description: Specifies the number of orders to skip in the result set before returning the first order in the paginated response. <p>Combine <b>offset</b> with the <b>limit</b> query parameter to control the items returned in the response. For example, if you supply an <b>offset</b> of <code>0</code> and a <b>limit</b> of <code>10</code>, the first page of the response contains the first 10 items from the complete list of items retrieved by the call. If <b>offset</b> is <code>10</code> and <b>limit</b> is <code>20</code>, the first page of the response contains items 11-30 from the complete result set.</p> <p><b>Default:</b> 0</p>
required: false
schema:
type: string
- name: orderIds
in: query
description: A comma-separated list of the unique identifiers of the orders to retrieve (maximum 50). If one or more order ID values are specified through the <b>orderIds</b> query parameter, all other query parameters will be ignored.<br><br><span class="tablenote"><strong>Note:</strong> <b>getOrders</b> can return orders up to two years old. Do not provide the <b>orderId</b> for an order created more than two years in the past.</span>
required: false
schema:
type: string
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/OrderSearchPagedCollection'
'400':
description: Bad Request
x-response-codes:
errors:
'30700':
domain: API_FULFILLMENT
category: REQUEST
description: 'Invalid filter name: {fieldname}'
'30800':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid filter value {fieldvalue} for filter {fieldname}
'30810':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid date format
'30820':
domain: API_FULFILLMENT
category: REQUEST
description: Start date is missing
'30830':
domain: API_FULFILLMENT
category: REQUEST
description: Time range between start date and end date must be within '{allowedTime}' years.
'30840':
domain: API_FULFILLMENT
category: REQUEST
description: Start date should be before end date
'30850':
domain: API_FULFILLMENT
category: REQUEST
description: Start and end dates can't be in the future
'30900':
domain: API_FULFILLMENT
category: REQUEST
description: Exceeded maximum number of order IDs (the current limit is <code>50</code>)
'31000':
domain: API_FULFILLMENT
category: REQUEST
description: 'Invalid offset: {offsetvalue}'
'31100':
domain: API_FULFILLMENT
category: REQUEST
description: 'Invalid limit: {limitvalue}'
'32800':
domain: API_FULFILLMENT
category: REQUEST
description: 'Invalid field group: {fieldGroup}'
'500':
description: Internal Server Error
x-response-codes:
errors:
'30500':
domain: API_FULFILLMENT
category: APPLICATION
description: System error
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.fulfillment
- https://api.ebay.com/oauth/api_scope/sell.fulfillment.readonly
/order/{order_id}/issue_refund:
post:
tags:
- Order
summary: eBay Issue Refund
description: '<div class="msgbox_important"><p class="msgbox_importantInDiv" data-mc-autonum="<b><span style="color: #dd1e31;" class="mcFormatColor">Important! </span></b>"><span class="autonumber"><span><b><span style="color: #dd1e31;" class="mcFormatColor">Important!</span></b></span></span> Due to EU & UK Payments regulatory requirements, an additional security verification via Digital Signatures is required for certain API calls that are made on behalf of EU/UK sellers, including <b>issueRefund</b>. Please refer to <a href="/develop/guides/digital-signatures-for-apis " target="_blank">Digital Signatures for APIs</a> to learn more on the impacted APIs and the process to create signatures to be included in the HTTP payload.</p></div><br> This method allows a seller to issue a full or partial refund to a buyer for an order. Full or partial refunds can be issued at the order level or line item level.<br><br>The refunds issued through this method are processed asynchronously, so the refund will not show as ''Refunded'' right away. A seller will have to make a subsequent <a href="/api-docs/sell/fulfillment/resources/order/methods/getOrder" target="_blank">getOrder</a> call to check the status of the refund. The status of an order refund can be found in the <a href="/api-docs/sell/fulfillment/resources/order/methods/getOrder#response.paymentSummary.refunds.refundStatus" target="_blank">paymentSummary.refunds.refundStatus</a> field of the <a href="/api-docs/sell/fulfillment/resources/order/methods/getOrder" target="_blank">getOrder</a> response.'
operationId: issueRefund
parameters:
- name: order_id
in: path
description: This path parameter is used to specify the unique identifier of the order associated with a refund.<br><br>Use the <a href="/api-docs/sell/fulfillment/resources/order/methods/getOrders" target="_blank ">getOrders</a> method to retrieve order 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/IssueRefundRequest'
required: false
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/Refund'
'400':
description: Bad Request
x-response-codes:
errors:
'34901':
domain: API_FULFILLMENT
category: REQUEST
description: Order id can't be null or empty.
'34902':
domain: API_FULFILLMENT
category: REQUEST
description: Request can't be empty.
'34903':
domain: API_FULFILLMENT
category: REQUEST
description: The refund reason must be specified.
'34905':
domain: API_FULFILLMENT
category: REQUEST
description: Either orderLevelRefundAmount or refundItems must be specified.
'34906':
domain: API_FULFILLMENT
category: REQUEST
description: The amount value must be specified.
'34907':
domain: API_FULFILLMENT
category: REQUEST
description: The amount value must be positive and within two decimals.
'34908':
domain: API_FULFILLMENT
category: REQUEST
description: The amount currency must be specified.
'34909':
domain: API_FULFILLMENT
category: REQUEST
description: The amount currency isn't correct.
'34910':
domain: API_FULFILLMENT
category: REQUEST
description: Either legacyReference or lineItemId must be specified for item level refund.
'34911':
domain: API_FULFILLMENT
category: REQUEST
description: Legacy item id must be specified for item level refund if you use legacyReference.
'34912':
domain: API_FULFILLMENT
category: REQUEST
description: Legacy transaction id must be specified for item level refund if you use legacyReference.
'34914':
domain: API_FULFILLMENT
category: REQUEST
description: Can't find the item in the order.
'34915':
domain: API_FULFILLMENT
category: REQUEST
description: The refund amount exceeds order amount.
'34916':
domain: API_FULFILLMENT
category: BUSINESS
description: A post-transaction case exists on this order, seller refund can't be triggered.
'34917':
domain: API_FULFILLMENT
category: BUSINESS
description: This order was already refunded.
'34920':
domain: API_FULFILLMENT
category: BUSINESS
description: It's too late to issue a refund for this order.
'34921':
domain: API_FULFILLMENT
category: REQUEST
description: The comment exceeds the length limit, please make sure it doesn't exceed 1000 characters.
'34922':
domain: API_FULFILLMENT
category: REQUEST
description: Refund can't be issued while previous refund is processing.
'34923':
domain: API_FULFILLMENT
category: REQUEST
description: Refund cannot be issued for this type of order.
'403':
description: Access Forbidden
'404':
description: Resource Not found
x-response-codes:
errors:
'34913':
domain: API_FULFILLMENT
category: REQUEST
description: Can not find the order.
'409':
description: Conflict
x-response-codes:
errors:
'34918':
domain: API_FULFILLMENT
category: BUSINESS
description: This is not an eBay managed payments order.
'34919':
domain: API_FULFILLMENT
category: REQUEST
description: Unauthorized access.
'34924':
domain: API_FULFILLMENT
category: BUSINESS
description: The item refund amount exceeds the item remaining amount.
'34925':
domain: API_FULFILLMENT
category: BUSINESS
description: The refund operation could not be completed with any of the payment methods saved to the seller's account.
'34926':
domain: API_FULFILLMENT
category: BUSINESS
description: A suitable payment method could not be found for the refund operation. Please resolve in Seller Hub.
'34927':
domain: API_FULFILLMENT
category: BUSINESS
description: The selected payment method for the refund operation was invalid or declined.
'34928':
domain: API_FULFILLMENT
category: BUSINESS
description: Your refund did not go through because we could not verify your payment option. Please change your payment option and try again.
'34929':
domain: API_FULFILLMENT
category: REQUEST
description: You cannot refund this order yet since the buyer payment has not been processed. Please try again later.
'34930':
domain: API_FULFILLMENT
category: REQUEST
description: Default payment method limit exceeded. Please use a different payment option or try again later.
'500':
description: Internal Server Error
x-response-codes:
errors:
'34900':
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.finances
/order/{orderId}/shipping_fulfillment:
get:
tags:
- Shipping_fulfillment
description: Use this call to retrieve the contents of all fulfillments currently defined for a specified order based on the order's unique identifier, <b>orderId</b>. This value is returned in the <b>getOrders</b> call's <b>members.orderId</b> field when you search for orders by creation date or shipment status.
operationId: getShippingFulfillments
parameters:
- name: orderId
in: path
description: This path parameter is used to specify the unique identifier of the order associated with the shipping fulfillments being retrieved.<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: true
schema:
type: string
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/ShippingFulfillmentPagedCollection'
'400':
description: Bad Request
x-response-codes:
errors:
'32100':
domain: API_FULFILLMENT
category: REQUEST
description: 'Invalid order ID: {orderId}'
'500':
description: Internal Server Error
x-response-codes:
errors:
'30500':
domain: API_FULFILLMENT
category: APPLICATION
description: System error
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.fulfillment
- https://api.ebay.com/oauth/api_scope/sell.fulfillment.readonly
post:
tags:
- Shipping_fulfillment
description: When you group an order's line items into one or more packages, each package requires a corresponding plan for handling, addressing, and shipping; this is a <i>shipping fulfillment</i>. For each package, execute this call once to generate a shipping fulfillment associated with that package. <br><br> <span class="tablenote"><strong>Note:</strong> A single line item in an order can consist of multiple units of a purchased item, and one unit can consist of multiple parts or components. Although these components might be provided by the manufacturer in separate packaging, the seller must include all components of a given line item in the same package.</span> <br><br>Before using this call for a given package, you must determine which line items are in the package. If the package has been shipped, you should provide the date of shipment in the request. If not provided, it will default to the current date and time.
operationId: createShippingFulfillment
parameters:
- name: orderId
in: path
description: This path parameter is used to specify the unique identifier of the order associated with the shipping fulfillment being created.<br><br> Use the <a href="/api-docs/sell/fulfillment/resources/order/methods/getOrders" target="_blank ">getOrders</a> method to retrieve order 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:
description: fulfillment payload
content:
application/json:
schema:
description: fulfillment payload
$ref: '#/components/schemas/ShippingFulfillmentDetails'
required: true
responses:
'201':
description: 'Created. The call also returns the following location response header: <br><br><code>{ENV}/sell/fulfillment/v1/order/{ORDERID}/shipping_fulfillment/{FULFILLMENTID}</code> <br><br>The <code>ENV</code> string is the HTTPS path to the same eBay supported environment in which this call was issued. The <code>ORDERID</code> parameter is the unique identifier of the order addressed by this call; for example, <code>01-03955-36441</code>. The <code>FULFILLMENTID</code> parameter identifies the newly created fulfillment; for example, <code>9405509699937003457459</code>. Use this Get Fulfillment URI to retrieve the contents of the new fulfillment.'
headers:
Location:
schema:
type: string
description: The <b>location</b> response header contains the <a href="/api-docs/sell/fulfillment/resources/order/shipping_fulfillment/methods/getShippingFulfillment" target="_blank ">getShippingFulfillment</a> URI to retrieve the contents of the newly created shipping fulfillment. The URL includes the eBay-assigned <code>fulfillmentId</code>, which you can use to reference the shipping fulfillment.
content:
application/json:
schema:
type: object
'400':
description: Bad Request
x-response-codes:
errors:
'32100':
domain: API_FULFILLMENT
category: REQUEST
description: 'Invalid Order Id: {orderId}'
'32200':
domain: API_FULFILLMENT
category: REQUEST
description: 'Invalid line item id: {lineItemId}'
'32210':
domain: API_FULFILLMENT
category: REQUEST
description: Duplicate line item in the request
'32300':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid shipment tracking number or carrier
'32400':
domain: API_FULFILLMENT
category: REQUEST
description: Requested user is suspended
'32500':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid shipped date
'32600':
domain: API_FULFILLMENT
category: REQUEST
description: Invalid input data
'34100':
domain: API_FULFILLMENT
category: REQUEST
description: Maximum tracking number for order is exceeded
'34200':
domain: API_FULFILLMENT
category: REQUEST
description: Line Items contain Global Shipping Program and non-Global Shipping Program orders
'34300':
domain: API_FULFILLMENT
category: REQUEST
description: Mark As Shipped for multiple Global Shipping Program line items is not supported
'34500':
domain: API_FULFILLMENT
category: REQUEST
description: Please use PUT operation for updating shipping fulfillment
'409':
description: Conflict
'500':
description: Internal Server Error
x-response-codes:
errors:
'30500':
domain: API_FULFILLMENT
category: APPLICATION
description: System error
security:
- api_auth:
- https://api.ebay.com/oauth/api_scope/sell.fulfillment
/order/{orderId}/shipping_fulfillment/{fulfillmentId}:
get:
tags:
- Shipping_fulfillment
description: Use this call to retrieve the contents of a fulfillment based on its unique identifier, <b>fulfillmentId</b> (combined with the associated order's <b>orderId</b>). The <b>fulfillmentId</b> value was originally generated by the <b>createShippingFulfillment</b> call, and is returned by the <b>getShippingFulfillments</b> call in the <b>members.fulfillmentId</b> field.
operationId: getShippingFulfillment
parameters:
- name: fulfillmentId
in: path
description: This path parameter is used to specify the unique identifier of the shipping fulfillment being retrieved.<br><br>Use the <a href="/api-docs/sell/fulfillment/resources/order/shipping_fulfillment/methods/getShippingFulfillments" target="_blank ">getShipping
# --- truncated at 32 KB (221 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/ebay/refs/heads/main/openapi/ebay-fulfillment-openapi-original.yml