Shopping.com Partners Resource Center Developer Blog

The new Shopping.com API version 3 (beta) went into production. Not sure if you should switch now? Here are 7 reasons why.

1. Unified Schema
In the previous version (2), you have to deal with different XML schema for search responses. In the new version, you only have to deal with 1 (yes, one!) unified schema for everything. While Einstein failed to discover the grand unified theory until he died, our engineers managed to design the Unified XML Schema for all of Shopping.com API search responses, whether they return categories only, products only, offers only, or any combination thereof.

2. No More Multiple Calls
That's right, folks. Whereas in API v.2 you need to make follow up calls to get merchant offers, detail specifications, or product reviews, in API v.3 it is as easy as setting the optional parameters to true. In these cases, you just need to say showProductOffers=true, showProductSpecs=true, or showProductReviews=true, and the offers, specs, or reviews will be returned. Your wish is our command.

3. Efficient Sorting in Keyword Search
More on the multiple call theme. In API v.2, you cannot specify a sort option ahead of time when doing a keyword based query. This is because our search engine may return products only, products and offers, or offers only. Each has different sort options, and you can only sort them by making a follow-up API call. In API 3, you can name your sort options with the first query. We'll understand, and return the results sorted, as your wish. Promise.

4. Easy-to-understand parameters We know you love befid, sam, tp, sf, np, nm, and all those API2 terms. Just kidding. We renamed the parameters so that they are more transparent, so that your engineers can remember them, so that new developers can learn and understand them more quickly. And errors due to misunderstanding will be a thing of the past.

Got Java? We got SDK. If you speak Java objects, this one's for you. An SDK with a library of Java classes and methods has been created, so that you don't have to write your own class definitions, construct your own REST query URLs, or write your own parser. Look at the sample code to learn. Write an SDCQueryObject, name the options, submit, and zoom. We give you the Java objects: sealed, parsed, delivered, they're yours.

6. Technical Documentation
You wanted transparency. We've spelled it out for you. You wanted education. We've written books for you. Please check out the documentation for XML Schema, Use Cases, and REST Option Reference.

7. SOAP and REST
SOAP, REST, which one is top, which one is best? Wash the dirt you throw each other with SOAP. And give the debate a REST. We got your backs. We support both. (Note: The SOAP interface is currently not working.  The issue is being addressed.)

Interested? Need help? Please contact your account managers to get your API 3 Key issued today! We're eager to please.