/danawa/products

POST /api/danawa/products

Price: 5 credits

Get a Danawa (다나와) product by code or URL: name, model, images, maker, brand, category path and codes, spec summary, certification code, release month, rating, review count, number of mall offers, lowest price, launch price and the product codes of the variant group

How to use it

Find product codes with danawa/products/search. Mall offers, price history and user opinions are separate calls taking the same code.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Danawa product code or product URL (examples: "124012178", "https://prod.danawa.com/info/?pcode=124012178")

Response

• @type string (default: "DanawaProduct")
• id string required
• url string required
• name string nullable
• model string nullable
• image string nullable
• images array (default: [])
• maker_code string nullable
• maker_name string nullable
• maker_url string nullable
• brand_name string nullable
• category_group string nullable
• category_path string nullable
• category_codes object nullable
  • @type string (default: "DanawaCategoryCodes")
  • ui_code string nullable
  • code_1 string nullable
  • code_2 string nullable
  • code_3 string nullable
  • code_4 string nullable
• specs string nullable
• certification_code string nullable
• release_month string nullable
• registered_date integer nullable
• rating number nullable
• review_count integer nullable
• offer_count integer nullable
• currency string nullable
• lowest_price number nullable
• launch_price number nullable
• variant_product_ids array (default: [])

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 — Danawa has no product under that 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.