POST /api/doordash/stores
Price: 5 credits
Get full DoorDash (doordash.com) store/restaurant details by store id (or store URL): name, description, price range, rating and review count, address, phone, website, cuisines, delivery fee, ETA, opening hours, the complete menu with categories, items, prices, dietary tags and item ratings, plus a review summary (star breakdown) and recent customer reviews.
Fetch a single DoorDash (doordash.com) store by id (e.g. '19906') or a full store URL. Returns id, name, description, price_range (1-4), rating, rating_count, address (street/city/state/lat/lng), phone, website, cuisines, offers_delivery/pickup, is_dashpass_partner, delivery_fee_text, delivery_minutes, asap_minutes, hours, the full menu as categories each with items (name, description, price, strikethrough_price, image, like_percent, rating_count, dietary_tags, badges), review_summary (average_rating, stars_breakdown) and recent reviews (reviewer, rating, text, created_at, items).
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 full store URL (examples: "19906", "https://www.doordash.com/store/katzs-delicatessen-new-york-19906/"; minLength: 1)@type string (default: "DoordashStore")id string requiredname string requireddescription string nullableprice_range integer nullableprice_range_display string nullablerating number nullablerating_count integer nullablerating_count_display string nullablecurrency string nullabletimezone string nullablestore_bio string nullableimage string nullablebanner string nullablephone string nullablewebsite string nullablebusiness_id string nullablebusiness_name string nullablecuisines array (default: [])is_open boolean nullableoffers_delivery boolean (default: false)offers_pickup boolean (default: false)is_dashpass_partner boolean (default: false)delivery_fee_text string nullabledelivery_minutes string nullablepickup_minutes string nullableasap_minutes integer nullablephoto_count_text string nullableaddress object nullable@type string (default: "DoordashAddress")street string nullablecity string nullablestate string nullabledisplay_address string nullablecountry_code string nullablelatitude number nullablelongitude number nullablehours array (default: [])@type string (default: "DoordashHours")day string requiredslots array (default: [])category_count integer (default: 0)item_count integer (default: 0)categories array (default: [])@type string (default: "DoordashMenuCategory")id string requiredname string requireddescription string nullableitems array (default: [])@type string (default: "DoordashMenuItem")id string requiredname string requireddescription string nullableprice number nullablestrikethrough_price number nullableimage string nullablerating_display string nullablelike_percent integer nullablerating_count integer nullableserving_size string nullabledietary_tags array (default: [])badges array (default: [])review_summary object nullable@type string (default: "DoordashReviewSummary")average_rating number nullablerating_count integer nullablereview_count integer nullablestars_breakdown array (default: [])@type string (default: "DoordashStarBucket")stars integer requiredrating_count integer (default: 0)reviews array (default: [])@type string (default: "DoordashReview")id string requiredreviewer string nullablerating integer nullabletext string nullablecreated_at string nullableis_verified boolean (default: false)source string nullableitems array (default: [])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 — Store not found (well-formed id but no such store on DoorDash) 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.