JMA Japan Forecast Scraper
Pricing
from $0.90 / 1,000 results
JMA Japan Forecast Scraper
Scrapes Japan Meteorological Agency weather forecasts by prefecture code. Returns each forecast as a flat row with temperature, precipitation probability, wind, and weather codes. Export to CSV, JSON, Excel, or XML.
Pricing
from $0.90 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
JMA Japan Forecast Scraper
Scrape Japan weather forecasts from the Japan Meteorological Agency, for any prefecture, up to a million records per run. Each forecast includes temperature, precipitation probability, wind, and weather codes, returned as flat rows. No API key required. Export to CSV, JSON, Excel, or XML.
The Japan Meteorological Agency publishes detailed local forecasts, but its website is built for human browsing, not bulk analysis. This Actor reads the public forecast pages directly, filtered by prefecture, and returns each forecast in one fixed schema. No registration, no rate limits beyond fair use.
| Who uses it | What they scrape JMA (Japan Meteorological Agency) for |
|---|---|
| Travel platforms | Displaying up-to-date weather for Japanese destinations |
| Logistics companies | Planning routes around precipitation and wind |
| Event organizers | Choosing dates with low rain probability |
| Researchers | Building historical forecast datasets |
| App developers | Powering weather widgets for Japan |
What it does
This Actor collects JMA weather forecasts by prefecture code and returns each forecast as a flat row with all available meteorological fields.
- π Prefecture filter: pick any of the 52 JMA forecast offices, from Tokyo to Yaeyama.
- π Flat rows: every forecast is one record, ready for spreadsheets or databases.
- π’ Scalable: fetch up to 1,000,000 forecasts per run for paid users.
- π No API key: the Actor reads public pages directly, no registration needed.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with JMA (Japan Meteorological Agency) data
βοΈ Power travel apps.
A travel startup pulls Tokyo and Osaka forecasts daily to show visitors what to pack.
π Optimize delivery routes.
A logistics firm checks wind and precipitation for Hokkaido to avoid delays.
πͺ Plan outdoor events.
An event organizer compares rain probability across weekends in Kyoto to pick a date.
π Build forecast archives.
A researcher collects a year of forecasts for Okinawa to study prediction accuracy.
π± Feed weather widgets.
A developer uses the Actor to keep a Japan-wide weather app updated every hour.
Why choose this scraper
| What you get | |
|---|---|
| Official source | Data comes straight from the Japan Meteorological Agency, the authoritative weather service. |
| No API key | Skip OAuth and rate limits; the Actor handles the public pages for you. |
| Fixed schema | Every forecast has the same fields, so you can merge runs without cleaning. |
| Prefecture coverage | All 52 forecast offices are supported, including remote islands. |
| Scalable | From a 10-record preview to a million-record archive, the Actor scales with your plan. |
How it compares
No other Store actor targets JMA (Japan Meteorological Agency) the same way, so the honest comparison is with the alternatives teams actually weigh.
| JMA Japan Forecast Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When JMA (Japan Meteorological Agency) changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
Drive the Actor with a single prefecture code, and it returns all forecasts for that office. The maxItems field caps how many records you pull, from 10 for a preview to 1,000,000 for a full archive. The Input tab lists every parameter.
A first run with the defaults:
{"maxItems": 10,"prefectureCode": "130000"}
A larger pull:
{"maxItems": 200,"prefectureCode": "130000"}
Pricing
Pay-per-result: $0.001 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $0.10 |
| 1,000 results | $1.00 |
| 10,000 results | $10.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the JMA Japan Forecast Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to JMA (Japan Meteorological Agency) through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/jma-japan-forecast-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check that the prefectureCode is valid. The input uses JMA office codes, not prefecture names. Use the dropdown in the input editor to select the correct code.
Why is my run limited to 10 items?
Free accounts are limited to a 10-record preview. Upgrade to a paid plan to set maxItems higher, up to 1,000,000.
The forecast data looks outdated.
JMA updates forecasts on a fixed schedule. Run the Actor again to fetch the latest data. If the issue persists, check the JMA website directly to confirm the update time.
I get an error about the prefecture code.
The code must be one of the 52 listed values, like 130000 for Tokyo. Copy the code exactly from the input schema or use the dropdown.
FAQ
| Question | Answer |
|---|---|
| Do I need a JMA API key? | No. The Actor reads the public forecast pages directly, so there is no registration or key management. |
| How many forecasts can I get? | Free users can preview up to 10 records. Paid users can set maxItems up to 1,000,000 per run. |
| Which prefectures are supported? | All 52 JMA forecast offices are available, from Hokkaido to Okinawa, including remote islands like Daito and Yaeyama. |
| What fields does each forecast include? | Each row includes temperature, precipitation probability, wind, weather codes, and other meteorological data as published by JMA. |
| Can I export the data? | Yes, you can export to CSV, JSON, Excel, or XML directly from the Apify platform. |
| How often is the forecast updated? | The Actor fetches the latest forecast from JMA at the time of the run. Schedule it hourly or daily to keep data fresh. |
| Is this legal? | JMA publishes forecasts as public information. Scraping public data for reasonable use is generally accepted, but check JMA's terms for your specific application. |
| Can I filter by date? | The Actor returns the current forecast for the selected prefecture. For historical data, run it on a schedule and store the results. |
Related actors
Browse the full ParseForge collection for more scrapers.
π Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
β οΈ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Japan Meteorological Agency. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
