Shopping.com Partners Resource Center Developer Blog

We are excited to announce that API version 3 is now available to the Shopping.com Partner Network!  

API version 3 offers a faster response time, unified schema, a java SDK and clear technical documentation. Here's 7 more reason to switch to the new API version 3 today.

Partners currently using API version 2 will have 12 months to migrate to the new API platform. Migration must be completed by September 2009.

Migration Instructions for existing partners: 

• You can visit the product suite within PAC to find your API 3 key and get started. Contact your Account Manager for technical support and a new tracking ID to use with API 3. Online documentation is readily available on the Resource Center Documentation tab. Please visit the API version 3 migration page for more information.

What's different?

• Linkin ID' is now called 'Tracking ID'.
• API Key and Tracking ID must be used simultaneously in each API query. The Key provides access to the API, while the Tracking ID enables you to get credit for your traffic. You may visit API Key FAQ to learn more about API Key.
• We have changed the name of Subparameter tracking to SubTracking. In API2, it was necessary to add a parameter ('OP') directly to the offer URLs to enable subparameter tracking. You can now simply add the parameter 'subTrackingId' to your API query URLs, and the value will be automatically added to all offer URLs in the response.
• API technical documentations are now online for easy access. Additional API version 3 FAQ are now also available.
• Partners are encouraged to use the sandbox URL for testing: http://sandbox.api.shopping.com/publisher/3.0/rest/GeneralSearch?apiKey=authorized-key&trackingId=7000610. Once your site is ready for production, AU and US partners should use the domain 'publisher.usb.api.shopping.com', while EU partners should use 'publisher.usa.shopping.com'.
• Stay tuned for additional API features that will be added in the coming months. In order to take advantage of these new features, you must be on API version 3!