/ubereats/stores

POST /api/ubereats/stores

Price: 10 credits

Get full Uber Eats (ubereats.com) store details by store URL, store id or store UUID: name, address, phone, rating, review count, cuisines, price range, opening hours, parent chain and the complete menu with categories, items, prices, descriptions, images and availability, plus recent customer reviews.

How to use it

Fetch a single Uber Eats (ubereats.com) store/restaurant by its store URL ('https://www.ubereats.com/store/{slug}/{id}'), the {id} from that URL, or the store UUID. Returns id, url, name, alias, image, images, phone, rating, review_count, price_range, currency, eta, is_open, is_orderable, city, city_slug, cuisines, chain (id, name), address (street, city, region, postcode, country, latitude, longitude), hours, category_count, item_count and the full menu as categories, each with items (name, description, price, image, is_available, is_sold_out, has_customizations), plus recent reviews (author, text, created_at).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• store string required — Uber Eats store as a full store URL, the store id from the URL, or the store UUID (examples: "https://www.ubereats.com/store/home-slice-pizza-s-congress/5y1hT9ipUYGYvIgY7A1N5A", "5y1hT9ipUYGYvIgY7A1N5A", "e72d614f-d8a9-5181-98bc-8818ec0d4de4"; minLength: 1)

Response

• @type string (default: "UbereatsStore")
• id string required
• url string required
• name string nullable
• alias string nullable
• image string nullable
• images array (default: [])
• phone string nullable
• rating number nullable
• review_count integer nullable
• price_range string nullable
• currency string nullable
• eta string nullable
• is_open boolean nullable
• is_orderable boolean nullable
• city string nullable
• city_slug string nullable
• cuisines array (default: [])
• chain object nullable
  • @type string (default: "UbereatsChain")
  • id string required
  • name string nullable
• address object nullable
  • @type string (default: "UbereatsStoreAddress")
  • address string nullable
  • street string nullable
  • city string nullable
  • region string nullable
  • postcode string nullable
  • country string nullable
  • latitude number nullable
  • longitude number nullable
• hours array (default: [])
  • @type string (default: "UbereatsHours")
  • day_range string nullable
  • ranges array (default: [])
• category_count integer (default: 0)
• item_count integer (default: 0)
• review_in_app_count integer (default: 0)
• menu array (default: [])
  • @type string (default: "UbereatsMenuCategory")
  • id string required
  • name string required
  • items array (default: [])
    • @type string (default: "UbereatsMenuItem")
    • id string required
    • name string required
    • description string nullable
    • price number nullable
    • image string nullable
    • is_available boolean (default: true)
    • is_sold_out boolean (default: false)
    • has_customizations boolean (default: false)
• reviews array (default: [])
  • @type string (default: "UbereatsReview")
  • id string required
  • author string nullable
  • text string nullable
  • created_at string nullable
  • time_since 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 — Store not found (well-formed id but no such store on Uber Eats) 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.