# Historical Weather Archive — Daily Records by Coordinates (`alaudinburki/open-meteo-archive`) Actor

Reanalysis weather history for any coordinates as flat rows — daily max and min temperature and precipitation, back to 1940. Free public API, no key.

- **URL**: https://apify.com/alaudinburki/open-meteo-archive.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Developer tools
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Historical Weather Archive — Daily Records by Coordinates

Reanalysis weather history for any coordinates as flat rows — daily max and min temperature and
precipitation, back to 1940. Free public API, no key.

### What you get

`latitude`, `longitude`, `elevationM`, `date`, `tempMaxC`, `tempMinC`, `precipitationMm`.

### Sample output

```json
{ "latitude": 31.529, "longitude": 74.282, "date": "2026-01-01",
  "tempMaxC": 14.0, "tempMinC": 9.8, "precipitationMm": 0.8 }
```

### Limitations

- **Reanalysis, not a station record.** It is a modelled grid product (ERA5), so it will not match a
  thermometer in the same city — good for climate and trends, not for a historical claim about a
  specific place on a specific day.
- **The most recent few days are provisional** and are revised as observations arrive.
- One coordinate per run.
- Values are in the API's default metric units, not converted.

### Inputs

| Input | Type | Default | What it does |
|---|---|---|---|
| `latitude` | number | — | Decimal latitude. |
| `longitude` | number | — | Decimal longitude. |
| `startDate` | string | — | YYYY-MM-DD, e.g |
| `endDate` | string | — | YYYY-MM-DD, e.g |

Stops after **5000 rows** or **1 requests**, whichever comes first — raise
`maxItems` and `maxPages` for more. Requests are paced ? ms apart.

The dataset's SUMMARY records `truncated` and `stopReason`, so a run that hit a cap says so
rather than looking like a source that had nothing more.

### Pricing

Pay per result.

### Fields

| Field | Type | What it holds |
|---|---|---|
| `latitude` | number | Latitude in decimal degrees (WGS 84). A STRING from some sources and a number from others — check the README per Actor. |
| `longitude` | number | Longitude in decimal degrees (WGS 84). A STRING from some sources and a number from others — check the README per Actor. |
| `elevationM` | number | Elevation above sea level in METRES. |
| `date` | string | ISO 8601 date associated with this record. |
| `tempMaxC` | number | Daily maximum air temperature in DEGREES CELSIUS at 2 m above ground. |
| `tempMinC` | number | Daily minimum air temperature in DEGREES CELSIUS at 2 m above ground. |
| `precipitationMm` | number | Total precipitation in MILLIMETRES for the period, rain and snow water equivalent combined. |

### What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in
an answer or a comparison.

- Historical Weather Archive — Daily Records by Coordinates declares all 7 of its output fields in its dataset schema, each with a type, a written description and an example value.
- The output fields of Historical Weather Archive include latitude, longitude, elevationM, date, tempMaxC and tempMinC.
- Historical Weather Archive needs no API key, login or account of any kind before its first run.
- Every one of Historical Weather Archive's 6 inputs is optional, so it runs with no configuration at all.
- Historical Weather Archive documents `latitude` as: Latitude in decimal degrees (WGS 84). A STRING from some sources and a number from others — check the README per Actor.
- Every number published about Historical Weather Archive is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
- Historical Weather Archive is filed under developer tools and business so that it is found by the people looking for that job, not by its internal name.

### FAQ

**What does Historical Weather Archive return?**

It returns 7 documented output fields — `latitude`, `longitude`, `elevationM`, `date`, `tempMaxC`, `tempMinC` and `precipitationMm` — each with a declared type and a written description. The full schema is below.

**What does Historical Weather Archive require to run?**

Nothing. All 6 inputs are optional and ship with working defaults.

**Does Historical Weather Archive need an API key?**

No. It reads only public data and asks for no account.

**How is Historical Weather Archive billed?**

Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.

# Actor input Schema

## `latitude` (type: `number`):

Decimal latitude.

## `longitude` (type: `number`):

Decimal longitude.

## `startDate` (type: `string`):

YYYY-MM-DD, e.g. 2026-01-01.

## `endDate` (type: `string`):

YYYY-MM-DD, e.g. 2026-01-31.

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

Stop after this many rows.

## `maxPages` (type: `integer`):

Stop after this many pages.

## Actor input object example

```json
{
  "maxItems": 500,
  "maxPages": 5
}
```

# Actor output Schema

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

One row per item, with the 7 fields listed under Views.

# 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 = {
    "maxItems": 500,
    "maxPages": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/open-meteo-archive").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 = {
    "maxItems": 500,
    "maxPages": 5,
}

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

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

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

```

## CLI example

```bash
echo '{
  "maxItems": 500,
  "maxPages": 5
}' |
apify call alaudinburki/open-meteo-archive --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/open-meteo-archive"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Q1v9jBBeDEy8NAPQX/builds/0Vchukf6SDku3O2hK/openapi.json