/kijiji/sellers/reviews

POST /api/kijiji/sellers/reviews

Price: 1 credit

Get the reviews left for a Kijiji seller by seller ID (or profile URL): star score, whether the reviewer was the buyer or the seller, the deal category, the reviewed listing and the feedback tags.

How to use it

Fetch the public reputation reviews of one Kijiji (Canada) seller. Each review has score (1-5 stars), reviewer_id, reviewer_role (buyer or seller, i.e. which side of the deal the reviewer was on), listing_id, category_name, created_at (unix seconds) and feedback: the tags picked by the reviewer such as Quick responses, Friendly, Fair negotiation, Item as described. A seller who exists but has never been reviewed returns an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — Kijiji seller ID (numeric, or COMMERCIAL_<id> for a dealer) or a seller profile URL (examples: "1134072"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• locale string — Language of localized labels (default: "en"; one of: "en", "fr")

Response

• @type string (default: "KijijiSellerReview")
• id string required
• score integer nullable
• reviewer_id string nullable
• reviewer_role string nullable
• seller_id string nullable
• listing_id string nullable
• category_name string nullable
• created_at integer nullable
• feedback 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 — Seller not found (well-formed but nonexistent seller ID) 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.