/momo/products

POST /api/momo/products

Price: 10 credits

Get a momo product: name, prices, images, brand, category path, specification table, variants with stock, payment and delivery options, promotions, shop, rating and review count

How to use it

Prices are in TWD. Find goods codes with momo/products/search; reviews are on momo/products/reviews.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — momo goods code or product URL (examples: "13108055", "TP00021310000596", "https://www.momoshop.com.tw/goods/GoodsDetail.jsp?i_code=13108055")

Response

• @type string (default: "MomoProduct")
• id string required
• name string nullable
• url string nullable
• subtitle string nullable
• price number nullable
• price_max number nullable
• price_label string nullable
• promo_price number nullable
• list_price number nullable
• images array (default: [])
• brand_name string nullable
• brand_id string nullable
• category_ids array (default: [])
• category_names array (default: [])
• vendor_code string nullable
• shop_name string nullable
• shop_rating number nullable
• shop_product_count integer nullable
• rating number nullable
• review_count integer nullable
• rating_breakdown object (default: {})
  • * number
• specifications array (default: [])
  • @type string (default: "MomoSpecification")
  • name string required
  • value string nullable
• features array (default: [])
• certification string nullable
• warranty string nullable
• payment_methods array (default: [])
• delivery_options array (default: [])
  • @type string (default: "MomoDeliveryOption")
  • name string required
  • code string nullable
  • fee_note string nullable
• shipping_note string nullable
• variant_title string nullable
• variants array (default: [])
  • @type string (default: "MomoVariant")
  • code string required
  • name string nullable
  • second_name string nullable
  • price number nullable
  • stock_quantity integer nullable
  • image string nullable
  • shipping_note string nullable
• promotions array (default: [])
  • @type string (default: "MomoPromotion")
  • label string nullable
  • summary string nullable
  • tiers array (default: [])
  • period string nullable
• labels array (default: [])
• total_sales_text string nullable
• purchase_limit integer nullable
• sale_start_text string nullable
• video_urls array (default: [])
• description_url string nullable
• return_policy string nullable
• rank_title string nullable
• rank_text string nullable
• has_gift boolean nullable
• is_adult boolean 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 — No momo product under that goods code 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.