METAR & NWS Weather Station Observations API

Pull raw METAR strings and hourly ASOS/NWS weather station observations for any ICAO station (KORD, KJFK, KLAX…) or any lat/lon point — decoded into clean JSON with temperature, dewpoint, wind, ceiling, visibility, and flight category (VFR/MVFR/IFR/LIFR). Up to 30 days of hourly history per station.

This is the observation data that aviation tools, weather dashboards, and prediction markets (Kalshi/Polymarket weather contracts) actually resolve on — straight from official sources (aviationweather.gov + the ASOS archive), not scraped weather websites that break.

What you get

One record per station per observation:

Field	Example
station_id	KORD
station_name	Chicago O'Hare Intl
lat, lon	41.97, -87.9
utc_time	2026-06-09T18:52:00Z
temp_f, dewpoint_f	78.8, 60.1
wind_dir, wind_speed_kt	240, 12
ceiling_ft	5500
visibility_sm	10
flight_category	VFR
metar_raw	KORD 091852Z 24012KT 10SM BKN055 26/16 A3002 …
source	aviationweather.gov

Export as JSON, CSV, or Excel directly from the dataset.

Input

{
  "stationIds": ["KORD", "KMDW"],
  "latLon": [{ "lat": 40.78, "lon": -73.97 }],
  "hoursBack": 24
}

• stationIds — ICAO codes. US ASOS stations fully supported; international stations supported up to 72h lookback.
• latLon — optional points, resolved to the nearest official observation station automatically.
• hoursBack — 1 to 720. Up to 72h is served from aviationweather.gov (freshest); longer lookbacks from the ASOS archive.
• fields — optional list to slim the output (e.g. just ["temp_f"]).

Pricing

Pay per observation record — no subscription. A 24h pull for one station is ~24 records.

Why this instead of scraping a weather website?

• Primary sources. aviationweather.gov + ASOS archive — the same observations NWS publishes, with raw METAR included for auditability.
• No scrape fragility. Public JSON/CSV APIs, not HTML scraping that breaks on redesigns.
• Resolution-grade. If you settle weather derivatives or prediction-market positions, you need the observation of record, not a weather app's interpolation.

FAQ

Which stations are supported?

Any ICAO station reporting METAR. Deep history (beyond 72h) covers US ASOS stations (K-prefix).

How fresh is the data?

aviationweather.gov observations typically appear within minutes of the station report.

Can I get the exact raw METAR string?

Yes — every record carries metar_raw exactly as published.

How do I get daily max/min temperature for Kalshi weather markets?

Pull hoursBack: 24 for the station (e.g. KNYC markets resolve on Central Park-area stations) and take the max/min of temp_f — or watch this developer's other actors for a dedicated Kalshi weather-markets feed.

Does it work for a lat/lon with no airport nearby?

Yes — latLon resolves through the official NWS station registry to the nearest observing station.

Use with AI agents (MCP)

Connect your agent to the Apify MCP server (mcp.apify.com) and it can call this actor as a tool: ask for "the latest METAR observations at KNYC" or "hourly temperatures at KMDW for the last 24 hours" and the agent fills the input schema (stationIds, hoursBack) itself. Useful as a ground-truth weather lookup for trading agents, aviation assistants, and research pipelines.

More prediction-market data actors

• Kalshi Weather Markets Data (KXHIGH & KXLOW) - live bracket prices and settlement history for the markets these observations resolve.
• Prediction Market Resolution Evidence Checker - paste a Kalshi weather market URL, get the live observation that resolves it, graded.