Image
EAN-130024543092742   EAN-13 barcode 0024543092742
UPC-A024543092742   UPC-A barcode 024543092742
Product NameSolaris & Abyss (Widescreen Edition and full edition)
CategoryElectronics / Photography: A/V Media: Movie / TV
Amazon.comA Buy on Amazon ~ B0000C23EL
IMDbIMDb Link
Run Time270 minutes
Aspect Ratio2.35:1
CastEd Harris, George Clooney, Mary Elizabeth Mastrantonio, Natascha McElhone, Ulrich Tukur
Run Time270 minutes
Width5.75 inches    (convert)
Height1 inches    (convert)
Length7.75 inches    (convert)
Weight50 hundredths pounds    (convert)
BindingDvd
FormatColor, NTSC, Subtitled, Widescreen
Run Time270 minutes
Long DescriptionSOLARIS/ABYSS - DVD Movie
Created05-22-2010
Modified07-27-2018 11:27:13pm
MD5fe3218fec0743d78376c63666c4d7c52
SHA256239a762d336e7cad63b727fef2767484bd0525c32c4e6fd2485af1505b4be2ea
Search Googleby EAN or by Title
Query Time0.0146430

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