Weather API — forecast, history & air quality (no key)

Get global weather over a clean HTTP API — forecast, past weather and air quality — by city name or coordinates. Powered by Open-Meteo's open data, wrapped so you just pass a city and get clean JSON: no API key, no separate geocoding step, no signup. Pay per query.

• 🌦️ Forecast — up to 16 days, current conditions + daily (temp, precip, wind, UV, sunrise/sunset)
• 🏙️ By city name — "Tokyo", "Buenos Aires" — auto-geocoded to coordinates for you (or pass lat/lon)
• 🕰️ History — past weather for any date range (80+ years of archive)
• 🌫️ Air quality — PM2.5, PM10, ozone, NO₂, US & European AQI
• 📍 Geocode — turn a place name into coordinates + timezone
• ⚡ HTTP API (Standby) + usable from AI agents (MCP)

Sample output (forecast)

{
  "ok": true,
  "place": { "name": "Tokyo", "country": "Japan", "latitude": 35.69, "longitude": 139.69, "timezone": "Asia/Tokyo" },
  "current": { "temperature_2m": 19.0, "weather_code": 1, "wind_speed_10m": 8.3, "relative_humidity_2m": 64 },
  "daily": { "time": ["2026-09-18","2026-09-19","2026-09-20"], "temperature_2m_max": [24.1,25.0,22.8], "precipitation_sum": [0,1.2,5.4] }
}

How to use

HTTP API (Standby — recommended)

Base URL: https://synthetic-ia--open-meteo-weather.apify.actor with header Authorization: Bearer <APIFY_TOKEN>.

Endpoint	Body	Does
POST /forecast	{ city | latitude,longitude, days?: 1-16, current?, daily?, hourly?, temperatureUnit? }	Weather forecast
POST /history	{ city | latitude,longitude, start_date, end_date, daily?, hourly? }	Past weather
POST /air-quality	{ city | latitude,longitude, current?, hourly? }	Air quality
POST /geocode	{ name, count?: 1-20, language? }	Place → coordinates
GET /	—	Endpoint list

GET /forecast?city=Paris&days=3 also works (query-string form).

# 3-day forecast for a city (auto-geocoded)
curl -X POST ".../forecast" -H "Authorization: Bearer $APIFY_TOKEN" \
  -d '{"city":"Buenos Aires","days":3}'

# Air quality
curl -X POST ".../air-quality" -H "Authorization: Bearer $APIFY_TOKEN" -d '{"city":"Delhi"}'

# Past weather for a date range at coordinates
curl -X POST ".../history" -H "Authorization: Bearer $APIFY_TOKEN" \
  -d '{"latitude":40.71,"longitude":-74.01,"start_date":"2026-01-01","end_date":"2026-01-31"}'

Input

• operation — forecast, history, air-quality or geocode.
• city — place name (auto-geocoded). Or latitude + longitude.
• days — forecast length (1-16). start_date/end_date — history range (YYYY-MM-DD).
• current / daily / hourly — comma-separated Open-Meteo variables (empty = sensible defaults). See open-meteo.com docs for variable names.
• temperatureUnit — celsius or fahrenheit.

Pricing

Per query from $0.01 (drops to $0.003 on higher tiers). Platform usage included. A /forecast by city does the geocoding + weather in one query fee.

Related Actors

• ESPN Sports Data API & Yahoo Finance API — more clean no-key data APIs.

FAQ

Do I need a key? No. Open-Meteo is open data and we handle geocoding too.

How far back does history go? Decades — Open-Meteo's reanalysis archive covers 80+ years.

Which variables can I request? Any Open-Meteo variable (temperature_2m, precipitation, wind_gusts_10m, uv_index, soil_moisture…). Pass them in current/daily/hourly.

Legal

Weather data by Open-Meteo (open data). Use is subject to their terms; attribute Open-Meteo where appropriate.