Feedback API

Feedback API Release Notes

You can find links to the Feedback 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 just getting started with the Feedback API? The following describes how to join the eBay Developers Program:


Version 1.2.2

Index of Changed Calls - 1.2.2

Schema Changes - 1.2.2

Announcements - 1.2.2

New Features - 1.2.2

Changed Functionality - 1.2.2

Documentation Changes and Errata - 1.2.2

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 1.2.2

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 1.2.2

NamePart of SchemaType of Change
GetDSRSummaryResponse.totalTransactionCount Element New

Announcements - 1.2.2

Change Requests

See the System Announcements for bug fixes related to this release.

New Features - 1.2.2

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 - 1.2.2.

Total Number of Transactions Is Returned

The getDSRSummary call returns the total number of transactions in the applicable time period.

Changed Functionality - 1.2.2

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.

Meaning of Two Fields in createDSRSummaryByShippingDetail Has Changed

In the createDSRSummaryByShippingDetail call, the meanings of the shipToCountry and shippingDestinationType input fields has changed. Formerly, the fields referred to the "ship to" country. Now, the fields refer to the buyer's country-of-residence.

Documentation Changes and Errata - 1.2.2

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.2 and Changed Functionality - 1.2.2.

None for this release.

Version 1.0.1

Index of Changed Calls - 1.0.1

Schema Changes - 1.0.1

Announcements - 1.0.1

New Features - 1.0.1

Changed Functionality - 1.0.1

Documentation Changes and Errata - 1.0.1

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 1.0.1

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 1.0.1

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 any new code list values added in this release. See Code Lists.

Name Part of Schema Type of Change
BaseServiceResponse Base response container for all service operations. Modified

Announcements - 1.0.1

None for this release.

Change Requests

For a current list of known issues, see Site Status Updates and the Knowledge Base.

New Features - 1.0.1

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.

Changed Functionality - 1.0.1

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.

Optional CONTENT-TYPE Header Must Have Correct Value

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

Also see Making an API Call.

Changes to BaseServiceResponse

Schema changes were made to the BaseServiceResponse type to correct problems encountered by .NET applications.

Documentation Changes and Errata - 1.0.1

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1.0.1 and Changed Functionality - 1.0.1.

None for this release.

Version 1.0.0

This is the first release of the eBay Feedback API.

Note: To aid developers in testing and adoption, the API call limits of 10 DSR query requests per day have been relaxed for the initial release. Watch these release notes for changes to the enforcement of API call limits.

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 1.0.0

These calls are included in the initial release of the eBay Feedback API.

New Calls



Copyright © 2008–2016 eBay, Inc. All rights reserved. This documentation and the API may only be used in accordance with the eBay Developers Program and API License Agreement.