# Japan EDINET Ownership Change (`w18notes.com/japan-edinet-ownership-change`) Actor

Normalized ownership-change events from EDINET large-shareholding disclosures in Japan.

- **URL**: https://apify.com/w18notes.com/japan-edinet-ownership-change.md
- **Developed by:** [w18notes com](https://apify.com/w18notes.com) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$100.00 / 1,000 normalized ownership change events

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 EDINET Ownership Change Feed

A deterministic feed of ownership-change events derived from Japan's EDINET
large-shareholding disclosures (大量保有報告書 / 変更報告書 / 訂正報告書).

For each filing it reports **who owns how much of which company, and how the holding
changed since the previous effective disclosure** — with source traceability back to
the original EDINET document.

### What you get

Each run emits normalized JSON events (one per ownership change) to the Actor's
default **Dataset**:

```json
{
  "event_type": "change",
  "issuer_name": "株式会社テストカンパニー",
  "issuer_code": "E05320",
  "holder_name": "黒田投資顧問",
  "previous_pct": 6.11,
  "current_pct": 7.02,
  "delta_pp": 0.91,
  "purpose_changed": false,
  "previous_purpose": "direct",
  "current_purpose": "direct",
  "filed_at": "2026-04-03",
  "document_type": "大量保有報告書",
  "source_doc_id": "S100NNCD",
  "previous_source_doc_id": "S099ZZ09",
  "correction_flag": false,
  "confidence": 0.92,
  "reporting_regime": "legacy",
  "taxonomy_version": "vh001",
  "cross_regime_comparable": true,
  "comparison_status": "directly_comparable",
  "calculation_basis": "aggregate_filing_group",
  "source_url": null,
  "event_summary_en": "Holder \"黒田投資顧問\" increased holding in \"株式会社テストカンパニー\" (issuer E05320) from 6.11% to 7.02% (+0.91pp) as of 2026-04-03."
}
```

Fields that cannot be reliably determined are reported as `null` rather than guessed:
when no reliable prior holding can be linked, `previous_pct`, `delta_pp`, and
`purpose_changed` are `null` and `confidence` is lowered.

When the previous and current filings use different XBRL regimes, the delta is reported
arithmetically but flagged as not directly comparable:

```json
{
  "event_type": "change",
  "reporting_regime": "revised_2026",
  "cross_regime_comparable": false,
  "comparison_status": "not_directly_comparable",
  "delta_pp_note": "Arithmetic delta across reporting regimes/taxonomy versions; not a directly comparable holding change."
}
```

### Inputs

| field | type | notes |
|---|---|---|
| `from_date` | YYYY-MM-DD | Filing-date window start (inclusive). Defaults to 30 days ago. |
| `to_date` | YYYY-MM-DD | Filing-date window end (inclusive). Defaults to today. |
| `issuer_code` | string | Optional EDINET issuer-code filter. Matches the document-list `issuerEdinetCode` exactly (case-insensitive). Omit (or use `""`) for all issuers. |
| `limit` | int (1–1000) | **Maximum normalized events returned** (default 200). Transparent output cap: the full document scan of the requested window always completes; when the cap is hit, run metadata reports `complete=false`, `truncated=true`, `events_omitted=N`. |

**EDINET API access:** Authentication is handled by the Actor; users do not need to provide an EDINET API key.

### Billing (Pay-Per-Event)

- **Price: $0.10 per normalized ownership-change event** (`normalized-ownership-change-event`).
- You are charged only for events actually **emitted to the Dataset**. A run that emits
  no events costs $0.
- You are **not** charged per page fetched or per compute second; compute and dataset
  usage are covered by Apify platform costs.
- A per-run cost cap (`Run max cost`) is enforced. When the spending limit is reached the
  run stops cleanly and reports `spending_limit_reached=true`.

### Design principles

- **Deterministic.** Parsing, linkage, and delta are rule-based — no LLM in the
  critical path.
- **Fail-closed.** Unreliable or missing values are reported as `null` rather than
  guessed.
- **Source-traceable.** Every event carries `source_doc_id` back to the original EDINET
  filing.

### Practical limitations

- Coverage is limited to EDINET 大量保有報告書 / 変更報告書 / 訂正報告書
  (`formCode` + `docTypeCode` pairs). Other filing types are skipped.
- Historical previous-holding linkage requires a prior filing for the **same issuer +
  filer**; if none exists, `previous_pct` is `null`.
- Cross-regime (XBRL taxonomy) deltas are reported arithmetically but flagged as not
  directly comparable.
- No complete historical coverage is guaranteed beyond what EDINET discloses.

### Data source / attribution

Data is derived from **EDINET** — Japan's Financial Services Agency disclosure system —
large-shareholding filings. It is used under EDINET's terms of use. Retain attribution
to EDINET and the original filing (`source_doc_id`, and `source_url` when available) in
any redistribution.

# Actor input Schema

## `from_date` (type: `string`):

EDINET filing date lower bound. Defaults to 30 days ago.

## `to_date` (type: `string`):

EDINET filing date upper bound. Defaults to today.

## `issuer_code` (type: `string`):

Optional EDINET issuer-code filter. Matches the document-list metadata field issuerEdinetCode exactly (case-insensitive). Omit or use an empty string to include all issuers.

## `limit` (type: `integer`):

Maximum number of normalized ownership-change events returned in the Dataset. The full document scan of the requested window always completes; limit is a transparent OUTPUT cap. When it caps, run metadata reports complete=false, truncated=true, events\_omitted=N. Default 200.

## Actor input object example

```json
{
  "from_date": "2026-08-28",
  "to_date": "2026-08-28",
  "issuer_code": "",
  "limit": 1
}
```

# Actor output Schema

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

Each row is one normalized ownership-change event derived from an EDINET large-shareholding disclosure (大量保有報告書 / 変更報告書 / 訂正報告書).

# 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 = {
    "from_date": "2026-08-28",
    "to_date": "2026-08-28",
    "limit": 1
};

// Run the Actor and wait for it to finish
const run = await client.actor("w18notes.com/japan-edinet-ownership-change").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 = {
    "from_date": "2026-08-28",
    "to_date": "2026-08-28",
    "limit": 1,
}

# Run the Actor and wait for it to finish
run = client.actor("w18notes.com/japan-edinet-ownership-change").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 '{
  "from_date": "2026-08-28",
  "to_date": "2026-08-28",
  "limit": 1
}' |
apify call w18notes.com/japan-edinet-ownership-change --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,w18notes.com/japan-edinet-ownership-change"
        }
    }
}

```

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/hugQuI5vP2bJPiH3z/builds/6LF2GVF3howGdgFXX/openapi.json