Disable All Advertising
Image
EAN-137321996294444   EAN-13 barcode 7321996294444
Product NameSans Plus Attendre
CategoryElectronics / Photography: A/V Media: Movie / TV
Amazon.comA Buy on Amazon ~ B003IKMQCY
Price New29.99 US Dollars    (curriencies)
Price Used5.62 US Dollars    (curriencies)
BindingDvd
Similar Items9780767811101: As Good As It Gets
0883929126651: Gran Torino
0883929105359: Driving Miss Daisy
0883929086696: The Blind Side
0794043690426: Secondhand Lions
0053939273427: Shawshank Redemption
0043396435469: Last Vegas
0012569817487: Grumpy Old Men/Grumpier Old Men (2pk)
Created03-30-2013 1:45:25pm
Modified10-09-2017 7:55:14pm
MD522d4d98a2cddfff7324b7daa2978a91a
SHA2562296850ac4e40daf09d086ebf888511dbe321984a224e739557d5efb6d5569b5
Search Googleby EAN or by Title
Query Time0.0235901

An article of interest

Making use of the tools we offer

Data Feed API v3 - Handling Product Images

With version 3.2 comes a new way to handle product images. This should give you more control over the images you display.

Prior to version 3.2, you simply had to check for the existance of the product>image property. If it existed and was not blank, you could safely display the image. 

Starting with version 3.2, you may want to check one more field before you display the product image. Many API users wanted access to the pending images. The only reasonable way to do this was to add a new property named product>hasImage which can be one of four values.

If you are displaying the product images to your users and you DO NOT want to display pending images that have not been checked, you should only display the image if product>hasImage=Yes. If you want to show production and pending images, you can simply check the product>image property if you like. We suggest using product>hasImage as your main check and only display the image if it meets your needs. Here are samples of the JSON structure.

The property product>hasImage will always be regurned even if you specified a list of properties in the "get" string that does not include the image property. The main reason for this is that it is possible to calculate the image path on your side thereby saving the bandwidth of returning the image path.

If you want to calculate the path to the image on your end instead of requesting it from us, you can do this in two ways. 

  1. If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
  2. If product>hasImage=Yes then it gets a little more tricky. We split the images into subfolders because there are so many of them. To calculate the path start with the 13 digit EAN and split it up like this: https://eandata.com/image/product/{1st_3_digits}/{2nd_3_digits}/{3rd_3_digits}/{13_digit_EAN}.jpg

This should make interacting with product and pending images much easier for you. Look at the example JSON shown above for working exmples of image paths.