Open-Meteo Weather Scraper

Look up current weather or a multi-day forecast for any place on Earth — by name or by coordinates — using the free Open-Meteo API. No API key, no login, no sign-up.

Give it a list of place names (["Berlin", "Tokyo", "New York"]) and it geocodes each to its top match, then returns clean, structured weather rows with a human-readable description (e.g. Partly cloudy, Slight rain, Thunderstorm) instead of a raw WMO code.

Modes

• current — current conditions per place: temperature, feels-like, humidity, precipitation, wind, weather text.
• forecast — one row per day (up to Forecast days, max 16): daily high/low, precipitation total, max wind, weather text.
• geocode — just resolve place names to coordinates + metadata (country, region, timezone, population). No weather call.

What you get per row

geocode: place, name, latitude, longitude, country, admin1 (region/state), timezone, population.

current: place, latitude, longitude, time, temperature, apparentTemperature, humidity, precipitation, windSpeed, weatherCode, weather (text), timezone.

forecast (one row per day): place, latitude, longitude, date, tempMax, tempMin, precipitationSum, windSpeedMax, weatherCode, weather (text).

Units are Open-Meteo defaults: temperatures in °C, wind in km/h, precipitation in mm.

Input

Field	Notes
mode	current (default), forecast, or geocode.
places	List of place names. Each is geocoded to its top match.
latitude / longitude	Optional exact coordinates, used only when places is empty.
forecastDays	Days for forecast mode, 1–16 (default 7).
maxItems	Caps total output rows across all places (default 100).

You must provide either places or both latitude and longitude.

Output

One dataset row per place (geocode/current) or per day (forecast). Pricing is pay-per-result: you are only charged for genuine result rows (ok: true). Rows we couldn't deliver are never charged — this includes:

• empty/invalid input (a single ok: false row with errorCode: "BAD_INPUT" — e.g. no place and no coordinates, or an unknown mode),
• a place that couldn't be geocoded / produced no data (NO_RESULTS),
• rate limits or network errors (RATE_LIMITED / NETWORK).

When some places resolve and others don't, the unresolved ones are listed under unresolved on the run log; the resolved rows are still returned and charged.

Proxy

Open-Meteo is a public, no-auth JSON API with no anti-bot, so no proxy is required and the default runs without one (saving proxy credits). Only enable Apify Proxy if you hit IP rate limits at very high volume.

Troubleshooting

• Getting a BAD_INPUT row? Provide places, or both latitude and longitude, and a valid mode.
• A place came back as NO_RESULTS? Try a more specific name (add the country, e.g. "Springfield, US"), or use direct coordinates.

Example

{ "mode": "forecast", "places": ["Paris", "Madrid"], "forecastDays": 5 }

Notes

Weather codes follow the WMO interpretation table and are mapped to short English text in the weather field; the raw number is kept in weatherCode. Data and geocoding come from Open-Meteo — please review their terms for attribution and fair-use limits at high volume.

Pricing

$0.20 per 1,000 rows ($0.0002 each), plus $0.001 each time a run starts. Flat rate — no volume tiers, no plan gates — and you are charged only for rows actually returned.

In forecast mode a row is one day, so a 7-day forecast for 10 cities is 70 rows: $0.014 plus the start fee. In current and geocode mode a row is one place.

Billing

Two charges apply: a $0.001 run-start fee each time a run begins, and $0.0002 per result row delivered. Samples, diagnostics, duplicates, blocked look-ups and no-result runs never incur the per-result fee — a run that returns nothing costs only the $0.001 start fee. No proxy is used by default, so there is no proxy line on your bill.