# MSN Weather Scraper (`romy/msn-weather-scraper`) Actor

Current conditions, forecast, and monthly trends for a list of coordinates, via MSN's own public weather API.

- **URL**: https://apify.com/romy/msn-weather-scraper.md
- **Developed by:** [Romy](https://apify.com/romy) (community)
- **Categories:** News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.17 / 1,000 weather lookups

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## MSN Weather Scraper

Unofficial, reverse-engineered wrapper around MSN's own public weather API. Give it one or more coordinates, get back current conditions, a multi-day forecast, and monthly climate trends as structured JSON — no scraping, no HTML parsing, no login required.

### What

A run-based Actor that takes a list of locations as input, fetches real weather data for each, and pushes one row per location to the dataset.

### Why

MSN's weather data is sourced from a real forecasting backend and kept current, but there's no public documented API for it. This Actor exposes that data as clean, queryable rows for anyone who wants real-time conditions or forecasts without building a scraper against MSN's web frontend.

### Input

| Field | Type | Required | Description |
|---|---|---|---|
| `locations` | array of `{lat, lon, label?}` | Yes | One or more coordinates. `label` is an optional name you choose, passed straight through to the output row. |
| `market` | string | No (default `en-us`) | Affects language and units (Fahrenheit for `en-us`, Celsius for others). |
| `includeForecast` | boolean | No (default `true`) | Fetch the multi-day forecast overview alongside current conditions. |
| `includeTrends` | boolean | No (default `true`) | Fetch monthly temperature/climate trend data alongside current conditions. |

**Note:** this Actor needs real decimal coordinates per location, not a free-text place name — the underlying weather backend doesn't resolve names to coordinates itself. `msn-weather-location-search-scraper` is a separate, related Actor, but it returns place/address/business entities for disambiguation, not coordinates — it does not currently fill this gap. Resolve place names to coordinates with any geocoding source of your choice before calling this Actor.

### Output

One dataset row per location:

```json
{
    "label": "Jakarta",
    "lat": -6.2088,
    "lon": 106.8456,
    "market": "en-us",
    "current": { "...": "MSN's own current-conditions payload" },
    "forecast": { "...": "MSN's own multi-day forecast payload" },
    "trends": { "...": "MSN's own monthly trend payload" }
}
```

Field names and shapes inside `current`/`forecast`/`trends` follow MSN's own API directly.

### Pricing

Pay-per-event:

- `apify-actor-start` — flat fee per run.
- `weather-lookup` — one charge per location successfully fetched.

### Known limitations

- Requires real coordinates as input — it does not resolve free-text place names on its own. Pair it with `msn-weather-location-search-scraper` for that step.
- Forecast/trends length is bounded by what MSN's own backend serves; very large ranges may return fewer days than requested.
- This Actor only wraps the weather vertical — no news, finance, or sports data.
- A location that fails (e.g. invalid coordinates) is skipped with a logged error rather than failing the whole run.

# Actor input Schema

## `locations` (type: `array`):

One or more locations as {"lat": number, "lon": number, "label": string (optional, your own name for this location, passed through to the output)}.

## `market` (type: `string`):

Affects language and units (Fahrenheit for en-us, Celsius for others).

## `includeForecast` (type: `boolean`):

Fetch the multi-day forecast overview alongside current conditions.

## `includeTrends` (type: `boolean`):

Fetch monthly temperature/climate trend data alongside current conditions.

## Actor input object example

```json
{
  "locations": [
    {
      "lat": -6.2088,
      "lon": 106.8456,
      "label": "Jakarta"
    }
  ],
  "market": "en-us",
  "includeForecast": true,
  "includeTrends": true
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# 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 = {
    "locations": [
        {
            "lat": -6.2088,
            "lon": 106.8456,
            "label": "Jakarta"
        }
    ],
    "market": "en-us"
};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/msn-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 = {
    "locations": [{
            "lat": -6.2088,
            "lon": 106.8456,
            "label": "Jakarta",
        }],
    "market": "en-us",
}

# Run the Actor and wait for it to finish
run = client.actor("romy/msn-weather-scraper").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 '{
  "locations": [
    {
      "lat": -6.2088,
      "lon": 106.8456,
      "label": "Jakarta"
    }
  ],
  "market": "en-us"
}' |
apify call romy/msn-weather-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/msn-weather-scraper"
        }
    }
}
```

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/tWlG5aoK1mBTI63BO/builds/xi9kG2udISH6Tp2uu/openapi.json