POST /api/doordash/stores/reviews
Price: 20 credits
Get the full DoorDash (doordash.com) customer review history of a store by store id (or store/reviews URL): each review's star rating, full text and marked-up text, reviewer, tagged menu items with prices, photos, helpful-vote count, verified flag and review date. This is the complete review feed, beyond the few recent reviews the store endpoint returns.
List a DoorDash store's customer reviews, identified by store id (e.g. '420033') or a store or reviews URL. Each review carries num_stars, the review_text and marked_up_review_text, the reviewer and their reviewed items with prices, any photos, the helpful-vote count, a verified flag and the review date. Reviews come only from delivered orders, so a store holds tens of reviews and one call with a high count returns the whole set. doordash/stores returns only the few most recent reviews of a store.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)store string required — DoorDash store id, or a store or reviews URL containing it (examples: "420033", "https://www.doordash.com/store/420033/", "https://www.doordash.com/reviews/store/420033/"; minLength: 1)count integer required — Max number of reviews to return (min: 1)@type string (default: "DoordashStoreReview")consumer_review_uuid string nullableorder_uuid string nullabledelivery_uuid string nullablestore_id string nullablereview_text string nullablemarked_up_review_text string nullablenum_stars integer nullablequality_rating number nullablequality_rating_v2 number nullablerating_tag string nullablereviewer_display_name string nullablereviewer_id string nullablereviewer_data object nullable@type string (default: "DoordashStoreReviewReviewer")id string nullabledisplay_name string nullabledescription string nullablestatus_icon string nullableprofile_image_url string nullableprofile_url string nullablereviewed_at string nullableorder_submitted_at string nullableitems array (default: [])@type string (default: "DoordashStoreReviewItem")id string nullablename string nullableprice number nullabledisplay_price string nullableimage string nullablevote string nullableorderability object nullable@type string (default: "DoordashItemOrderability")orderable boolean nullablereason string nullablemenu_id string nullablecategory_id string nullabletagged_items array (default: [])@type string (default: "DoordashStoreReviewItem")id string nullablename string nullableprice number nullabledisplay_price string nullableimage string nullablevote string nullableorderability object nullable@type string (default: "DoordashItemOrderability")orderable boolean nullablereason string nullablemenu_id string nullablecategory_id string nullablereview_photos array (default: [])@type string (default: "DoordashStoreReviewPhoto")id string nullableurl string nullablecreated_at string nullablesubtitle string nullabletagged_items array (default: [])@type string (default: "DoordashPhotoTaggedItem")id string nullablename string nullableprice number nullabledisplay_price string nullableimage string nullablecategory string nullablereviewer_data object nullable@type string (default: "DoordashStoreReviewReviewer")id string nullabledisplay_name string nullabledescription string nullablestatus_icon string nullableprofile_image_url string nullableprofile_url string nullablephoto_count_display_string string nullablehelpful_count integer nullablemarked_helpful boolean nullableis_verified boolean nullablemoderation_status string nullablefull_review_url string nullable422 — store is not a valid DoorDash store id or URL 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.