Japan New Companies & Corporate Changes API

A machine-readable Japan Corporate Events Feed built from the National Tax Agency's official Corporate Number daily differential data.

This Actor is not a general corporate-registry lookup wrapper. It answers one question:

What changed in Japan's company universe?

Use it to retrieve a daily feed of newly published company registrations, name changes, address changes, and closures.

The underlying corporate change can predate the day it appears in the NTA feed.

Productized corporate signals

Event	NTA process	What it means
NEW_COMPANY	01	Newly published corporate number
NAME_CHANGE	11	Company / organization name changed
ADDRESS_CHANGE	12	Domestic principal-office address changed
CLOSED	21	Registry closed / dissolution-related closure

Other official process codes can optionally be returned as OTHER, but the default product surface is intentionally limited to these four signals.

Why use an event feed instead of a registry API?

Registry lookup APIs are useful when you already know which company you want to inspect.

This Actor is designed for the opposite workflow:

1. A company event happens.
2. The NTA later publishes or updates it in a daily differential file.
3. The Actor preserves the underlying change date and adds the feed-file date.
4. The Actor normalizes the record into a stable event object.
5. Your automation, database, sales workflow, or monitoring system consumes the event.

Typical downstream uses include:

• Detect newly published companies for B2B prospecting workflows
• Detect headquarters or address changes for data hygiene
• Detect name changes for CRM and master-data maintenance
• Detect closures for suppression and risk-review workflows
• Build scheduled Japan company-change datasets without parsing NTA CSV files yourself

Example input

{
  "date": "",
  "eventTypes": [
    "NEW_COMPANY",
    "ADDRESS_CHANGE"
  ],
  "prefectures": [
    "東京都"
  ],
  "includeCorrections": false,
  "maxItems": 10
}

Leave date empty to use the newest Unicode CSV daily differential file available on the NTA download page.

Leave prefectures empty to retrieve events from all Japan.

The Actor follows the NTA site's official tokenized POST download flow; no NTA Web API application ID is required.

Example event

{
  "event_id": "3a2f24cb9608d695ce42",
  "event_type": "NEW_COMPANY",
  "event_date": "2026-08-21",
  "feed_date": "2026-08-21",
  "updated_at": "2026-08-21",
  "process_code": "01",
  "corporate_number": "1234567890123",
  "name": "Example株式会社",
  "prefecture": "東京都",
  "city": "千代田区",
  "address": "東京都千代田区丸の内1丁目",
  "postal_code": "1000005",
  "is_correction": false,
  "source": "National Tax Agency Corporate Number Publication Site (Japan)",
  "source_url": "https://www.houjin-bangou.nta.go.jp/download/sabun/"
}

event_id is deterministic and is intended to make downstream deduplication easier.

Date semantics

The feed deliberately exposes three separate dates:

• event_date — the underlying corporate change date reported by the NTA record
• feed_date — the NTA daily differential-file date from which this Actor retrieved the record
• updated_at — the NTA record's updateDate

These dates can differ.

For example, an address change can have:

event_date = 2026-07-23
feed_date  = 2026-08-21

Therefore, this Actor is a feed of newly published corporate events.

It does not claim that every underlying change occurred on the feed date.

Filters

date

Optional YYYY-MM-DD file date.

Leave blank to automatically use the latest available daily differential file.

eventTypes

The standard feed supports:

[
  "NEW_COMPANY",
  "NAME_CHANGE",
  "ADDRESS_CHANGE",
  "CLOSED"
]

NEW is also accepted as a backward-compatible alias for NEW_COMPANY.

prefectures

Filter by one or more Japanese prefectures.

Examples:

東京都
大阪府
福岡県

Leave empty to return events from all Japan.

includeCorrections

Default: false

NTA correction records can replay historical records for an affected corporation.

If treated as fresh events, these corrections can create false newly-published signals. Correction rows are therefore excluded from the standard event feed by default.

includeOther

Default: false

Enable this only if you need official NTA process codes outside the four standard event types.

Additional supported records are returned with event_type set to OTHER.

maxItems

Maximum number of corporate-event records to return.

The Store form starts with a small number of events so you can inspect the output before increasing the limit for larger runs.

Output

Results are stored in the default Apify dataset and can be consumed as:

• JSON
• CSV
• Excel
• Apify API output
• Downstream Apify integrations

Each corporate event is normalized into a consistent object containing fields such as:

• event_id
• event_type
• event_date
• feed_date
• updated_at
• process_code
• corporate_number
• name
• prefecture
• city
• address
• postal_code
• is_correction
• source
• source_url

The run summary is stored under the SUMMARY record and includes:

• Feed / source-file date
• Source URL
• Total event count
• Counts by event type
• Selected filters
• Whether PPE charging was active

Data source

Source: National Tax Agency Corporate Number Publication Site (Japan)

The official daily differential data contains newly assigned corporate-number records and newly published or updated change records, including names, domestic addresses, and registry closures.

The NTA provides recent differential files as ZIP archives in CSV and XML formats.

This Actor is an independent transformation and normalization tool and is not an official National Tax Agency service.

Verify important information against the official source.