/paypayfleamarket/items

POST /api/paypayfleamarket/items

Price: 1 credit

Get a full Yahoo!フリマ (formerly PayPay フリマ) listing by its id or URL: asking price in yen, sale status, declared item condition, title and description, the whole photo gallery, view and like counts, how many buyers asked a question, requested a discount or made an offer, the four-level category path, brands, the linked product catalogue entry, the JAN barcode, hashtags, item specifications, shipping method, parcel size and dispatch window, the IMEI of a listed phone, the prefecture the item ships from, and the seller with their rating, verification status and trading record. Sold listings also carry when they sold and how long they took to sell.

How to use it

Fetch a single Yahoo!フリマ / PayPay フリマ listing by id (e.g. 'z650615796') or a full listing URL. Prices are always in Japanese yen. Returns name, description, price, status (open/sold/...), condition (new/like_new/no_visible_damage/slight_damage/damaged) with the original Japanese wording in condition_name, image/images, view_count, like_count, question_count, discount_count, offer_count, created_at/opened_at/updated_at (unix seconds), category and category_path (four levels, Japanese names), product_category, brands, catalog_id and product_url of the matching product page, jancodes, hashtags, specs, delivery_method/delivery_schedule and their Japanese labels, delivery_size (parcel size in cm for bulky items), imei (published for listed phones), location (shipping prefecture code) with location_name in Japanese, and seller. A sold listing also carries sold_at (unix seconds), sold_in_minutes (how long it stayed on sale), sold_in_label (the same span in Japanese) and is_fast_sale; these are null while the listing is still on sale. Seller nicknames are published masked by the source. Use paypayfleamarket/items/search to find listing ids.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• item string required — Yahoo!フリマ listing id or a full listing URL (examples: "z650615796", "1238594996", "https://paypayfleamarket.yahoo.co.jp/item/z650615796"; minLength: 1)

Response

• @type string (default: "PaypayfleamarketItem")
• id string required
• url string required
• name string required
• description string nullable
• price number nullable
• status string nullable
• condition string nullable
• condition_name string nullable
• image string nullable
• images array (default: [])
• view_count integer nullable
• like_count integer nullable
• question_count integer nullable
• discount_count integer nullable
• offer_count integer nullable
• created_at integer nullable
• opened_at integer nullable
• updated_at integer nullable
• sold_at integer nullable
• sold_in_minutes integer nullable
• sold_in_label string nullable
• is_fast_sale boolean nullable
• category object nullable
  • @type string (default: "PaypayfleamarketCategoryRef")
  • id integer required
  • name string required
• category_path array (default: [])
  • @type string (default: "PaypayfleamarketCategoryRef")
  • id integer required
  • name string required
• category_url string nullable
• product_category object nullable
  • @type string (default: "PaypayfleamarketCategoryRef")
  • id integer required
  • name string required
• brands array (default: [])
  • @type string (default: "PaypayfleamarketBrand")
  • id integer required
  • name string required
  • name_kana string nullable
  • name_english string nullable
  • has_children boolean nullable
• catalog_id string nullable
• product_url string nullable
• jancodes array (default: [])
• price_compare_url string nullable
• hashtags array (default: [])
• specs array (default: [])
  • @type string (default: "PaypayfleamarketItemSpec")
  • id integer nullable
  • name string nullable
  • values array (default: [])
• delivery_method string nullable
• delivery_method_name string nullable
• delivery_size string nullable
• delivery_schedule string nullable
• delivery_schedule_name string nullable
• imei string nullable
• location string nullable
• location_name string nullable
• item_type string nullable
• is_no_price_item boolean nullable
• is_first_submit boolean nullable
• is_free_shipping_campaign boolean nullable
• is_web_purchase_only boolean nullable
• is_flat_price boolean nullable
• is_inspecting boolean nullable
• is_bulk_purchase_requestable boolean nullable
• count_down_campaign_expires_at integer nullable
• seller object nullable
  • @type string (default: "PaypayfleamarketUser")
  • id string required
  • url string required
  • nickname string nullable
  • image string nullable
  • rating_count integer nullable
  • good_ratio number nullable
  • is_deleted boolean nullable
  • is_kyc_completed boolean nullable
  • is_trusted boolean nullable
  • is_gold boolean nullable
  • ship_badge_level string nullable
  • trading_record_label string nullable
  • trading_record_level integer nullable
  • external_trading_record_level integer nullable
  • follower_count integer nullable
  • followee_count integer nullable

Errors

• 422 — 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 — Listing not found (well-formed id but no such listing on Yahoo!フリマ) 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.