/xianyu/items/recommended

POST /api/xianyu/items/recommended

Price: 10 credits

List the listings Xianyu (Goofish) recommends on its home page to a visitor who is not signed in. Each row carries the item id and URL, the title, the asking price, the city, the want count, the free-shipping flag, the photos and the seller's masked nickname.

How to use it

This is a recommendation stream, so two calls return different listings and there is no keyword or category filter. Rows carry no seller id: take `id` to /xianyu/items for the full listing and its `seller.id`.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of listings to return (examples: 40; min: 1; max: 300)

Response

• @type string (default: "XianyuFeedItem")
• id string required
• url string nullable
• price number nullable
• original_price number nullable
• price_note string nullable
• currency string nullable
• city string nullable
• category_id string nullable
• want_count integer nullable
• is_free_shipping boolean nullable
• listed_at integer nullable
• place_name string nullable
• area_name string nullable
• division_code string nullable
• is_pickup_only boolean nullable
• last_sold_at integer nullable
• refreshed_at integer nullable
• origin_price number nullable
• origin_title string nullable
• origin_shop_name string nullable
• origin_purchase_date integer nullable
• image string nullable
• images array (default: [])
• video object nullable
  • @type string (default: "XianyuVideo")
  • id string required
  • url string nullable
  • url_320p string nullable
  • url_480p string nullable
  • image string nullable
  • width integer nullable
  • height integer nullable
• tags array (default: [])
• seller_name string nullable
• seller_image string 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 — The entity was not found, or a precondition failed 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.