Yahoo! Auctions Japan Sold Price Summary & History

What it does: Returns a Yahoo! Auctions Japan sold-price summary from ended auctions with bids, with optional monthly history and individual auction rows.

You enter: Keywords, e.g. Leica M6; sample limits; optional monthly history and JPY price band.

You get: One summary per keyword: median, range, bid statistics and sample counts in JPY/USD. Optional monthly medians include direction and window coverage; auction rows include title, price, bids, condition, end time and URL.

Price: $0.02 per keyword with priced sold-auction data, including optional monthly history, plus $0.002 per returned auction. Individual rows are ON by default: 100 returned auctions plus one summary cost $0.22. Set includeIndividualItems: false for summaries only. Calculation-only history rows are not charged individually.

Example: For monthly camera-price research, use keywords: ["Leica M6"], includePriceTrend: true and includeIndividualItems: false. A nonempty keyword summary with monthly history costs $0.02; inspect priceTrend coverage before comparing months.

Unofficial — not affiliated with Yahoo! Auctions. Reads public pages only.

Choose the product for your job

Use this Actor for a price answer: a sold-price summary, optional monthly history, and optional supporting auction rows. Individual rows are ON by default for compatibility, adding $0.002 per returned auction to the $0.02 per-keyword summary. Set includeIndividualItems: false for summaries only. maxItemsPerKeyword accepts 30–1,000; monthly-history price bands keep their documented includePriceTrend requirement.

For a feed of individual rows from up to 2,000 live, ended or both auction rows per keyword with price bounds, choose Yahoo! Auctions Japan Listings Scraper — Bulk Data, at $0.0015 per row with no keyword fee. For known auction URLs, use Item Details by URL. The bulk feed is not a price summary; ended rows can include auctions without a sale.

Why closed auctions?

Yahoo! Auctions Japan (ヤフオク) exposes public ended-auction results for collectibles, retro games, camera gear, watches and trading cards. This Actor uses priced ended auctions with at least one bid for its sold-price benchmark. A closing bid is not independent payment verification. One keyword gives you:

• A price to work from before you buy or sell — the median and middle 50% range of source-listed closing prices
• A read on bidding activity — bid statistics describe the auctions in your sample
• A number you can compare abroad — every figure also comes in US dollars, so you can hold it against eBay or your local market
• A second opinion from Mercari — run our Mercari Japan Price Summary — Sold Out & Live on the same keyword to see the gap between the two sites

Choose the result for your job

Use this Actor for a sold-price benchmark and optional monthly history. Turn on includePriceTrend when you need the monthly medians; keep the same keyword, price band and sample settings across comparisons. It samples ended auctions and reports whether the requested history window was reached.

• For a larger live or ended auction feed, use Yahoo! Auctions Japan Listings Scraper — Bulk Data. It returns individual auctions rather than this price benchmark.
• For one known auction URL, use Yahoo! Auctions Item Details.
• For live listings below a sampled sold-price benchmark, use Yahoo! Auctions Underpriced Deals.

Each linked Actor has its own inputs, result limits and charges. Choose the result you need before saving a Task; changing this Actor's title does not change existing Task/API inputs.

Monthly sold-price history

For a new monthly-history workflow, use this Actor with includePriceTrend: true. For summaries without per-auction fees, also set includeIndividualItems: false. Monthly History — Legacy Task/API remains available for saved legacy inputs; its whole-sample statistics, coverage definition and trend-fee gate differ, so renaming old input fields is not a numerically or financially equivalent migration.

Turn on Add monthly sold-price history (includePriceTrend) to add a priceTrend object to each keyword summary. It contains each month's sold count and median, the first-to-last change, and a rising, falling or flat direction. Months with fewer than trendMinSoldPerMonth sales are shown but do not decide the direction.

The default combined sample cap is 300 ended auctions over six months. The collection cap is the larger of maxItemsPerKeyword and trendMaxItemsPerKeyword. Auctions beyond the main sample are calculation-only: they are not returned as individual rows or charged individually. windowCovered says whether newest-first paging reached an ended auction in or before the requested starting month, including auctions without bids or outside a local price band. It does not promise that the entire first month was read. Monthly counts and overall history prices include only the requested month window; they remain samples, including a partial current month.

