eBay Bulk Data Exchange API
|
You can find links to the Bulk Data Exchange API documentation in the top navigation bar. Information about the schema location is in the Schema Location section of the "Making an API Call" topic.
Are you new to the Large Merchant Services solution?
If so, see Large Merchant Services User Guide -- an introduction to the eBay Large Merchant Services solution
Are you just getting started with the eBay Developer's Program?
The following links provide useful information for beginners:
| Version | Release Date | |
|---|---|---|
| 1.4.1 | 2009-08-19 | |
| 1.4.0 | 2009-07-22 | |
| 1.2.0 | 2009-04-01 | |
| 1.1.0 | 2009-02-18 | |
| 1.0.0 | 2008-11-12 |
Index of Changed Calls - 1.4.1
Documentation Changes and Errata - 1.4.1
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
None for this release.
None for this release.
For a current list of known issues, see System Announcements and the Knowledge Base.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 607.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
As of mid-April (release 665), the Merchant Data API is no longer limited to fixed-price listing APIs. For example, you can now use AddItem to list auctions.
Here are the new values supported by the uploadJobType field:
Each of these job types corresponds to a call of the same name in the Trading API.
As of January 15, 2010, eBay evaluates the CONTENT-TYPE header against the request payload format. If the CONTENT-TYPE value is incorrect for the payload, the request will fail. Previously, eBay did not validate the CONTENT-TYPE header in requests.
This HTTP header is optional. If you do not submit the CONTENT-TYPE header with your request, eBay will determine the content type from the payload.
The following table lists the correct CONTENT-TYPE header values for HTTP POST request formats:
| Request Payload Format | CONTENT-TYPE Value |
|---|---|
| XML | text/xml |
| SOAP11 | text/xml (together with the SOAPAction header, for which the value can be anything) |
| SOAP12 | application/soap+xml |
See Making An API Call for more information about the call format.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1.4.1 and Changed Functionality - 1.4.1.
The Bulk Data Exchange Service can be used in conjunction with the Trading API Platform Notification feature. When you subscribe to the BulkDataExchangeJobCompleted event, you will be notified when the processing for your jobs has finished. See Large Merchant Services Users Guide for details about how to subscribe.
Since the fileReferenceId is only returned in job status calls when the job processing has completed, the value 'Always' was changed to 'Conditionally' in the Details table.
Index of Changed Calls - 1.4.0
Documentation Changes and Errata - 1.4.0
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
| Name | Part of Schema | Type of Change |
|---|---|---|
getJobs.inputFileReferenceId |
Element | Added |
getJobStatus.inputFileReferenceId |
Element | Added |
getRecurringJobExecutionStatus.inputFileReferenceId |
Element | Added |
getRecurringJobExecutionHistory.inputFileReferenceId |
Element | Added |
None for this release.
For a current list of known issues, see System Announcements and the Knowledge Base.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 607.
If you misplace the original fileReferenceId that is returned with the createUploadJob response, you can use a job status call to retrieve it as the inputFileReferenceId. The inputFileReferenceId can be retrieved using any of the following calls: getJobs, getJobStatus, getRecurringJobExecutionStatus, and getRecurringJobExecutionHistory. The inputFileReferenceId is only returned in the job status of upload jobs.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1.4.0 and Changed Functionality - 1.4.0.
None for this release.
Index of Changed Calls - 1.2.0
Documentation Changes and Errata - 1.2.0
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
| Name | Part of Schema | Type of Change |
|---|---|---|
createRecurringJobs.dailyRecurrance |
Element | Added |
createRecurringJobs.weeklyRecurrance |
Element | Added |
createRecurringJobs.monthlyRecurrance |
Element | Added |
recurringJobDetail.dailyRecurrance |
Element | Added |
recurringJobDetail.weeklyRecurrance |
Element | Added |
recurringJobDetail.monthlyRecurrance |
Element | Added |
None for this release.
For a current list of known issues, see System Announcements and the Knowledge Base.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 607.
You can now request daily, weekly, or monthly, frequency for recurring job types by including dailyRecurrance, weeklyRecurrance, or monthlyRecurrance tags in the createRecurringJobs and getRecurringJobs calls.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1.2.0 and Changed Functionality - 1.2.0.
None for this release.
Index of Changed Calls - 1.1.0
Documentation Changes and Errata - 1.1.0
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
| Name | Part of Schema | Type of Change |
|---|---|---|
GetItemInfoReportFilter |
Complex Type | Reserved for Future Use |
GetItemJobActionType |
Complex Type | Reserved for Future Use |
ItemEventType |
Enumerated Type | Reserved for Future Use |
DownloadRequestFilter.getItemInfoReportFilter |
Element | Reserved for Future Use |
None for this release.
For a current list of known issues, see System Announcements and the Knowledge Base.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 607.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
This release includes the new job type of FeeSettlementReport.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1.1.0 and Changed Functionality - 1.1.0.
None for this release.
This is the first release of the eBay Bulk Data Exchange API.
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls are included in the initial release of the eBay Bulk Data Exchange API.
© 2008–2010 eBay Inc. All rights reserved.
eBay and the eBay logo are registered trademarks of eBay Inc.
All other brands are the property of their respective owners.