Disable All Advertising
Image
EAN-130643858958392   EAN-13 barcode 0643858958392
UPC-A643858958392   UPC-A barcode 643858958392
Product Name33' Fiberglass Running Wire Cable Coaxial Electrical Fish Tape Pull Push Kit
CategoryHardware
Amazon.comA Buy on Amazon ~ B075174GG6
Price New24.45 US Dollars    (curriencies)
Width1 inches    (convert)
Length36 inches    (convert)
Weight117 hundredths pounds    (convert)
FeaturesFor running wire through walls, attics, crawl spaces, sub-floors and suspended ceilings Great for installing cable, Includes (3.3FT) 10 rods with threaded brass connectors, 3/16" flexible acrylic connection, brass push and pull rods, Rods connect for extension up to 33FT., Comes with plastic storage case, Fiberglass rod diameter is 3/16"
Long Description✔CLEVER DESIGN These non-conductive fiberglass rods can be screwed together to form longer lengths for running wire through walls, attics, crawl spaces, sub-floors, and suspended ceilings. ✔KIT INCLUDES (10) 39 in. rods with threaded brass connectors, a 6-1/2 in. flexible acrylic connection that can be set to any angle, a brass hook end for pulling, and a brass eye end for pushing Material:Fiberglass, brass Quantity:10 Product Length:33 Ft. Shipping Weight:1.24 lb. Size(s):3/16 in.
Similar Items0792363653725: 11' Electric Fiberglass Wire Pull Rods Fish Tape
0783310061861: Greenlee 06186 Cablecaster Wire Pulling Tool With Three Darts
0713976627996: Klein Tools 56119 Illuminated Fish Rod Tip
0701904916663: Cen-Tech 65327 3/16" x 11' Fiberglass Wire Running Kit
0682017350806: Cable Matters (20-Pack) Blank Keystone Jack Inserts in White
0625912234123: Rack-A-Tiers BB3412 Bumper Balls
0609465967943: Cable Matters 25 Pack, Cat6 Rj-45 Keystone Jack In White
0092644560057: Klein Tools 56005 25-Feet Depth Finder High Strength 1/4-Inch Wide Steel Fish Tape
Created04-18-2018 12:46:59am
Modified04-29-2020 9:27:10pm
MD508e3a20bd16a415d1cbcdac4dc70c4d8
SHA256f04b3f58850e2a426cfa36c0adf1e3741666c8db3ddab909b77e8cc0b07bd395
Search Googleby EAN or by Title
Query Time0.0218842

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.