EAN-130043396059238   EAN-13 barcode 0043396059238
UPC-A043396059238   UPC-A barcode 043396059238
Product NameBlob (1988)
CategoryElectronics / Photography: A/V Media
Short DescriptionDVD
Amazon.comA Buy on Amazon ~ B00005N5RM
Similar Items9780788815256: Arachnophobia
9780778604273: Little Shop of Horrors
9342424003665: The Stuff | NON-USA Format | PAL | Region 4 Import - Australia
5060057770092: The Little Shop of Horrors
5050582376975: Fright Night
5039036024686: The Fly [Import anglais]
5035822747630: Vampires [Region 2]
4012019979877: Alligator [Import allemand]
0024543192060: Fly II
0024543004578: Fly /The Fly 2
0013132415697: Metal Shifters
Created07-01-2006
Modified10-10-2017 6:51:20am
MD5595dcd40802b965548985dac1e563d9c
SHA256f4792be189eba2f68eab593de6c670be2dd46adf27b372cfeea3769c60946896
Search Googleby EAN or by Title
Query Time0.0216529

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