POST /api/yahoo/auctions/items
Price: 20 credits
Get full Yahoo! Auctions Japan (Yahoo!オークション) listing details by auction id or URL, for both live and completed auctions: current or winning price, start price, buy-it-now price, bid and bidder counts, watch count, start and end time, item condition, category path, brand, description, photo gallery, shipping terms and methods, accepted payment methods, question counts, highest bidders and the seller profile with rating.
Fetch a single Yahoo! Auctions Japan listing by auction id (e.g. 'd1236130164') or a full auction URL. Works for live auctions (status 'open', price = current bid) and finished ones (status 'closed', price = the winning bid). Returns name, price, start_price, buy_now_price, bid_count, bidder_count, watch_count, quantity, start_at/end_at (unix seconds), condition and condition_name, category and category_path, brand, description and description_html, image/images, shipping_paid_by ('seller' or 'winner'), shipping_schedule, shipping_methods, accepts_credit_card/accepts_paypay/accepts_bank_transfer, answered_question_count, highest_bidders and seller. price, buy_now_price and start_price include consumption tax (tax_rate is the percentage applied).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)item string required — Yahoo! Auctions Japan auction id or a full auction URL (examples: "d1236130164", "https://page.auctions.yahoo.co.jp/jp/auction/d1236130164"; minLength: 1)@type string (default: "YahooAuctionsItem")id string requiredurl string requiredname string requiredstatus string nullableprice integer nullablestart_price integer nullablebuy_now_price integer nullabletax_rate integer nullablebid_count integer nullablebidder_count integer nullablewatch_count integer nullablequantity integer nullablestart_at integer nullableend_at integer nullablecondition string nullablecondition_name string nullablecategory object nullable@type string (default: "YahooAuctionsCategoryRef")id string requiredname string requiredcategory_path array (default: [])@type string (default: "YahooAuctionsCategoryRef")id string requiredname string requiredbrand object nullable@type string (default: "YahooAuctionsCategoryRef")id string requiredname string requiredmarketplace string nullabledescription string nullabledescription_html string nullableimage string nullableimages array (default: [])shipping_paid_by string nullableshipping_schedule string nullableshipping_methods array (default: [])is_worldwide_delivery boolean nullableis_anonymous_delivery boolean nullableis_automatic_extension boolean nullableis_early_closing boolean nullableis_offer_accepted boolean nullableis_returnable boolean nullablereturn_policy string nullableaccepts_credit_card boolean nullableaccepts_paypay boolean nullableaccepts_bank_transfer boolean nullableanswered_question_count integer nullableunanswered_question_count integer nullablehighest_bidders array (default: [])@type string (default: "YahooAuctionsBidder")display_name string requiredrating_count integer nullableseller object nullable@type string (default: "YahooAuctionsSeller")id string requiredurl string requireddisplay_name string nullableimage string nullablerating_count integer nullablegood_rating number nullableis_store boolean nullableis_best_store boolean nullableis_excellent_seller boolean nullableis_verified boolean nullableis_speed_shipping boolean nullableregion string nullableregion_code integer nullableprofile_message string nullablestore_licenses array (default: [])@type string (default: "YahooAuctionsStoreLicense")name string requiredcode string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Auction not found (well-formed id but no such auction on Yahoo! Auctions Japan) Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.