The haps on the API...

[Prosperent Andrew]

While working on the new Performance Ads, some changes have been made that will affect the API.

Here they are:

1. image_thumb_url will be deprecated. There is no sense in us using valuable bandwidth when you can change the size of the image in the image_url node. That being said, you will be able to specify the size of the image you would like returned. No more string replacing on your end.
   
   
2. There will be a new property that you can set to improve API performance. It is called enableFullData. Basically, we store most of the API data in memory. We then do a database lookup to retreive the rest of the larger data that we cannot store in memory (mainly the product description). By setting this to false, the lookup is bypassed and we send you the data from memory. This will also improve bandwidth because there will be a lot less data to send back to your app. EnableFullData will default to true for backwards compatibility. More on this later...
   
   
3. The standard query will now automatically group by productId. A new node will be introduced for each product called groupCount. This will make it easier for you to determine if there are multiple products that share the same productIds for comparison purposes.
   
   UPDATE: We will also be providing the following nodes: min_price, max_price, min_price_sale and max_price_sale. No need to determine those on your end any longer.
   
   
4. The standard query will return looser results. For example, currently you may run a search that returns one product. Now it will return other closely related products along with the other product.

More details to come when this is closer to be launched...

[700]

Wow!!!! I love those improvements!

[AcidRaZor]

lol at the groupCount node. I actually implemented something similar a few weeks ago. It really isn't rocket science to do you know, especially with the API. But having less processing on my end is probably good... I think.

I'm just wondering where I'd be using the enableFullData though, since I tend to use the description (even though trimmed to fit) in my search results. mmmmmm think think think think...

[prosperent brian]

We went through theNetPool as an example, and there are only two pages on the entire site that use the description.

[312k1t]

What is the default value for parameter enableFullData? I hope that true. Otherwise I would have to do a some changes in my code.

[bigshell]

What is the default value for parameter enableFullData? I hope that true. Otherwise I would have to do a some changes in my code.

Read the first post.

While working on the new Performance Ads, some changes have been made that will affect the API.

Here they are:

1. image_thumb_url will be deprecated. There is no sense in us using valuable bandwidth when you can change the size of the image in the image_url node. That being said, you will be able to specify the size of the image you would like returned. No more string replacing on your end.
   
   
2. There will be a new property that you can set to improve API performance. It is called enableFullData. Basically, we store most of the API data in memory. We then do a database lookup to retreive the rest of the larger data that we cannot store in memory (mainly the product description). By setting this to false, the lookup is bypassed and we send you the data from memory. This will also improve bandwidth because there will be a lot less data to send back to your app. EnableFullData will default to true for backwards compatibility. More on this later...
   
   
3. The standard query will now automatically group by productId. A new node will be introduced for each product called groupCount. This will make it easier for you to determine if there are multiple products that share the same productIds for comparison purposes.
   
   
4. The standard query will return looser results. For example, currently you may run a search that returns one product. Now it will return other closely related products along with the other product.

More details to come when this is closer to be launched...

[prosperent brian]

true of course

[Prosperent Andrew]

The standard query will now automatically group by productId. A new node will be introduced for each product called groupCount. This will make it easier for you to determine if there are multiple products that share the same productIds for comparison purposes.

UPDATE: We will also be providing the following nodes: min_price, max_price, min_price_sale and max_price_sale. No need to determine those on your end any longer.