/citilink/products/qa

POST /api/citilink/products/qa

Price: 5 credits

List the question-and-answer thread of one citilink.ru product: the text of each message, when it was posted, the author nickname with the expert and verified-buyer flags, the like and dislike counts, and the parent message that ties an answer to its question.

How to use it

Questions and answers arrive in one flat list, not nested: follow `parent_id` to pair them, and treat `is_answer` as the quick discriminator. Answers written by Citilink staff carry `is_expert`, which is what separates a merchant statement about the product from a shopper's guess. `count` counts messages, so a thread of ten questions with replies needs roughly twenty.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city string — Citilink city code that the returned prices, stock and delivery belong to. Codes come from citilink/cities; the response echoes the resolved city back in `city` (default: "msk_cl"; examples: "msk_cl", "kzn_cl", "nvs_cl", "abn_cl:5x0050435"; minLength: 1)
• product string required — Citilink product page URL or the product code printed on the page as 'Код товара' (examples: "2019135", "M00300851", "https://www.citilink.ru/product/noutbuk-digma-pro-fortis-m-i5-1235u-16gb-ssd512gb-2019135/"; minLength: 1)
• count integer required — Max number of questions and answers to return (min: 1)
• sort string — Thread ordering (default: "new"; one of: "new", "likes")

Response

• @type string (default: "CitilinkQuestion")
• id string required
• product_id string required
• parent_id string nullable
• depth integer nullable
• is_answer boolean nullable
• text string nullable
• created_at string nullable
• updated_at string nullable
• author string nullable
• author_id string nullable
• is_expert boolean nullable
• is_buyer boolean nullable
• is_best boolean nullable
• is_marked_helpful boolean nullable
• status string nullable
• likes integer nullable
• dislikes integer nullable
• url string nullable

Errors

• 422 — Unknown city code — take one from citilink/cities. 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 such product on citilink.ru, or the product has no discussion container. 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.