# Weather Scraper — Current + 16-Day Forecast, No Key (`dami_studio/open-meteo-weather-scraper`) Actor

Weather for any place on Earth, by name or coordinates, at $0.20 per 1,000 rows. Get current conditions (temperature, feels-like, humidity, precipitation, wind) or a 16-day daily forecast with highs, lows, rainfall totals and readable descriptions instead of raw WMO codes. Geocoding included.

- **URL**: https://apify.com/dami\_studio/open-meteo-weather-scraper.md
- **Developed by:** [Dami's Studio](https://apify.com/dami_studio) (community)
- **Categories:** Automation, Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $0.20 / 1,000 weather results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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](https://open-meteo.com/) 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

```json
{ "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.

### Billing

Two charges apply: a **$0.001 run-start fee** each time a run begins, and the per-result fee for results actually 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.

# Actor input Schema

## `mode` (type: `string`):

What to return: "current" = current conditions per place, "forecast" = one row per day (up to Forecast days), "geocode" = just resolve place names to coordinates and metadata.

## `places` (type: `array`):

List of place names to look up (e.g. \["Berlin", "Tokyo", "New York"]). Each is geocoded to its top match. Leave empty if you provide Latitude + Longitude directly.

## `latitude` (type: `string`):

Optional. Use exact coordinates instead of a place name. Only used when Places is empty. Must be paired with Longitude. Example: 52.52.

## `longitude` (type: `string`):

Optional. Use exact coordinates instead of a place name. Only used when Places is empty. Must be paired with Latitude. Example: 13.41.

## `forecastDays` (type: `integer`):

Number of days to return in forecast mode (1-16). Ignored in current / geocode modes.

## `maxItems` (type: `integer`):

Maximum total output rows across all places. Caps forecast rows too (each forecast day is one row).

## `notionConnector` (type: `string`):

Optional. Write each item as a page into your Notion when the run finishes. Authorize a Notion connector once in Settings → API & Integrations → MCP connectors, then pick it here. Leave empty to skip (default) — results are always saved to the dataset regardless.

## `notionParentId` (type: `string`):

Optional. The Notion data source ID of the database to write into (only used if a Notion connector is set). Leave empty to create the pages privately in your workspace instead.

## `proxyConfiguration` (type: `object`):

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

## Actor input object example

```json
{
  "mode": "current",
  "places": [
    "Berlin",
    "London",
    "Tokyo"
  ],
  "forecastDays": 7,
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Scraped rows are stored in the default dataset (one row per result). Blocked/empty/error runs return a single uncharged diagnostic row instead.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "places": [
        "Berlin",
        "London",
        "Tokyo"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dami_studio/open-meteo-weather-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "places": [
        "Berlin",
        "London",
        "Tokyo",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("dami_studio/open-meteo-weather-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "places": [
    "Berlin",
    "London",
    "Tokyo"
  ]
}' |
apify call dami_studio/open-meteo-weather-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=dami_studio/open-meteo-weather-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/clnKMoWgu0q7k9Eao/builds/8fTsnZhPVXna9mMsR/openapi.json