# Japan Volcano Warnings & Activity (`shiokoshi356/japan-volcano-data`) Actor

Real-time Japan volcano warnings and activity data from JMA. Covers all active volcanoes with alert levels, eruption warnings, and activity reports.

- **URL**: https://apify.com/shiokoshi356/japan-volcano-data.md
- **Developed by:** [Shiokoshi356](https://apify.com/shiokoshi356) (community)
- **Categories:** Other, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.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?

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

## Japan Volcano Warnings & Activity Data

Real-time Japan volcano warnings, eruption alerts, and activity reports scraped from the Japan Meteorological Agency (JMA). Covers all active volcanoes in Japan with alert levels, eruption warnings, and detailed activity information.

### What Data Does This Actor Provide?

- **Volcano Warnings**: Current eruption warnings and alert levels for all monitored Japanese volcanoes (Sakurajima, Mt. Fuji, Mt. Aso, Kirishima, etc.)
- **Activity Reports**: Regular volcano activity status updates and observation summaries
- **Alert Levels**: JMA 5-level volcanic alert system (Level 1-3 + special warnings)
- **Real-time Updates**: Data sourced directly from JMA official APIs

### Use Cases

- **Disaster monitoring & early warning systems**: Integrate real-time volcano alerts into emergency response platforms
- **Academic research**: Analyze historical eruption patterns and volcanic activity trends across Japan
- **Travel safety applications**: Provide travelers with current volcano alert levels near their destinations
- **Insurance & risk assessment**: Monitor volcanic risk levels for property and travel insurance models
- **News & media monitoring**: Automated tracking of volcano status changes for reporting

### Input Parameters

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `data_type` | string | `"all"` | `"warnings"`, `"activity"`, or `"all"` |
| `volcano_name` | string | — | Filter by volcano name (Japanese or partial match) |
| `max_results` | integer | `100` | Maximum results (1-5000) |
| `log_level` | string | `"INFO"` | `DEBUG`, `INFO`, `WARNING`, or `ERROR` |

### Output Schema

Each record in the dataset contains:

```json
{
    "volcano_name": "桜島",
    "volcano_code": "506",
    "record_type": "warning",
    "alert_level": 3,
    "alert_level_text": "Level 3 - Mountain Entry Restriction",
    "title": "噴火警報・予報（対象火山）",
    "description": "レベル３（入山規制）",
    "issued_at": "2024-01-15T10:00:00+09:00",
    "event_id": "506",
    "serial": null,
    "condition": "Continuing",
    "affected_areas": null,
    "source": "Japan Meteorological Agency (JMA)"
}
```

#### Alert Level Reference

| Level | Code | English | Japanese |
|-------|------|---------|----------|
| 1 | 11 | Be Aware (Active Volcano) | 活火山であることに留意 |
| 2 | 12 | Crater Area Restriction | 火口周辺規制 |
| 3 | 13 | Mountain Entry Restriction | 入山規制 |
| — | 22 | Crater Area Danger | 火口周辺危険 |
| — | 23 | Mountain Entry Danger | 入山危険 |
| — | 36 | Surrounding Sea Area Warning | 周辺海域警戒 |

### Data Source

- **Provider**: Japan Meteorological Agency (JMA) / 気象庁
- **License**: CC BY 4.0 compatible (Japanese government open data)
- **Endpoints**:
  - Warnings: `https://www.jma.go.jp/bosai/volcano/data/warning.json`
  - Activity: `https://www.jma.go.jp/bosai/volcano/data/info.json`
- **Update frequency**: Updated by JMA as conditions change (typically daily for active volcanoes)

# Actor input Schema

## `data_type` (type: `string`):

Type of volcano data to fetch. 'warnings' for eruption warnings/alerts, 'activity' for activity reports, 'all' for both.

## `volcano_name` (type: `string`):

Filter by volcano name (Japanese or English). Leave empty for all volcanoes.

## `max_results` (type: `integer`):

Maximum number of results to return.

## `log_level` (type: `string`):

Logging verbosity level.

## Actor input object example

```json
{
  "data_type": "all",
  "max_results": 100,
  "log_level": "INFO"
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("shiokoshi356/japan-volcano-data").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("shiokoshi356/japan-volcano-data").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 '{}' |
apify call shiokoshi356/japan-volcano-data --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,shiokoshi356/japan-volcano-data"
        }
    }
}

```

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/VwGU7B1OFj9rE3IeB/builds/OvM1eEisuqVYhhAnz/openapi.json