Image | |
EAN-13 | 0333420811094 |
UPC-A | 333420811094 |
Product Name | Stant 48138 XACTStat 180 Degrees Fahrenheit Thermostat |
Category | Automotive |
Amazon.com | Buy on Amazon ~ B001FIDD46 |
SKU | STN48138 |
Model | 48138 |
Price New | 10.88 US Dollars (curriencies) |
Width | 2.8 inches (convert) |
Height | 2.8 inches (convert) |
Length | 2.9 inches (convert) |
Weight | 10 hundredths pounds (convert) |
Binding | Automotive |
Features | Designed for customers that demand the exact OEM thermostat, Thermostats include all the features that make them original equipment equivalent parts, OE Type Thermostat with Jiggle Pin, This thermostat is Nissan OE # 21200V7206 |
Long Description | Stant’s XACTStat thermostats are designed for customers that demand the exact OEM thermostat as a replacement product. XACTStat thermostats include all the features that make them original equipment equivalent parts. Jiggle pins and check valves for air venting, integral seals and integrated water outlet housings. Some even have ports for attaching coolant temperature sensors. So if you want thermostats that are EXACTLY the same as the original part, order XACTStat thermostats from Stant. |
Similar Items | 0770075472650: Gates Tckwp249 Engine Timing Belt Kit With Water Pump 0686226220714: Permatex 22071 Water Pump And Thermostat Rtv Silicone Gasket, 0.5 Oz. 0072053525090: Gates 22517 Upper Radiator Hose 0072053525076: Gates 22516 Lower Radiator Hose 0072053488678: Gates K040529 Multi V-Groove Belt 0072053458633: Gates 22478 Lower Radiator Hose 0033342001275: Stant 10227 Radiator Cap - 13 Psi |
Created | 01-24-2018 9:37:39pm |
Modified | 04-29-2020 7:49:46pm |
MD5 | 09fd143871cdaf3de684e86b30906741 |
SHA256 | 355c5e4c1df2ea55355c12ffae7201c9ada2312ae28ba38b41c5c6813fc06ed8 |
Search Google | by EAN or by Title |
Query Time | 0.0206070 |
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.
- 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.