Wolt restaurants and stores near a point

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

Restaurants and stores that Wolt lists for a point (30 countries), or the venues and dishes matching a search (q). Each venue: id, slug, name, link, description, address, country, coordinates, rating score, label and count, price range, currency, tags, product line, open and delivers flags, status, delivery estimate, delivery-fee promotions, badges, Wolt+ flag, preview items with prices, image and logo. Filters: cuisine, price range, open now, Wolt+, minimum rating, venue type; sorts: recommended, rating, delivery price, delivery time, distance. Without q, the response lists the area's cuisines. limit sets the page size; pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
latrequired number Latitude of the delivery point. Example: 60.1699
lonrequired number Longitude of the delivery point. Example: 24.9384
q string Search venues and dishes (e.g. sushi, pizza).
cuisine string Cuisine values, comma-separated (e.g. sushi, pizza, burgers, vegan; see available_filters). Example: sushi
price string Price range 1-4, comma-separated (1 = €).
sort string recommended (default), rating, delivery_price, delivery_time or distance. Example: rating
open_now boolean Only venues open now.
wolt_plus boolean Only Wolt+ venues.
min_rating number Minimum Wolt score (0-10).
type string restaurant, retail or grocery (stores).
limit integer Venues per page, 1-200 (default 50). Example: 50
page integer Page number (default 1). Example: 1

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

Example

curl "https://api.api.sh/wolt/v1/venues?lat=60.1699&lon=24.9384" \
  -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.