/snapdeal/products/questions

POST /api/snapdeal/products/questions

Price: 1 credit

Get customer questions and answers for a Snapdeal product by product id (or product URL): question text, author, date, answer count, votes, and the answers for each question.

How to use it

Fetch the customer Q&A for a single Snapdeal product by product id or a product URL. Optional sort (score/recent). Returns a list of questions, each with text, author, date, created_at, answer_count, upvote_count, score and answers (each answer with text, author, date, created_at, upvote_count). Many products have no questions yet (empty list).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Snapdeal product id or a product URL containing it (examples: "620423338553", "https://www.snapdeal.com/product/action-running-shoes/620423338553"; minLength: 1)
• count integer required — Max number of questions to return (min: 1)
• sort string — Question ordering (default: "score"; one of: "score", "recent")

Response

• @type string (default: "SnapdealQuestion")
• id string required
• text string nullable
• author string nullable
• date string nullable
• created_at integer nullable
• answer_count integer nullable
• upvote_count integer nullable
• score integer nullable
• answers array (default: [])
  • @type string (default: "SnapdealAnswer")
  • id string required
  • text string nullable
  • author string nullable
  • date string nullable
  • created_at integer nullable
  • upvote_count integer 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.