# Yahoo Auctions Japan Sold Prices (ヤフオク落札相場) (`jpopendata/japan-yahoo-auction-sold`) Actor

Sold-item prices (落札相場) from Yahoo Auctions Japan closed search: title, sold price JPY, bid count, end time, condition, category — English schema for resale comps and price research. Item facts only, no seller data. Unofficial; not affiliated with LY Corporation.

- **URL**: https://apify.com/jpopendata/japan-yahoo-auction-sold.md
- **Developed by:** [JP Open Data](https://apify.com/jpopendata) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 per records

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

## Yahoo Auctions Japan Sold Prices (ヤフオク落札相場)

**Sold-item comps from Yahoo! Auctions Japan (ヤフオク!) — what items actually sold for: title, final price in JPY, bid count, end time, condition and category, in a clean English schema.**

This Actor searches the public closed-auction (sold items, 落札相場) listings on auctions.yahoo.co.jp by keyword — optionally narrowed by category — and returns each sold item as English-schema JSON: item title, sold price (JPY), buy-now price when the listing had one, bid count, end timestamp (ISO 8601), condition (new/used plus the site's condition grade code), category path and id, thumbnail image URL, item URL, fixed-price vs auction flag, flea-market flag, and watch count. Optional price-range and condition filters and end-time/price sorting are applied client-side.

Yahoo! Auctions is Japan's largest auction marketplace and its sold-price history is the reference price database for Japanese collectibles, cameras, trading cards, figures, watches and electronics — but it is Japanese-only and invisible to most international tooling. This Actor is the bridge for price research, resale comps and authenticity/market analysis.

> **Unofficial tool.** Not affiliated with or endorsed by LY Corporation (LINEヤフー株式会社) or Yahoo! Auctions (ヤフオク!). It collects **publicly available data only** (no login, no paywall), politely (strictly serial requests, ≥1.2 s apart, hard per-run budget, no block evasion), fetches **only URLs the site's robots.txt allows**, and extracts **item facts only** — **no seller information of any kind** (no seller IDs, names, ratings or locations), no personal data (relevant e.g. under GDPR: no personal data is collected or processed). Users are responsible for ensuring their own use of the data complies with the source site's terms and applicable law.

***

### Who is this for?

- **Resellers & arbitrage** — real sold prices (not asking prices) for anything traded in Japan: trading cards, figures, retro games, camera gear, watches, denim.
- **Overseas collectors & proxy-buying services** — know the fair market price in Japan before bidding or quoting; Zenmarket/Buyee-style flows need exactly this data.
- **Authenticity & market research** — price distributions, bid activity and condition mix per item family; spot outliers and fakes by price.
- **Data teams** — a stable English schema over a Japanese-only source, with an analysis-ready shape (numeric prices, ISO timestamps, coarse + detailed condition).

### Sample output (dataset item)

```json
{
  "itemTitle": "ポケモンカード コイキング AR 080/073 ポケカ",
  "soldPriceJpy": 7645,
  "buyNowPriceJpy": null,
  "bidCount": 20,
  "endedAt": "2026-08-25T21:58:28+09:00",
  "condition": "used",
  "conditionDetail": "USED60",
  "categoryPath": ["おもちゃ、ゲーム", "ゲーム", "トレーディングカードゲーム", "ポケモンカードゲーム", "シングルカード"],
  "categoryId": 2084317608,
  "imageUrl": "https://auc-pctr.c.yimg.jp/i/auctions.c.yimg.jp/images.auctions.yahoo.co.jp/image/...",
  "itemUrl": "https://page.auctions.yahoo.co.jp/jp/auction/j1241577860",
  "isFixedPrice": false,
  "isFleaMarket": false,
  "watchCount": 43,
  "source": "ヤフオク! 落札相場 (auctions.yahoo.co.jp closed search)",
  "sourceUrl": "https://auctions.yahoo.co.jp/",
  "license": "Publicly available data — unofficial tool; users are responsible for compliance with the source site's terms",
  "retrievedAt": "2026-08-25T13:12:44.000Z"
}
```

`condition` is `new` / `used`; `conditionDetail` is the site's grade code (`NEW`, or `USED10`…`USED80` — lower number = better condition). `isFixedPrice` separates buy-it-now listings from true auctions; `bidCount` and `watchCount` signal demand.

### Input example

```json
{
  "keyword": "ポケモンカード",
  "priceMin": 1000,
  "priceMax": 50000,
  "condition": "used",
  "sortBy": "price",
  "maxItems": 100
}
```

`keyword` is required (Japanese keywords match best). `category` takes a numeric Yahoo Auctions category id (the `auccat` value in category URLs). Price range, condition and sorting are applied **client-side after fetching** — the equivalent URL parameters are disallowed by the site's robots.txt, and this Actor strictly requests only robots-allowed URLs. Tight filters therefore discard part of what was fetched; raise `maxApiRequests` if a filtered run comes back incomplete.

### Pricing

Pay per result — see the pricing tab. One upstream page holds 50 sold items.

### FAQ

**Where does the data come from?**
Live from the public, login-free closed-auction search (落札相場) pages on auctions.yahoo.co.jp at run time. Every record embeds the source, source URL, a license note, and the retrieval timestamp.

**Is this an official Yahoo! / LY Corporation service?**
No. **Unofficial**, independently built and maintained, and **not affiliated with or endorsed by LY Corporation.** It reads only publicly available pages. (Yahoo's official auction API was discontinued in 2018; no API route exists.)

**Is seller information included?**
No — deliberately and verifiably not. Seller IDs, display names, ratings, store flags and item location are **never extracted** (the test suite asserts recursively that no seller-derived value can appear in any output field). Sold-price analysis needs the item and the price, not the person.

**Does it respect robots.txt?**
Yes, strictly. The closed-search page this Actor uses (`/closedsearch/closedsearch`) is expressly **allowed** by the site's robots.txt; several filter URL-parameters are disallowed there, so this Actor never sends them and applies those filters client-side instead.

**Who is responsible for how the data is used?**
You are. The Actor collects publicly available factual data politely, but the legality of your specific use (redistribution, database rights, the source site's terms) is your responsibility as the user.

**How fresh and complete are the results?**
Sold listings are what the site's closed search returns at retrieval time, most recently ended first (the site retains roughly the last 180 days of sold items). Treat each run as a snapshot; re-run for fresh comps.

**What about server load?**
Strictly serial requests, ≥1.2 s apart, 50 items per request, hard per-run request budget (max 60), exponential backoff, no CAPTCHA/login/block evasion. If the site changes its page format, the Actor stops with a clear error instead of silently mis-parsing; if it blocks persistently, the run fails visibly.

### Search terms this Actor answers

yahoo auction japan sold prices · yahoo auctions japan scraper · japan auction comps · yahoo auction price history · yauction sold listings · ヤフオク 落札相場 データ · japan collectibles resale data · pokemon card sold prices japan · japan camera lens sold prices · yahoo japan auction closed search · japanese auction market data · resale price research japan

### More Japan data Actors by the same developer

- **Japan Government Tenders & Awards** — tender notices and award results from the kkj.go.jp portal.
- **Japan Medical Facilities** — every registered hospital, clinic, dental clinic, and pharmacy (MHLW open data).
- **Japan Care Facilities** — long-term care providers across 35 service types (MHLW open data, CC BY).
- **Japan Government Subsidies & Grants** — open subsidy calls from the official jGrants API.
- **Japan Renewable Energy FIT/FIP Facilities** — METI-certified renewable installations, privacy-safe schema.
- **Japan Financial Licenses & Registrations** — FSA-licensed banks, securities firms, crypto exchanges and more.
- **Japan Construction & Real-Estate Licenses** — licensed contractors and brokers from MLIT's official register.
- **Japan Trade Statistics** — monthly import/export flows by HS code and partner country, from Japan Customs.
- **Japan Hotels & Ryokan Prices (jalan.net)** — hotel/ryokan prices, plans and ratings by prefecture and area.
- **Japan Hobby & Collectibles Prices (駿河屋 Suruga-ya)** — new/used/marketplace asking prices from suruga-ya.jp; the perfect companion to compare current asking prices against these sold comps.
- **Yahoo Flea Market Japan Prices (Yahoo!フリマ / PayPayフリマ)** — live asking prices from paypayfleamarket.yahoo.co.jp; the fixed-price flea-market side of the same LY commerce ecosystem, ideal for comparing current listings against these sold comps.

***

*Unofficial tool; not affiliated with LY Corporation. Publicly available data only; users are responsible for compliance with the source site's terms and applicable law. No personal data and no seller data are collected.*

# Actor input Schema

## `keyword` (type: `string`):

REQUIRED. Search keyword for sold (closed) items, e.g. "ポケモンカード", "Nikon F3", "ガンプラ". Japanese keywords match best.

## `category` (type: `string`):

Optional numeric Yahoo Auctions category id to narrow the search (the auccat value in auctions.yahoo.co.jp category URLs), e.g. 2084241343 = ポケモンカードゲーム. Leave empty to search all categories.

## `priceMin` (type: `integer`):

Optional lower bound on the sold price in JPY. Applied client-side after fetching (the equivalent URL parameter is disallowed by the site's robots.txt), so tight ranges may need a higher request budget.

## `priceMax` (type: `integer`):

Optional upper bound on the sold price in JPY. Applied client-side after fetching.

## `condition` (type: `string`):

Filter by item condition. Applied client-side after fetching.

## `sortBy` (type: `string`):

endTime = most recently ended first (the source's native order). price = highest sold price first. Sorting is applied client-side to the collected records.

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

Stop after this many dataset records.

## `maxApiRequests` (type: `integer`):

Hard budget of HTTP requests to auctions.yahoo.co.jp for this run (one request = one 50-item result page). Requests are strictly serial with >= 1.2 s spacing. When the budget runs out the run completes with complete=false in RUN\_SUMMARY.

## `proxyConfiguration` (type: `object`):

Apify proxy settings. Default: no proxy. Never used for rotation/evasion — one client identity per run.

## Actor input object example

```json
{
  "keyword": "ポケモンカード",
  "category": "2084241343",
  "priceMin": 1000,
  "priceMax": 50000,
  "condition": "any",
  "sortBy": "endTime",
  "maxItems": 10,
  "maxApiRequests": 10
}
```

# Actor output Schema

## `records` (type: `string`):

Structured sold-item (落札) records with source attribution (source, sourceUrl, license, retrievedAt) on every item.

# 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 = {
    "keyword": "フィギュア",
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpopendata/japan-yahoo-auction-sold").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 = {
    "keyword": "フィギュア",
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("jpopendata/japan-yahoo-auction-sold").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 '{
  "keyword": "フィギュア",
  "maxItems": 10
}' |
apify call jpopendata/japan-yahoo-auction-sold --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpopendata/japan-yahoo-auction-sold"
        }
    }
}

```

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/plh7PtOciuGq1vtha/builds/aofPovdPij7VRBzyI/openapi.json