# Bit Japan Court Auction Properties and Details Scraper (`realestateapi/bit-japan-court-auction-properties-and-details-scraper`) Actor

Collects public property records from the official Japanese BIT court-auction database: case numbers, addresses, property types, areas, sale-standard and guarantee amounts, bid deadlines, and public three-point-set PDF links.

- **URL**: https://apify.com/realestateapi/bit-japan-court-auction-properties-and-details-scraper.md
- **Developed by:** [Real Estate API](https://apify.com/realestateapi) (community)
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Bit Japan Court Auction Properties and Details Scraper

This Actor reads the public Japanese Courts **BIT 不動産競売物件情報サイト** search pages and emits normalized auction-property listings. It supports the nine BIT blocks, the public court-region identifiers used by BIT (including the four Hokkaido district-court regions), property-category filters, case numbers, addresses, property types, areas, sale-standard/guarantee amounts, bid windows, coordinates, and the public three-point-set PDF link.

### Source and method

- Public source: https://www.bit.courts.go.jp/app/top/pt001/h01
- Search help: https://www.bit.courts.go.jp/help/help01/help01_02.html
- Three-point-set explanation: https://www.bit.courts.go.jp/words/sa-so/sa05.html
- The Actor follows the same public form flow as the site: block → region → all public listings. It maintains only the session cookies returned by the public site.
- `includePdfLinks` requests the public BIT PDF preparation endpoint and returns its link; it does not download or store PDF bytes.

### Inputs

- `blockIds`: BIT block IDs `01`–`09`; default `all`.
- `prefectureIds`: optional BIT region/court-region IDs such as `91`, `13`, or `40`; empty means all regions in the selected blocks.
- `courtIds`: optional court IDs to retain after the regional result pages are parsed.
- `saleTypes`: `1` land, `2` detached house, `3` condominium, `4` other.
- `maxRecords`: global unique-listing cap, default 50.
- `includePdfLinks`: create three-point-set PDF links, default true.
- `includeRawFields`: retain bounded hidden BIT result fields, default false.
- `timeoutSeconds`: per-request timeout, default 30.

The site’s public result fields are returned as source-backed values. A listing can contain a generic `areaSqM` because BIT’s result page exposes the area appropriate to that property category; the raw field `areaText` is retained when present. The Actor does not log in, submit bids, access private contact information, download PDF files, use a proxy, or call Apify cloud APIs.

### Local development

```bash
npm ci
apify validate-schema
apify run --input '{"prefectureIds":["91"],"maxRecords":5,"includePdfLinks":true}'
npm test
```

The Actor entrypoint is `src/main.js`; transport, BIT form handling, HTML parsing, normalization, and crawling are separate modules.

### Dependency maintenance

See [SECURITY_DEPENDENCIES.md](SECURITY_DEPENDENCIES.md) for the locked dependency remediation, the cache-disabled policy replacement, and offline regression coverage. Source permission/access prerequisites remain unchanged.

# Actor input Schema

## `blockIds` (type: `array`):

BIT block identifiers 01-09. Leave as all to cover every block.

## `prefectureIds` (type: `array`):

Optional BIT region/court identifiers such as 91 (Sapporo), 13 (Tokyo), or 40 (Fukuoka). Empty means all public court regions.

## `courtIds` (type: `array`):

Optional court IDs to retain after public region searches. Empty means all courts returned by the selected regions.

## `saleTypes` (type: `array`):

BIT sale category codes: 1 land, 2 detached house, 3 condominium, 4 other.

## `maxRecords` (type: `integer`):

Maximum unique auction listings to emit across the selected public regions.

## `includePdfLinks` (type: `boolean`):

Request the public BIT three-point-set PDF link for each emitted listing. PDF bytes are not downloaded.

## `includeRawFields` (type: `boolean`):

Keep the bounded hidden result fields returned by BIT alongside normalized values.

## `timeoutSeconds` (type: `integer`):

Timeout applied to each official BIT request.

## Actor input object example

```json
{
  "blockIds": [
    "all"
  ],
  "prefectureIds": [],
  "courtIds": [],
  "saleTypes": [
    "1",
    "2",
    "3",
    "4"
  ],
  "maxRecords": 50,
  "includePdfLinks": true,
  "includeRawFields": false,
  "timeoutSeconds": 30
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `outputSummary` (type: `string`):

No description

## `sourceMetadata` (type: `string`):

No description

# 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("realestateapi/bit-japan-court-auction-properties-and-details-scraper").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("realestateapi/bit-japan-court-auction-properties-and-details-scraper").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 realestateapi/bit-japan-court-auction-properties-and-details-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,realestateapi/bit-japan-court-auction-properties-and-details-scraper"
        }
    }
}
```

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/jHiPpnMeI61eyeWyE/builds/MjQd398NZnjTrzJWY/openapi.json