EAN-130012236604976   EAN-13 barcode 0012236604976
UPC-A012236604976   UPC-A barcode 012236604976
Product NameDrugstore Cowboy
CategoryElectronics / Photography: A/V Media
Short DescriptionDVD
Amazon.comA Buy on Amazon ~ 6305594333
Similar Items0011891800884: Golden Gate / City of Ghosts
9780783228471: Rumble Fish
6867449000299: Trainspotting [Region 2] [UK Import]
5060002830628: Bad Lieutenant
3259190271210: Trainspotting
9780783137322: Gus Van Sant's Last Days
9786305260622: Permanent Midnight
9781404934115: Spun
7501050617055: Last Exit to Brooklyn (Ultima Salida A Brooklyn) [PAL/REGION 2 DVD. Import-Spain]
5050070009897: Rush [Region 2]
9780792858225: Boost
9786305433873: Georgia
5060021171214: Requiem for a Dream
Modified01-04-2020 8:18:05pm
Search Googleby EAN or by Title
Query Time0.0240929

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{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:{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.