Image
EAN-130000002007052   EAN-13 barcode 0000002007052
UPC-A000002007052   UPC-A barcode 000002007052
Product NameAnza Large Hunter, 5 1/8 Fixed Blade Knife 705
CategoryHardware: Tools
Short DescriptionLb
Amazon.comA Buy on Amazon ~ B0001WAZSY
Price New83.52 US Dollars    (curriencies)
Weight14.4 ounces    (convert)
BindingSports
Long DescriptionAnza Large Hunter. 10" overall. 5 1/8" blade made from a file which has been annealed, cold ground and polished. Laminated plastic impregnated wood finger grooved handle. Handle colors will vary. Full tang construction. Top grain cowhide belt sheath. Handmade in the USA
Created07-01-2006
Modified06-29-2020 4:07:47am
MD50b66b8e1ac576c6e30f333ca8fc485ff
SHA256fcedae859b7b614095ef15dd5abf2a92b4ff8fabfc994fe1efd13454063420e1
Search Googleby EAN or by Title
Query Time0.0044539

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