/doordash/stores/search

POST /api/doordash/stores/search

Price: 5 credits

Find DoorDash (doordash.com) restaurants and stores delivering in a US city, optionally filtered by cuisine. Returns store cards with name, rating, review count, price range, cuisines, address, delivery ETA, distance, delivery fee, current offers, popular items and recent review snippets.

How to use it

Find DoorDash (doordash.com) restaurants in a US city. Provide city, state (two-letter code) and count. Optional cuisine filter (American, Italian, Chinese, Pizza, Sushi, Mexican, ...). Each result has id, name, url, image, rating, rating_count, price_range (1-4), cuisines, address, eta (minutes), distance, delivery_fee, offers (promotions), popular_items (name, price, image) and recent review snippets. Use a store id or url with the stores endpoint for the full menu and reviews.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city string required — City name (examples: "New York", "Los Angeles"; minLength: 1)
• state string required — Two-letter US state code (examples: "NY", "CA"; minLength: 2; maxLength: 2)
• count integer required — Max number of stores to return (min: 1; max: 50)
• cuisine string nullable — Filter by cuisine (one of: "African", "American", "Arabic", "Argentinian", "Asian", "Australian", "Bakery", "BBQ", "Boba", "Brazilian", "Breakfast", "Brunch", "Bubble-Tea", "Burgers", "Cafe", "Caribbean", "Cheesesteak", "Chicken", "Chinese", "Coffee", "Colombian", "Comfort-Food", "Crab", "Cuban", "Deli", "Dessert", "Dim-Sum", "Ethiopian", "FastFood", "Filipino", "French", "Greek", "Gyro", "Halal", "Hawaiian", "Healthy", "Indian", "Italian", "Japanese", "Korean", "Latin-American", "Malaysian", "Mediterranean", "Mexican", "Middle-Eastern", "Noodles", "Pakistani", "Peruvian", "Pho", "Pizza", "Poke", "Ramen", "Salads", "Sandwiches", "Seafood", "Smoothie", "Soul-Food", "Soup", "Southern", "Spanish", "Steak", "Sushi", "Tacos", "Tapas", "Thai", "Vegan", "Vegetarian", "Vietnamese", "Wings", "Wraps")

Response

• @type string (default: "DoordashStoreCard")
• id string required
• name string required
• url string nullable
• image string nullable
• rating number nullable
• rating_count integer nullable
• rating_count_display string nullable
• price_range integer nullable
• cuisines array (default: [])
• address object nullable
  • @type string (default: "DoordashAddress")
  • street string nullable
  • city string nullable
  • state string nullable
  • display_address string nullable
  • country_code string nullable
  • latitude number nullable
  • longitude number nullable
• eta integer nullable
• distance string nullable
• delivery_fee number nullable
• service_fee number nullable
• delivery_fee_text string nullable
• offers_pickup boolean (default: false)
• offers array (default: [])
• popular_items array (default: [])
  • @type string (default: "DoordashCardItem")
  • id string required
  • name string nullable
  • description string nullable
  • price number nullable
  • image string nullable
  • calories integer nullable
• reviews array (default: [])
  • @type string (default: "DoordashCardReview")
  • text string nullable
  • rating integer nullable
  • date string nullable
  • source string nullable
  • reviewer string 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.