Image
EAN-130027616851390   EAN-13 barcode 0027616851390
UPC-A027616851390   UPC-A barcode 027616851390
Product NameMisery
CategoryElectronics / Photography: A/V Media
Short DescriptionDVD
Amazon.comA Buy on Amazon ~ 0792846443
Similar Items5014437809032: Pet Semetary [DVD]
5014138287344: Children Of The Corn
3333297524612: Flatliners
0715515009133: The Silence of the Lambs
0097361379449: Fatal Attraction
0097360164626: The Dead Zone
0085391174257: 4 Film Favorites Thrillers
0025192137624: Caveman's Valentine
0012569832299: Stephen King Thriller Collection: The Shining/ Shawshank Redemption/ Dreamcatcher
0012569722101: The Shining (Two-Disc Special Edition)
View 10 more similar items
Created07-01-2006
Modified01-05-2020 6:36:30am
MD50e74df5f36f094f8dcbddda60c7c1296
SHA2564d4c016efec3c27983218620a1451aa1133ddac42f44d31454352ea290fe4c91
Search Googleby EAN or by Title
Query Time0.0190210

Article of interest

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.

Close

Search

Close

Share

Close

Dialog