Local price-band filtering and coverage

With monthly history enabled, priceMinJpy / priceMaxJpy filter the source-listed JPY price locally, with inclusive bounds. The Actor reads the allowed unfiltered closed-auction search pages using only the permitted p and b parameters; page width comes from each response, without a requested n or price-filter parameters. Only price-matching rows can enter the main summary, history statistics or returned individual auctions. Paging continues until the matching sample cap is reached, the observed source results end, or a page reaches an auction older than the requested first month. The existing run timeout still applies; sparse price bands can require more page reads than an unfiltered sample.

totalListingsFound is null for a locally filtered search that stops before all source results have been inspected. The source's unfiltered hit count is never presented as an exact price-filtered total. If the entire observed source result set is inspected, this field reports the counted matching auctions, including an exact zero when none match. In an unfiltered search, it keeps the source-reported total as before.

History sampledListings, soldTotal, monthly rows and overall prices describe matching rows inside the requested month window. oldestEndTime, newestEndTime and windowCovered describe the source time span actually inspected, even when the oldest inspected auction does not match the price band. budgetExhausted means the combined matching sample cap was filled; a false value alone does not establish complete source coverage. An empty partial sample does not prove that no matching sale exists outside the inspected range.

Input example

{
    "keywords": ["ポケモンカード リザードン psa10", "Leica M6"],
    "maxItemsPerKeyword": 100,
    "includePriceTrend": true,
    "trendMonthsBack": 6,
    "convertToUsd": true
}

Output

JSON results preserve nested price and optional history objects. The overview and CSV export also expose selected display fields and a months field containing monthly history. Keep JSON when your integration needs the full nested structure.

One price_summary record per keyword. Measured on 2026-08-17 (real run, keyword ポケモンカード リザードン psa10):

{
    "type": "price_summary",
    "keyword": "ポケモンカード リザードン psa10",
    "status": "closed_auctions",
    "keywordStatus": "ok",
    "totalListingsFound": 5452,
    "sampledListings": 100,
    "soldListings": 100,
    "priceJpy": { "min": 7500, "p25": 15000, "median": 41180, "p75": 124985, "max": 1500000, "average": 92033 },
    "compSpread": 8.33,
    "mixedKeywordLikely": true,
    "priceUsd": { "min": 47.11, "p25": 94.22, "median": 258.65, "p75": 785.03, "max": 9421.5, "average": 578.06 },
    "bidCountStats": { "min": 1, "p25": 1, "median": 1, "p75": 1, "max": 82, "average": 6 },
    "exchangeRateJpyUsd": 0.006281,
    "checkedAt": "2026-08-17T17:43:41.863658+00:00"
}

Plus (on by default) each sold auction, one row each, with title, final price (JPY + USD), bids, watch count, condition, category, whether it was a fixed-price listing, end time, photo, and a direct auctions.yahoo.co.jp URL.

What counts as sold. An ended auction with at least one bid. Ended auctions that got no bids are asking prices nobody accepted, and the summary never counts them. By default the individual rows are the sold ones only; turn off Individual results: sold only to get the unsold ended auctions as well (they are charged the same $0.002 each).

How wide the keyword is. compSpread is the middle 50% divided by itself (p75 ÷ p25), and mixedKeywordLikely is true above 4x — the same measure and the same ceiling as the optional monthly history and underpriced deals. One product sits near 1.5–3x. Above that, the keyword caught several kinds of thing and no single median describes them: measured 2026-08-18, camera returns 644,782 ended auctions at 9.45x, with a Surface Pro and a car door mirror on the first page, and even Nikon Z6 spans 38.48x. When you see true, use a fuller model name or a narrower keyword.

Which language to use. English generic words work: Yahoo maps them to Japanese, and camera and カメラ returned the identical 644,782 ended auctions on 2026-08-18 (guitar = ギター 132,855, gundam = ガンダム 436,536). Japanese spelling still gives the tightest match, and the spelling of a model number (α7 IV vs ILCE-7M4) is usually what decides whether a search hits at all.

When a keyword comes back empty

keywordStatus distinguishes the main sample from optional history. The keyword summary fee is not charged when neither contains priced sold auctions; optional returned unsold rows still have their declared individual-row charge:

