Image
EAN-130000030145917   EAN-13 barcode 0000030145917
UPC-A000030145917   UPC-A barcode 000030145917
Product NameStoneware Dish - Extra Large
CategoryAnimals: Pet Supplies
Amazon.comA Buy on Amazon ~ B000A7GOSU
Long DescriptionThis item has been discontinued. Stock is limited! Your dog won't tip or slide this sturdy, heavyweight dish. Feeding area will stay cleaner and food spills will be reduced. Made of quality ceramic stoneware. Attractive high-gloss finish resists bacteria and is dishwasher safe for easy cleaning. Availabe in four sizes: Small capacity measures 10oz Medium capacity measures 16oz Large capacity measures 52oz Extra Large capacity measures 77oz
Created06-27-2011 8:42:22am
Modified10-18-2016 7:16:03pm
MD5a446d4ea695a7fb1eb1e8617adaa4489
SHA25653b403399c1fae1710f970287518780c1fd8043cf7d1e6844dbe2cf19ccc9f9c
Search Googleby EAN or by Title
Query Time0.0050249

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