Image
EAN-139780812426823   EAN-13 barcode 9780812426823
Product NameThere's A Nightmare In My Closet
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionPrebound
Amazon.comA Buy on Amazon ~ 0812426827
SKUNU-ING-00067865
Price New11.24 US Dollars    (curriencies)
Price Used5.18 US Dollars    (curriencies)
Long Description
The pesky nightmare in the closet won't stay in there at night, even with the door closed all the way. When he gets out, what do you do? Comfort him and put him to bed, of course! The ultimate afraid-of-the-dark story has helped generations of kids deal with the nightmares in their own closets.A perennial favorite.
Created11-08-2012 8:51:31am
Modified12-23-2013 10:23:51am
MD573b1e4c562aac6e02ff29d95b833d247
SHA256ab636b1269f7fc07cbae607c87665f48a5ea2e8ce57bef87f320b99114a0600f
Search Googleby EAN or by Title
Query Time0.0051801

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

Close

Dialog