keywordStatus	What it means	What to do
ok	Sold auctions were found	—
not_found	No ended auction matches the keyword and any selected local price band after source inspection	Try another spelling (α7 IV / ILCE-7M4), a broader keyword or a wider price band
history_only	No sold auction in the main sample, but the requested monthly history has sold prices	Read priceTrend; the $0.02 keyword fee applies, with no extra individual row for history-only auctions
no_sold_history	No priced sold auction in the sampled results, including history when requested	Try a broader keyword or a larger sampling budget

When the status is not ok, a hint field spells out the same next step in one sentence.

Pricing

$0.02 per keyword, plus $0.002 per individual ended-auction row returned. Individual auctions are on by default, so the 100-sold example above would come to $0.22; turn off Include individual auctions to pay the $0.02 only. The $0.02 keyword fee also applies when only the requested monthly history contains priced sold auctions (history_only). Auctions read only for history are never returned or billed as individual rows. A keyword with no priced sold auction in either the main sample or requested history is not charged. You pay per keyword; there is no monthly fee.

Price a whole list in one run

keywords takes a list — one item or a whole buying list. Each keyword returns its own summary at $0.02, plus the sold-auction rows at $0.002 each (on by default).

Measured on 2026-08-21 (real run): 25 camera keywords with Include individual auctions turned off → all 25 summaries in 160 seconds, $0.50.

The platform stops a run when it reaches its Maximum cost per run setting (default $3.00). With auction rows on, that comes fast: a 25-keyword camera list was stopped mid-run after 12 keywords (measured 2026-08-21). For long lists, turn the rows off, raise the ceiling in the run options, or split the list. The run's default time limit is 300 seconds.

Recheck the same product watchlist each week

Save a small buying or pricing watchlist as an Apify Task, then rerun the same searches each week. For example, start with these three camera models:

{
    "keywords": ["Leica M6", "Nikon D850", "Sony ILCE-7M4"],
    "maxItemsPerKeyword": 30,
    "soldOnly": true,
    "includeIndividualItems": true,
    "convertToUsd": true
}

These are example model names, not a promise of available sold auctions. Run once and inspect the titles before saving the list: accessories, bundles and condition differences can change the sample. If mixedKeywordLikely is true or the titles mix products, narrow that keyword first.

Cost for this example: at most 3 × ($0.02 + 30 × $0.002) = $0.24 in Actor result charges per run, including all three keyword summaries and up to 90 individual auction rows. With includeIndividualItems: false, the three summaries cost at most $0.06. Choose summaries only if you just need the median and range; keep individual rows when you need to inspect titles, condition and links. These estimates are before trial credits and exclude any applicable Apify platform charges. Keywords with no sold auctions incur no summary charge; actual cost depends on returned results.

1. Open this Actor in Apify Console and click Save as a new task. In the Task's Input tab, save the example JSON and give the Task a name such as weekly-camera-sold-prices. Set your timeout and Maximum cost per run under Run options, then click Start and check that each wanted keyword completed. See Apify's Task guide.
2. Once the test run gives you the data you need, open Schedules → Create new. In Schedule setup, choose a weekly time and your timezone; for example, Sunday at 09:00 in Asia/Tokyo. Use Add → Task to select your saved Task. Keep input overrides empty to reuse its configuration. Check Next runs, then enable the schedule. You can disable it whenever you want. See Apify's scheduling guide.
3. For each completed run, open its dataset and use Export to download JSON or CSV. Keep the run date or ID with the export so you can compare runs; JSON preserves the nested price statistics. See Apify's dataset export guide.

Compare like with like. Keep the same model spelling, sample limit and options across runs. Compare price_summary rows by keyword and checkedAt: start with priceJpy.median, priceJpy.p25, priceJpy.p75, sampledListings and soldListings. Inspect individual rows when the range widens, and treat a smaller sample as a reason to investigate. Compare JPY first; USD changes can also reflect the exchange rate.

Each checkedAt marks when that keyword was checked. The result is a snapshot of the first ended auctions returned by the source, up to your limit; it is not that week's sales total. Successive samples can overlap and can contain a different mix of auctions. If you change a keyword or sample limit, start a new comparison baseline. Export snapshots you want to keep before your account's data-retention period ends.

