EAN-130714043050112   EAN-13 barcode 0714043050112
UPC-A714043050112   UPC-A barcode 714043050112
Product NameRubik's Cube 4x4
CategoryToy / Game / Puzzle
Short DescriptionHeight:63.6 inches / Length:6 inches / Weight:0.65 pounds / Width:5 inches
Amazon.comA Buy on Amazon ~ B0001CU16A
Price New12.99 US Dollars    (curriencies)
Price Used12.51 US Dollars    (curriencies)
Long DescriptionThis Rubik’s Cube is bigger, better and more mind-boggling. Building on the classic 3x3” cube, this large model is 4x4” and requires some fun new twists and turns. Includes instruction booklet.
Similar Items4710713271357: Eastsheen Black 4x4x4 Magic Cube - With Diy Instruction Manual
0714043750029: Winning Moves Rubik's Twist Brainteaser Game
0714043050167: Rubik's Key Ring Action Game
0714043050075: Winning Moves Games Rubik's 2 x 2 Cube
Created02-24-2013 8:05:13pm
Modified05-04-2021 11:23:32pm
Search Googleby EAN or by Title
Query Time0.0114269

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.