| EAN-13 | 0000002060064  |
| UPC-A | 000002060064  |
| Product Name | Grouper Fillets |
| Category | Food |
| Short Description | Lb |
| Created | 07-01-2006 |
| Modified | 12-15-2016 10:12:13am |
| MD5 | 7d2485874826b29511f31419a4d027c9 |
| SHA256 | 1c2dfcefbb68352ac50c2f9400f083351c5715c731b0458301ff06870a042dec |
| Search Google | by EAN or by Title |
| Query Time | 0.0037858 |
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.
- Unknown (should never actually appear in the API)
- Yes (a production image exists)
- No (there is no image)
- Pending (a pending image exists)
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.
- If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
- 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.