Image
EAN-139781415713952   EAN-13 barcode 9781415713952
Product Name7 Men from Now
Amazon.comA Buy on Amazon ~ B000BDH6DU
Similar Items0012569821446: Colt .45 / Tall Man Riding / Fort Worth
0012569760257: Man Behind the Gun / Thunder Over the Plains / Riding Shotgun
0012569690721: Ride The High Country
0012236182726: Wagon Wheels
0011927110246: The Gunfighter [Dvd]
0011891801003: Along Came Jones / Fury at Showdown
0011301627773: Day of the Outlaw
0009200018747: Cariboo Trail Collector Edition ~ Randolph Scott
0009200017641: Canadian Pacific Collector Edition ~ Randolph Scott, Jane Wyatt, J. Carrol Naish
Created08-30-2018 3:21:00pm
Modified05-14-2019 3:59:35am
MD5458b0e12457f0e326ee70ae4737c1a4c
SHA2564ed13af732b25588622a9f5e89a0a72f364c72544b3b7e2b2733262a4d71bb4b
Search Googleby EAN or by Title
Query Time0.0165648

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