Disable All Advertising
Image
EAN-130013700330209   EAN-13 barcode 0013700330209
UPC-A013700330209   UPC-A barcode 013700330209
Product NameKordite Hefty E33020 Large Trash Bags, 20 Count, 30-Gallon
CategoryHome
Short Description20 Ct.
Amazon.comA Buy on Amazon ~ B000LNVWYY
SKU3326-7600
ModelE33020
Width2.63 inches    (convert)
Height8.5 inches    (convert)
Length5.25 inches    (convert)
Weight126 hundredths pounds    (convert)
BindingKitchen
FeaturesValue price large trash bags Includes bags twist tie 30-gallon size
Long DescriptionAll of our hefty waste bags are specifically designed to stand up to all of your toughest waste disposal tasks, whether you're cleaning up from dinner or raking leaves in your back yard.
Created07-01-2006
Modified04-28-2020 2:51:08pm
MD5c0d48d6504c2930a31fcffc7440f4e39
SHA256dcb0f8b6a3fc1dd04845f08adfc759906f9ffe6feba1ed07bdaeb1c2609a22ec
Search Googleby EAN or by Title
Query Time0.0059359

An article of interest

Making use of the tools we offer

Data Feed API v3 - Handling Product Images

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.