/petco/products/questions

POST /api/petco/products/questions

Price: 20 credits

Get customer questions about a Petco product with their answers, including brand answers and helpful votes

How to use it

Pass the product id from Petco search results, or a product URL. Each question carries its answers, so do not count answers as separate results.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Petco product id or product URL (examples: "5030043", "https://www.petco.com/product/taste-of-the-wild-pacific-stream-grain-free-dry-dog-food-with-smoked-salmon-28-lbs-2998871"; minLength: 1)
• count integer required — Max number of questions to return (min: 1)
• sort string — Question ordering (default: "newest"; one of: "newest", "oldest", "most_answers")
• has_answers boolean — Only questions with at least one answer when true (default: false)

Response

• @type string (default: "PetcoQuestion")
• id string required
• product_id string nullable
• text string nullable
• details string nullable
• author string nullable
• author_id string nullable
• author_location string nullable
• created_at integer nullable
• updated_at integer nullable
• answer_count integer nullable
• helpful_count integer nullable
• unhelpful_count integer nullable
• has_best_answer boolean nullable
• is_syndicated boolean nullable
• answers array (default: [])
  • @type string (default: "PetcoAnswer")
  • id string required
  • text string nullable
  • author string nullable
  • author_id string nullable
  • author_location string nullable
  • created_at integer nullable
  • updated_at integer nullable
  • helpful_count integer nullable
  • unhelpful_count integer nullable
  • is_brand_answer boolean nullable
  • is_best_answer boolean nullable
  • is_syndicated 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 Petco product has this id or URL. 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.