# Japan Fireworks Live Feed (This Week's Hanabi Events) (`kaichi-labs/japan-fireworks-live-feed`) Actor

Rolling 7-day feed of Japanese fireworks (hanabi) festivals, sourced from hanabi.cloud's daily event pages. Returns event name, date, prefecture, start time, venue, and coordinates for events happening today through the next 6 days.

- **URL**: https://apify.com/kaichi-labs/japan-fireworks-live-feed.md
- **Developed by:** [Yuji Kaichi](https://apify.com/kaichi-labs) (community)
- **Categories:** Developer tools, Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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 Fireworks Live Feed (This Week's Hanabi Events)

Get a rolling **7-day feed of Japanese fireworks (hanabi) festivals** — event name, date, prefecture, start time, venue, and GPS coordinates — sourced from [hanabi.cloud](https://hanabi.cloud), a specialist hanabi-event tracking site. Every run returns what's happening **today through the next 6 days**, nationwide.

### Why this Actor

Fireworks season in Japan runs May–October with thousands of local events, most with no English coverage and no structured feed. Static "top 10 fireworks" listicles go stale within weeks. This Actor scrapes the site's own daily event pages — the same pages the site itself keeps current — so every run reflects what's actually happening this week, not a cached snapshot from months ago.

### Sample output

```json
{
  "event_name": "隅田川花火大会",
  "event_date": "2026-08-01",
  "prefecture": "東京都",
  "start_time": "19:00～",
  "location": "台東区・墨田区(隅田川)",
  "latitude": 35.7148,
  "longitude": 139.8003,
  "detail_url": "https://hanabi.cloud/html/Tokyo/tokyo/2026/2026-08-01_sumidagawa-hanabi.html",
  "scraped_at": "2026-08-01T11:30:37.935Z"
}
```

Every record includes source-verified coordinates ready to drop onto a map, and a link back to the event page for full details.

### Who uses this

- Travel-app / itinerary-planner developers surfacing "what's happening near you this week" for visitors to Japan
- Tourism boards and local-event aggregators building a live events widget
- Map/dashboard builders needing geocoded event data with no manual lookup
- Anyone automating a weekly "upcoming fireworks" digest (Slack/LINE bot, newsletter)

### Pricing

Pay per event: **1 `fireworks-event` charged per record returned.** No subscription. A full unfiltered weekly run currently returns roughly 500 records — actual per-event rate is set in the Apify Store listing.

### Input parameters

Optional. See `.actor/input_schema.json` for the authoritative schema.

| Parameter | Description |
|---|---|
| `prefectures` | Filter to specific prefectures, exact Japanese name match (array). Omit for nationwide. |

### Data freshness & scope

Each run scrapes hanabi.cloud live for the current date through +6 days — data reflects what the site shows at run time, not a cached snapshot. This is a **live/recurring** dataset by design: re-run it weekly (or via Apify's scheduler) to keep results current. Only the site's explicitly robots.txt-permitted daily/today pages are used (`/servlet/GetToday`, `/html/dayEvent/YYYYMMDD.html`); the site's bulk database endpoints are intentionally never accessed. See `DESIGN_NOTE.md` for the robots.txt analysis.

***

### For developers (this repo)

This is a lightweight-pipeline project (single `DESIGN_NOTE.md` instead of full SRS/SDD, unit tests only) — see `DESIGN_NOTE.md` for source/ToS/architecture notes.

#### Setup

```bash
npm install
```

#### Run locally

```bash
npm start
## or via Apify CLI
npx apify run
```

Local runs write to `storage/` (Apify SDK's local-dev storage emulation, gitignored) — no Apify account needed to test.

#### Tests

```bash
npm test
```

# Actor input Schema

## `prefectures` (type: `array`):

取得対象を絞り込む都道府県名（例: "東京都", "大阪府"）。日本語の完全一致で指定してください。未指定なら全国を対象にします。

## Actor input object example

```json
{}
```

# 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("kaichi-labs/japan-fireworks-live-feed").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("kaichi-labs/japan-fireworks-live-feed").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 kaichi-labs/japan-fireworks-live-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kaichi-labs/japan-fireworks-live-feed"
        }
    }
}
```

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/ynLvrw4RN3vA0ucdR/builds/ao46JFSATOnurJDs5/openapi.json