Use with AI agents

Connect your client to the Apify MCP server and identify this Actor as jpmarketdata/yahoo-auction-sold-comps. A concrete prompt keeps the chosen history, evidence and cost settings clear:

Use jpmarketdata/yahoo-auction-sold-comps to check Yahoo Auctions Japan sold prices and monthly history for Leica M6. Run with keywords: ["Leica M6"], maxItemsPerKeyword: 100, includePriceTrend: true, trendMonthsBack: 6, trendMaxItemsPerKeyword: 300, includeIndividualItems: false and convertToUsd: false. Report the JPY median and middle 50% range, main sample count, monthly sold counts/medians, windowCovered, budgetExhausted and checkedAt. Explain partial months and coverage limits. Treat ended auctions with bids as source results, not verified payments. Do not run other Actors or repeat the search unless I ask.

With individual rows off, this example costs at most $0.02 in keyword summary events, before trial credits and any applicable Apify platform charges. History-only auctions are calculation-only and incur no individual-row fee.

Fair use & data

• Reads only publicly visible ended-auction data — no login; no private account or payment records are accessed
• Requests are spaced out to keep the load on Yahoo! Auctions small
• Not affiliated with LY Corporation. Data is provided for market research; verify before large transactions

FAQ

How do I get Yahoo Auctions Japan sold prices?

Run this Actor with one or more model keywords. The sold-price summary uses priced ended auctions with at least one bid and returns the median, range, bid statistics and sample count. That is evidence of source-listed auction results, not independent verification that a buyer paid. Set includeIndividualItems: false when you only need the summary; individual rows are on by default and cost extra.

How do I get monthly Yahoo Auctions price history?

Set includePriceTrend: true and choose trendMonthsBack (2–12 months). Monthly history is included in the $0.02 keyword summary fee. Set includeIndividualItems: false to avoid optional auction-row charges. Read monthly sold counts, windowCovered, budgetExhausted and sample dates: missing or partial coverage is not a complete market history, and the current month can be partial.

Should I use the sold-price summary or the listings scraper?

Use this Actor for calculated medians, ranges and monthly history. Use the Yahoo! Auctions Japan Listings Scraper — Bulk Data for up to 2,000 raw live/ended auction rows per keyword at $0.0015 per delivered row. Raw ended results can include auctions without bids; they are not a ready-made sold-price benchmark.

Can I use the results in Python or a spreadsheet?

Yes. Run the Actor with Apify API or an Apify client and export results as JSON or CSV. JSON preserves the nested price and history objects. Keep each run ID and checkedAt so repeated samples can be compared with the same keyword, price band and sample settings.

If something goes wrong

• Wrong number or a failed run? Open a ticket on the Issues tab. I read every one and reply within 2 business days (Japan time).
• Source failures are reported. Read run logs and partial-result warnings; a successful run can contain fewer completed searches than requested. An acquisition failure is not proof of zero market matches.
• Summary and evidence have separate fees. No priced sold-auction data means no summary fee; optional returned unsold auction rows still cost $0.002 each.
• Checked every week. An automatic test runs this tool weekly; if the site changes, I fix it.
• Public pages only. No login. No private account or payment records are accessed.

More tools by the same author

• Yahoo! Auctions Japan Listings Scraper — Bulk Data
• Yahoo! Auctions Japan Monthly History — Legacy Task/API
• Yahoo! Auctions Japan Deals — Below Past Sold Prices
• Mercari Japan Price Summary — Sold Out & Live
• Daikokuya Japan Buyback — What a Shop Actually Paid
• Hifido Japan Used Audio — What It Actually Sold For
• Japan Used Camera & Lens — Dealer Price vs Sold Price
• Used iPhone & Android Prices Japan — Dealer vs Sold

All tools (Japan marketplaces, real estate, jobs, racing, prediction markets): https://apify.com/jpmarketdata

Disclaimer

Unofficial, independent tool — not affiliated with, endorsed by, or sponsored by Yahoo! Auctions. Product names and logos belong to their owners and only say where the data comes from. Data is read from public pages, for market research; check before you act on it.