Uber Eats store with its full menu

GET https://api.api.sh/ubereats/v1/store
1 credit / call food & delivery try it in the playground →

One Uber Eats store: id, name, link, phone, full address with coordinates and neighbourhood, rating, rating score and count, price bucket, cuisines, labels and tags, currency, open and orderable flags, working-hours line, delivery fee, service fee, ETA, distance, dining modes, opening hours per day range, badges, parent chain, images, the menus with their hours and every menu category with its items (id, name, description, price, sold-out and availability flags, has-options flag, endorsement badges, dietary labels, image, section ids for /ubereats/v1/item) and featured reviews. Fees and ETA are for the delivery point when lat/lon or address is given. Each menu item also has the share of customers who liked it and on how many reviews (liked_percent, liked_reviews), calories where the menu shows them, and its tags (e.g. #1 most liked).

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
url string The store's ubereats.com/store/<name>/<id> link (from /ubereats/v1/stores). Example: https://www.ubereats.com/store/joes-pizza-times-square-1435-broadway/F9A-B2bKRg-ikAd0B8uzgg
id string The store's UUID instead of url.
lat number Latitude of the delivery point, for fees and ETA (with lon).
lon number Longitude of the delivery point (with lat).
address string Delivery address instead of lat/lon.
dining_mode string delivery (default) or pickup.
locale string Language and market of the texts, e.g. en-US, en-GB, fr-FR, es-MX (default en-US).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/ubereats/v1/store?url=https%3A%2F%2Fwww.ubereats.com%2Fstore%2Fjoes-pizza-times-square-1435-broadway%2FF9A-B2bKRg-ikAd0B8uzgg" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.