eBay Commerce Network API General Requirements

The eBay Commerce Network API, (ECN API"), is a tool for submitting a query (e.g. keyword) to obtain eBay Commerce Network result data in XML format to be displayed on the Publisher's website to the end user.

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

  1. 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 eBay to avail itself of all legal remedies.
  2. Publisher shall provide email notice to ECN, including projected traffic volume, no later than two (2) business days prior to Publisher's load testing of the API and shall limit test traffic volumes to expected production levels.  Publisher shall provide ECN with email notice of the expected Launch Date of Publishers site no later than five (5) business days prior to the Launch Date.  ECN reserves the right to deny or require delay of load testing or launch based on available capacity.
  3. Access to the ECN API and to information contained in ECN API result sets shall be solely through the Publisher Site and displayed only for end users of the Publisher site. The ECN API results shall not be permitted or facilitated through any other Web site or means whether under Publisher's ownership and control or otherwise. No sub-licensing, re-packaging, or other use (including "service bureau" use) shall be permitted.
  4. Information returned by the ECN API shall not be edited or modified, stored or cached, unless otherwise previously agreed upon with ECN.
  5. Store offers returned by the ECN API must be displayed on a pre-existing web page, to a visitor and in the order received.  The store (merchant) name and offer price must be displayed along with each store offer, and it must be made clear to the user that they are leaving your site.
  6. No substitution shall be made for page URLs included in ECN API result sets, and ECN 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).
  7. Publisher must include the ECN tracking image returned in the API result set on each page of the Publisher Site displaying ECN API results.
  8. Queries to the ECN API must contain all required parameters, including apiKey, trackingId, visitorIPAddress, and visitorUserAgent.
  9. No more than 250,000 ECN API queries may be submitted per Publisher per day, unless otherwise previously agreed upon with Shopping.com.
  10. 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 of 4 hours.
  11. Store offers returned by the ECN API shall not be commingled with Publisher or third-party store offers.
  12. Shopping.com will create a Publisher account in its system and supply Publisher with a specific Tracking ID. It is essential that Publisher include this tracking ID in all requests to the API so that the activity will be reported to Publisher account to receive referral revenue.
  13. Minimum Number of Offers - For all results where store offers are returned, Publisher must display at least 3 store offers so that users may perform a comparison. In the event that a result has fewer than 3 store offers Publisher must display all available store offers.
  14. Only a user can initiate a click out to a merchant site/store (“Merchant Referral”). You can only display offer URLs 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.