Image
EAN-130025192398377   EAN-13 barcode 0025192398377
UPC-A025192398377   UPC-A barcode 025192398377
BrandUniversal Home Video
Product NameFast and the Furious
CategoryElectronics / Photography
Short DescriptionFAST AND THE FURIOUS
Amazon.comA Buy on Amazon ~ B01N0E4S22
Model31793155
Similar Items5050582702361: Fast & Furious (Import) [Blu-ray]
5050582698046: 2 Fast 2 Furious
0025195055178: 2 Fast 2 Furious [Blu-ray]
0025192400896: Fast & Furious Collection 5 & 6
0025192400889: Fast & Furious Collection 3 & 4
0025192398575: Fast & Furious 6 [Blu-ray]
0025192398506: Fast & Furious
0025192398476: Fast and the Furious Tokyo Drift
0025192398438: 2 Fast 2 Furious [Blu-ray]
Created10-03-2017 5:11:51pm
Modified04-16-2020 12:15:58am
MD598769db7529db7a9714e8cc37faeb44b
SHA25604f15dec3598b8adb558efaf4bc0ee08527c1827f47c36a7c5a6dea968493844
Search Googleby EAN or by Title
Query Time0.0202708

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