Yahoo! Auctions Japan Item Details by URL

Look up known public Yahoo! Auctions Japan items by exact URL. Unofficial and not affiliated with Yahoo! Auctions. An AI agent can ask whether a known auction has a buy-now price, how many bids and watchers it has, who pays shipping, and whether the end time can extend.

Input

Supply 1–20 itemUrls, each exactly https://auctions.yahoo.co.jp/jp/auction/<id> without query or fragment. Duplicates are removed before requests. No keyword search.

Repeat the same auction watchlist

Save the exact itemUrls as an Apify Task and run that Task on your chosen schedule, or start it with POST /v2/actor-tasks/<TASK_ID>/runs. Wait for the run to finish before reading its default dataset through GET /v2/datasets/<DATASET_ID>/items?format=json&clean=true. Keep the run ID with each import.

For available auctions, append history by auctionId and observedAt; use (runId, auctionId) to make importing the same run again safe. In a mixed run with at least one available detail, retain each unavailable URL's separate status using requestedAuctionId and checkedAt, with (runId, requestedAuctionId) as the import key. If every URL is unavailable, the run fails with not-found before publishing rows; keep the previous snapshot and inspect the failure. A missing or unavailable item does not prove that it sold, and closed does not prove payment. Compare bid, buy-now, bid count and end time only for the same ID, keeping the observation timestamp.

Choose this Actor when the auction URLs are already known. Use Bulk Listings — Live or Ended to discover auctions by keyword, or Sold Price Summary & Monthly History for market-level price comparisons.

Output

One auction_detail row per available ID, with exact ID and URL, status, displayed and raw source prices, buy-now price where validated, bid/bidder/watch counts, condition, start/end times, shipping payer, dispatch lead time, automatic extension, early closing and observation time. A live current bid is a floor, not a guaranteed purchase price; closed does not prove paid sale. The displayed price is taken from the page offer, because a store item can have a different raw internal price. In a mixed run with at least one available detail, unavailable items have an uncharged item_status row with requestedAuctionId, requestedUrl, itemStatus=unavailable and checkedAt. If all URLs are unavailable, the run fails with not-found before publishing rows. Upstream failure is never an empty success.

The default Auction details table shows buy-now price and dispatch lead time when the page supplies validated values. The separate Unavailable auction URLs table shows the uncharged status rows.

Pricing

$0.003 per delivered auction_detail; no start fee and no charge for duplicate/unavailable/error rows. Maximum 20 charged rows = $0.06, subject to run maximum cost and trial settings.

Limits

Maximum 20 item pages plus one robots request, at least 1.5 seconds between Yahoo requests, 30-second request timeout and 120-second run budget. No login, browser, paid API, redirects outside the exact host, search, seller pages or robots-disallowed paths. Source and DC egress may change; the run fails on auth block, rate limit, upstream HTTP 5xx, timeout or page-structure mismatch, with those causes reported separately.

Privacy

Only a bounded allowlist of product/auction facts is exported. Explicit contact handles in a seller-written title, such as LINE ID: ..., are replaced with [contact removed]. Seller identities, bidder identities, descriptions, images, questions, contacts, location, account/cookie data and raw HTML/JSON are excluded.