/ubereats/stores/search

POST /api/ubereats/stores/search

Price: 10 credits

Search Uber Eats (ubereats.com) stores near a delivery location by keyword and filters (cuisine/dish keyword, sort, minimum rating, price tier, delivery fee, delivery time, offers). Returns store cards with id, url, name, rating, review count, delivery ETA and current offer.

How to use it

Search Uber Eats (ubereats.com) stores near a latitude/longitude. Optional free-text 'query' (dish, cuisine or store name) and filters: sort (recommended/rating/delivery_time), min_rating (3..5), price ($..$$$$), max_delivery_fee, under_30_min, best_overall, offers, benefits_eligible, snap. Returns store cards (id, url, name, alias, image, rating, review_count, eta, is_orderable, offer). Use ubereats/stores with a returned id/url to fetch the full store details and menu.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• latitude number required — Delivery location latitude (min: -90; max: 90)
• longitude number required — Delivery location longitude (min: -180; max: 180)
• query string required — Search keyword (dish, cuisine or store name) (minLength: 1)
• count integer required — Max number of stores to return (min: 1)
• sort string nullable — Result ordering (one of: "recommended", "rating", "delivery_time")
• min_rating string nullable — Only stores at or above this star rating (one of: "3", "3.5", "4", "4.5", "5")
• price array — Keep only stores in these price tiers (default: []; one of: "$", "$$", "$$$", "$$$$")
• max_delivery_fee string nullable — Only stores at or below this delivery fee (one of: "$1", "$3", "$5", "$5+")
• under_30_min boolean — Only stores delivering in under 30 minutes (default: false)
• best_overall boolean — Only top-rated 'Best overall' stores from Uber Eats (default: false)
• offers boolean — Only stores currently running offers/deals (default: false)
• benefits_eligible boolean — Only stores eligible for member benefits (default: false)
• snap boolean — Only stores accepting SNAP/EBT (default: false)

Response

• @type string (default: "UbereatsStoreCard")
• id string required
• url string required
• name string nullable
• alias string nullable
• image string nullable
• rating number nullable
• review_count integer nullable
• eta string nullable
• is_orderable boolean nullable
• offer 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.