This section provides links to the associated LMS call and the Feed API call for specific upload flows. See the What's Changed section following each table for additional information about migrating to the Feed API from LMS.

Create Upload Job

LMS

Feed API

CreateUploadJob

createTask

What's Changed:

  1. LMS works through SOAP API while Feed API takes in REST API.
    In the Feed API, the OAuth Token (AuthorizationToken) follows the term Bearer (Bearer + UserToken).
  2. TaskId in Feed API response is equivalent to jobId in LMS API processing.
  3. SchemaVersion and SiteID values are provided through input Headers in Feed API. In LMS, these values were provided inside the inputFile. The value of <version> in the input files should match the SchemaVersion header value.
  4. In the Feed API, the MarketPlaceId value is provided through X-EBAY-C-MARKETPLACE-ID header. In LMS, this value was provided by SiteID.
  5. With the Feed API, sellers can create multiple jobs at a time. They are queued and only one is processed at any time. In LMS, sellers were blocked to create jobs as well.
  6. In the Feed API, the possible values for schemaVersion, X-EBAY-C-MARKETPLACE-ID, and feedType are described in Version Details / Schema Version and Supported MarketPlaceIds.
  7. The taskId is used in the uploadfile call.

Upload Input File

LMS

Feed API

uploadFile

uploadFile

What's Changed:

  1. In LMS, the seller can either attach file as input or place its base64 encoded value in the request body. File input  can only be a zipped xml formatted file for uploadJob.

  2. For the Feeds API, the input can be an xml file and zipped or in regular format (both formats are allowed). The input can be a file or InputStream type (Inputstream can be used while uploading file programmatically).

  3. Use the Feed API getInputFile method to download the file previously uploaded usinguploadFile.

Start Upload Job

LMS

Feed API

startUploadJob

Not applicable for the Feed API

  1. In the Feed API, the task is automatically moved to Queued Status, waiting for processing and will be picked up by the system.
  2. The QUEUED status in the Feed API corresponds to the SCHEDULED state in LMS.

AbortJob

LMS

Feed API

AbortJob

Not supported