Currently sellers can upload feeds programmatically using REST web service (POST) to the FileExchange (BulkSell) url. We’ve migrated the Programmatic File Exchange endpoints into the Feed API. Once sellers switch over, performance and reliability will be improved, but there are manual changes required from our sellers and integration partners. This document provides instructions required for sellers to transition from the programmatic File Exchange integration to the Sell Feed API.

Important! The feed files used are the same, but the endpoints used for the programmatic File Exchange will be deprecated by June 2021.

Feed API

The Feed API lets sellers upload and download feed files and reports. Both upload and download feed files are processed asynchronously by eBay. The status of all upload and download tasks are tracked with a unique 'task ID'. Each report can be customized with date ranges and other filter criteria. General Sell Feed API Tasks (Flows) provide basic use of the Sell Feed API.

Differences between File Exchange and Feed API

The following list describes the general differences between using programmatic File Exchange and the Feed API. Information specific to each flow (upload and download) and provided in a different section of this document.

  • Sell Feed API requires an eBay OAuth token. The authorization code grant flow contains more information on working with the eBay OAuth token. The userToken used for the Feed API will be active for two hours while the existing token stays active for a year.
  • Currently, the seller programmatically uploads the file and bulkApi framework internally identifies the feedType through fileContents. In Feed API, sellers need to provide the feedType explicitly (for example, FX_LISTING or FX_FULFILLMENT).
  • The taskId generated in the Feed API is alphanumeric format (task-xx-xxxxxx) while it is numeric in the programmatic file exchange (existing system).

REST Verbs

The general guideline for when to use which verb is as follows:

  • A GET is used for requesting information from the web service.
  • A POST is used to put data to a web server. There is no specification as to where the web service should put the data.