Shopping.com Partners Resource Center Knowledge Base

 The following provisions shall govern use of Shopping.com's Application Programmer Interface (API).

1.  Partner affirms that the contents of the API White Paper are “confidential information” and are governed by the provisions of the Confidentiality Agreements in place between Shopping.com and Partner.
2. The terms of the API White Paper govern the contents and use of API. Shopping.com reserves the right to modify the terms of the API White Paper at any time.
3. The terms of this Exhibit are an integral part of the Agreement to which it is attached.  Breach of any of the terms of this Exhibit shall constitute a material breach of such Agreement and shall entitle Shopping.com to avail itself of all legal remedies.
4. Partner shall provide written notice to Shopping.com no later than two (2) business days prior to Partner’s testing of the API and shall provide Shopping.com with notice of the expected Launch Date no later than five (5) business days prior to the Launch Date.
5. Partner recognizes that as to certain aspects of this relationship, a breach by Shopping.com would result in irreparable harm to Shopping.com.  Accordingly, Partner agrees that Shopping.com is entitled to injunctive relief as to any breaches of the provisions of this Exhibit. 

Shopping.com API White Paper

General Requirements

The Shopping.com API, “SDC API”, is a tool that can be used to submit a query (e.g. keyword) to obtain Shopping.com result data in XML format to be displayed on the partner’s website to the end user.

When planning the implementation of the SDC API it is important to keep in mind thatShopping.com frequently adds new XML elements and parameters to enhance the product offering. Partner must ensure that its implementation allows for this flexibility so it can take advantage of these new elements in the future. The order that the XML elements are returned should also remain flexible. Depending on the result type, the elements may be returned in different orders. If Shopping.com changes or removes any existing field, Shopping.com will provide Partner with advanced notice.

The following are SDC API usage requirements which must be met by all partners submitting queries to the SDC API. In some cases an amendment to the SDC API usage requirements will preempt the terms listed below.

1. Access to the SDC API and to information contained in SDC API Result Sets shall be solely through the Partner Site and displayed only for end users of the partner site. The SDC API results shall not be permitted or facilitated through any other Web site or means whether under Partner’s ownership and control or otherwise. No sub-licensing, re-packaging, or other use (including “service bureau” use) shall be permitted.
2. Domain Listings and Store Offers returned in each SDC API Result Set must be displayed on a pre-existing Web page, to an End User and in the order received. SDC API tag elements shall not be edited or modified, stored or cached.
3. No substitution shall be made for page URLs included in SDC API Result Sets, and SDC API links shall convey users directly to such page URLs within the same browser window and without any framing, redirection (with the exception of redirection through a tracking system), or interstitial advertising (including pop-up or pop-under ads).
4. Partner must include the Shopping.com Logo and pixel returned in the API Result Set on each page of the Partner Site displaying Shopping.com Data.
5. Queries to the SDC API must contain all required parameters. A maximum of one (1) SDC API query may be submitted for each Web page on which SDC API content is displayed.
6. No more than 250,000 SDC API queries may be submitted per partner per day.
7. SDC API tag elements shall not be edited or modified, stored or cached.
8. DNS caching, the use of localized DNS or hard coding the Shopping.com API server IP address, should only be used in combination with the Shopping.com time to live (TTL) DNS configuration which is 4 hours.
9. SDC API links shall not be commingled with Partner or third-party links.
10. Tracking – Shopping.com will create a Partner account in its system and supply Partner with a  specific Linkin ID. It is essential that Partner include this linkin ID in all requests to the API so that the activity will be reported to Partner account to receive referral revenue.
11. Minimum Number of Offers - For all match types where store-offers are returned, Partner must display at least 3 store-offers so that users may perform a comparison. In the event that a result has fewer than 3 results Partner must display all the results.
12. Only a user can initiate a click out to a merchant site. You can only display merchant links on your site when the specific merchant details and offer information are prominently displayed. There must be a clear indication that the user is leaving your site to have the option to purchase the product.

Implementation Recommendations

When planning the implementation of the SDC API it is important to keep in mind that we frequently add new XML elements and parameters to enhance the product offering. If you ensure that your implementation allows for this flexibility it will be easier to take advantage of these new elements.

If we change or remove any existing field, we will provide you with advanced notice.

Also, the order that the XML elements are returned should remain flexible. Depending on the result type, the elements may be returned in different orders.

Implementation Guide

Please refer to the Implementation Guide online for the detailed integration instructions.

https://partners.shopping.com/ResourceCenter_ApiImplGuide.external?sp=Simplementation

Back to Category Index