🌦️ Weather Scraper (Open-Meteo)

Get current weather and a multi-day forecast for any city or coordinates — temperature, feels-like, humidity, precipitation, wind, UV index, sunrise/sunset and conditions. Powered by the public Open-Meteo API, so it's fast and reliable: no browser, no login, no API key. Just pass city names and it handles the geocoding for you.

Built for travel and logistics tools, dashboards, event planning and weather datasets. Export to JSON/CSV/Excel, run on a schedule, call via API, or connect to Make, Zapier or n8n.

🔎 What is the Weather Scraper?

Give it a list of locations (e.g. "Berlin", "London", or a lat,lon pair) and it returns one clean record per location: the current conditions plus a daily forecast for the days you ask for. Great for building a weather feed for many cities at once.

What data does it extract?

• Location, country, region and timezone
• Latitude, longitude and elevation
• Current: temperature, feels-like, humidity, precipitation, wind speed/direction, condition, day/night
• Daily forecast (per day): condition, max/min temperature, feels-like max, precipitation sum and probability, max wind, UV index, sunrise and sunset

⬇️ Input

Field	Type	Description
locations	array	City names (e.g. Berlin) or lat,lon pairs.
forecastDays	integer	Number of forecast days (1–16). Default 7.
temperatureUnit	string	celsius or fahrenheit.
windSpeedUnit	string	kmh, mph, ms or kn.

Example input

{
  "locations": ["Berlin", "London", "New York"],
  "forecastDays": 3,
  "temperatureUnit": "celsius",
  "windSpeedUnit": "kmh"
}

⬆️ Output

One record per location:

{
  "location": "Berlin",
  "country": "Germany",
  "region": "Land Berlin",
  "latitude": 52.52,
  "longitude": 13.41,
  "elevation": 38.0,
  "timezone": "Europe/Berlin",
  "temperature_unit": "°C",
  "current": {
    "time": "2026-06-29T13:00",
    "temperature": 26.0,
    "apparent_temperature": 27.3,
    "humidity": 58,
    "precipitation": 0.0,
    "weather_code": 1,
    "weather": "Mainly clear",
    "wind_speed": 9.0,
    "wind_direction": 210,
    "is_day": true
  },
  "daily": [
    {
      "date": "2026-06-29",
      "weather": "Partly cloudy",
      "temp_max": 28.4,
      "temp_min": 16.1,
      "precipitation_sum": 0.0,
      "precipitation_probability_max": 10,
      "wind_speed_max": 14.2,
      "uv_index_max": 7.1,
      "sunrise": "2026-06-29T04:45",
      "sunset": "2026-06-29T21:33"
    }
  ],
  "query": "Berlin"
}

💡 Use cases

• ✈️ Travel & events — show forecasts for destinations or venues.
• 🚚 Logistics — plan routes and operations around weather.
• 📊 Dashboards — build a multi-city weather feed.
• 🤖 Automation — trigger alerts when rain or heat is forecast.

❓ FAQ

Do I need an API key or login? No — it uses the public Open-Meteo API.

Can I pass city names? Yes — they're geocoded automatically. You can also pass lat,lon.

How many days of forecast? Up to 16 — set forecastDays.

Celsius or Fahrenheit? Either — set temperatureUnit.

Do I get the current conditions too? Yes — both current and a daily forecast.

Is the UV index included? Yes — the daily maximum UV index.

How does pricing work? Pay per location returned. No subscription.

Is it legal? Open-Meteo offers free weather data for non-commercial and commercial use within their terms. Use responsibly.

⚙️ How it works

The scraper geocodes each city through Open-Meteo's geocoding API, then calls the forecast API for the resulting coordinates — no browser and no key. It normalizes the response into a tidy record with a current block and a daily array, mapping WMO weather codes to readable text, so you get clean data instead of parallel arrays. Runs are fast and dependable, which is why the actor keeps passing its daily health check. The same input shape works for one city or a long list.

👥 Who uses weather data?

Weather data is valuable to travel apps, logistics teams, event planners and analysts. A travel app shows destination forecasts; a logistics team plans around storms; an event planner checks venue conditions; an analyst correlates weather with sales. Because every record is plain JSON with consistent fields, it drops straight into a spreadsheet, database, BI tool or automation with no custom parsing.

📤 Export, schedule & integrate

Every run is saved to a dataset you can export to JSON, CSV, Excel, XML or RSS, or pull through the Apify API. Wire it into Make, Zapier, n8n, Google Sheets, Slack or your own database, run it on a schedule to refresh forecasts, and call it from AI agents through the Apify MCP server.

💡 Tips for best results

• Pass many cities in one run to build a regional weather feed.
• Use a lat,lon pair for precise, non-city locations.
• Schedule a morning run to feed a daily forecast into Slack or email.
• Switch temperatureUnit to match your audience's region.

❓ More FAQ

How fresh is the data? It is fetched live on each run.

Can I run it automatically? Yes — use Apify Schedules (cron).

What if a city can't be found? It's skipped and logged — the run continues.

Which export formats? JSON, CSV, Excel, XML and RSS, plus the Apify API.

Can AI agents use it? Yes — via the Apify API and MCP server.

🔗 You might also like

• Federal Register Scraper — US government documents.
• Open Library Book Scraper — book & ISBN data.
• TheSportsDB Scraper — teams & players.

---

Keywords: weather scraper, open-meteo api, weather api, weather forecast, weather data, current weather, daily forecast, temperature data, precipitation, wind data, uv index, city weather, weather feed, forecast api, no api key weather