compliance API1.1.0

Compliance API release notes

Just getting started with the Compliance API? See the following documents for details on using this API:

The API release history

The following table lists the releases for the Compliance API:

Release Version

Release Date

Description of Release

Version 1.1.0

2018-05-24 Canned Response in Sandbox for the PRODUCT_ADOPTION compliance type now returning recommended eBay Catalog products for non-compliant listings.

Version 1.0.1

2018-05-02 Enabled OUTSIDE_EBAY_BUYING_AND_SELLING and HTTPS compliance types.

Version 1.0.0

2018-03-15 Initial API release

Version 1.1.0

Canned Response in Sandbox for the PRODUCT_ADOPTION compliance type now returning recommended eBay Catalog products for non-compliant listings. Recommended catalog products are expected to start getting returned in the Production environment in July for non-compliant listings

See the getListingViolations call reference documentation for more information about this new interface and to see the sample canned response.

Version 1.0.1

Below is a summary of the changes that were made for Version 1.0.1:

  • The OUTSIDE_EBAY_BUYING_AND_SELLING compliance type was enabled in Production and Sandbox environments (only canned response returned in Sandbox). The seller can specify this compliance type in getListingViolationsSummary operation to get a total count of listings that are violating eBay's policy of including prohibited links to sites outside of eBay and/or including contact phone numbers or email addresses, and getListingViolations operation can be used to get specific data on these violations (if any).
  • The HTTPS compliance type was enabled in Production and Sandbox environments (only canned response returned in Sandbox). The seller can specify this compliance type in getListingViolationsSummary operation to get a total count of listings that are violating eBay's security requirement of using the 'HTTPS' protocol for all links (inside and outside of eBay), and this includes links to externally-hosted listing images, and getListingViolations operation can be used to get specific data on these violations (if any).
  • The X-EBAY-C-MARKETPLACE-ID request header is now optional instead of required when using getListingViolationsSummary operation.
  • Error codes 850102 and 850109 are no longer applicable to the getListingViolationsSummary operation, and have been removed from the list of error codes for that operation.

Version 1.0.0

This is the initial release of the Compliance API, Version 1.0.0

For a list of the new calls, see the Compliance API Call Reference.