# Japan New Company Registrations Feed (`bido_jp/japan-new-company-registrations`) Actor

- **URL**: https://apify.com/bido\_jp/japan-new-company-registrations.md
- **Developed by:** [Bido Tools](https://apify.com/bido_jp) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Japan New Company Registrations Feed

Get a clean, English-labelled list of **companies newly registered in Japan**, every business day, straight from the official National Tax Agency (NTA) Corporate Number data. About **400–550 new companies** are registered each business day (for example, 968 across 17–18 September 2026).

The Actor can also track **name changes, address changes, closures, restorations and mergers** of any Japanese corporation.

### Who is it for?

- **Sales and business development teams**: reach newly founded Japanese companies before your competitors do. New companies need banking, accounting, office space, SaaS, recruiting and insurance.
- **KYC, compliance and credit teams**: watch for closures, mergers and address or name changes.
- **Market researchers and investors**: count company formations by prefecture and legal form.
- **Data teams outside Japan**: get Japanese registry data without reading Japanese-only government pages or handling Shift\_JIS files.

### Why use this Actor?

- **Official source**: the data comes from the NTA Corporate Number Publication Site. This Actor does not scrape third-party websites.
- **English labels**: each record includes English labels for its change type, legal form (for example, Kabushiki Kaisha or Godo Kaisha (LLC)), prefecture and closure reason.
- **Search-friendly names**: `nameNormalized` converts full-width letters, digits and spaces to their normal ASCII forms (`ＲｅｓｉＬｉＮＸ` → `ResiLiNX`). `nameRomaji` gives a best-effort Hepburn reading.
- **Filters**: filter by change type, prefecture, legal form and date window. Corrections to old records are excluded by default, so "new" means genuinely new.
- **Fast and cheap**: one day of data takes only a few seconds to process.

### Tip: run it daily

Create an [Apify Schedule](https://docs.apify.com/platform/schedules) that runs every weekday morning (Japan time) with the default input. Each run returns the most recent day's new companies. You can connect the dataset to Google Sheets, Slack, email, Make, Zapier or a webhook with Apify integrations.

### Input

By default, the Actor returns only newly registered companies from the most recently published day. The following example returns new companies, name changes and address changes in Tokyo and Osaka for the last 5 published days:

```json
{
  "changeTypes": ["new", "name_change", "address_change"],
  "daysBack": 5,
  "prefectures": ["Tokyo", "27"],
  "companyKinds": ["stock_company", "llc"],
  "includeCorrections": false,
  "maxItems": 0
}
```

| Field | Description |
|---|---|
| `changeTypes` | Any of `new`, `name_change`, `address_change`, `closed`, `restored`, `merger`, `other`. Default: `["new"]`. |
| `daysBack` | The number of most recent published days to fetch (1–40). |
| `dateFrom` / `dateTo` | An inclusive `YYYY-MM-DD` range. If `dateFrom` is set, `daysBack` is ignored. |
| `prefectures` | English prefecture names (`Tokyo`, `Osaka`, …) or two-digit codes (`13`, `27`, …). |
| `companyKinds` | Any of `stock_company`, `llc`, `foreign_company`, `other`. |
| `includeCorrections` | Set to `true` to also include corrections to earlier records. |
| `maxItems` | The maximum number of items to return. `0` means unlimited. |

### Output

One item is returned for each registry event. Empty values are `null`, and dates are ISO strings. Example:

```json
{
  "corporateNumber": "1010003052706",
  "changeType": "new",
  "changeTypeLabel": "New",
  "processCode": "01",
  "isCorrection": false,
  "updateDate": "2026-09-17",
  "changeDate": "2026-09-17",
  "assignmentDate": "2026-09-17",
  "nameJa": "プラスエナジー合同会社",
  "nameNormalized": "プラスエナジー合同会社",
  "nameKana": "プラスエナジー",
  "nameRomaji": "Purasuenaji",
  "nameEn": null,
  "companyKind": "llc",
  "companyKindLabel": "Godo Kaisha (LLC)",
  "prefectureJa": "東京都",
  "prefectureEn": "Tokyo",
  "prefectureCode": "13",
  "cityJa": "千代田区",
  "cityEn": null,
  "streetJa": "永田町２丁目１１番１号山王パークタワー５階トラスティーズ・コンサルティングＬＬＰ内",
  "postalCode": "100-0014",
  "addressJa": "東京都千代田区永田町２丁目１１番１号山王パークタワー５階トラスティーズ・コンサルティングＬＬＰ内",
  "addressNormalized": "東京都千代田区永田町2丁目11番1号山王パークタワー5階トラスティーズ・コンサルティングLLP内",
  "addressOverseas": null,
  "closeDate": null,
  "closeCauseLabel": null,
  "successorCorporateNumber": null,
  "hidden": false,
  "nta_url": "https://www.houjin-bangou.nta.go.jp/henkorireki-johoto.html?selHouzinNo=1010003052706",
  "source": "Source: National Tax Agency Corporate Number Publication Site (processed by this Actor)"
}
```

### Pricing

You pay per result: each dataset item is one charged event. Because the default input returns only the latest day's new companies, a typical daily run returns a few hundred items.

### Data freshness and limitations

- The NTA publishes diff files on Japanese business days. There are no files for weekends or public holidays.
- The source page offers roughly the latest 40 business days. Older history is not available through this Actor.
- The registry contains legal data only (name, address, legal form, dates). It does not include phone numbers, emails, representatives or capital.
- English names and English city names appear only when the company registered them with the NTA, which is rare for new companies.
- `nameRomaji` is generated from the official katakana reading. It is approximate, has no word breaks, and is not an official transliteration.
- Rows that the NTA marks as partially hidden remain in the dataset with `hidden: true`.

### Attribution

Data from the National Tax Agency (NTA) under the Public Data License 1.0 (公共データ利用規約 第1.0版), processed and edited by this Actor. This Actor is not affiliated with or endorsed by the NTA.

# Actor input Schema

## `changeTypes` (type: `array`):

Registration events to include.

## `daysBack` (type: `integer`):

Number of most recent published business days. Ignored when dateFrom is set.

## `dateFrom` (type: `string`):

Inclusive start date. Must be available on the NTA list page.

## `dateTo` (type: `string`):

Inclusive end date. Must be available on the NTA list page.

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

Filter by English prefecture name (for example Tokyo) or two-digit code.

## `companyKinds` (type: `array`):

Filter by broad registered-corporation kind.

## `includeCorrections` (type: `boolean`):

Include correction records for earlier registrations.

## `maxItems` (type: `integer`):

Maximum records to store. Set to 0 for unlimited.

## Actor input object example

```json
{
  "changeTypes": [
    "new"
  ],
  "daysBack": 1,
  "includeCorrections": false,
  "maxItems": 0
}
```

# Actor output Schema

## `overview` (type: `string`):

Key fields of each registry event in a table.

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

Every field of each registry event (JSON, CSV or Excel via the dataset API).

# 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("bido_jp/japan-new-company-registrations").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("bido_jp/japan-new-company-registrations").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 bido_jp/japan-new-company-registrations --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bido_jp/japan-new-company-registrations"
        }
    }
}
```

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/LyK3ymzhnSUh5q0oD/builds/z20J44LU8BdJI67vt/openapi.json