Visual Crossing Timeline Weather API
Commercial global Timeline API for buyer-selected addresses, partial addresses, coordinates, or US ZIP codes and date ranges. It returns historical daily and hourly records in JSON/CSV; paid plans document 50+ years of …
Questions this answers
3 · best fit firstWith event reports enabled, a buyer can query a U.S. location/date range for reported severe-wind damage. Wind events identify time, coordinates, distance from the requested location, and measured or estimated speed where available. This is Strong, not Primary, because it is a proximity search over secondary reports, severity can be absent, and recent reports can be revised.
With event reports enabled, a buyer can query a U.S. location/date range for hail reports. Returned events identify time, coordinates, distance from the requested location, and reported hailstone size where available, directly supporting where, when, and at what reported severity hail occurred.
For a buyer-selected location and window, Timeline requests can select historical station observations. Daily/hourly records carry record time and interval, contributing station IDs, source class, and temperature, precipitation, snow, wind, and gust values. Records may be weighted from up to three nearby stations, so this is Strong nearby-observation evidence rather than a raw single-station row.
Fields it delivers
10 fieldsFirst-party product documentation represents the service as worldwide/global across supported locations; exhaustive country enumeration would be misleading.
Visual Crossing publishes a free API tier of 1,000 records per day, sufficient for a standing business-use route. Higher-volume monthly and usage-priced plans are alternatives, so the qualifying route is free.
Want Visual Crossing Timeline Weather API tested on your records?
We run match and fill rates on a sample of your data, then handle the contract, security review, and delivery into your stack if it earns its place.