MICHELIN Guide restaurants in a city or country

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

Restaurants of the MICHELIN Guide for a country, region or city, optionally only some distinctions (three, two or one star, Bib Gourmand, selected, Green Star), 48 per page: id, name, link, stars, distinction, Green Star flag, location, city, region, country, price band, cuisine, coordinates, hotel, online-booking flag and image, with the total. Also filter by cuisine, price band and restaurants new in this year's Guide; the answer echoes them as applied_filters. Pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
location string Country/region/city path as in the Guide's links: fr, fr/ile-de-france/paris, gb/greater-london/london, us/new-york-state/new-york, jp/tokyo-region/tokyo, it, es/comunidad-de-madrid/madrid... Example: fr/ile-de-france/paris
url string A guide.michelin.com/<lang>/<location>/restaurants link instead of location.
distinction string Comma-separated: 3-stars, 2-stars, 1-star, bib-gourmand, selected, green-star. Example: 3-stars,2-stars
cuisine string The Guide's cuisine slugs, comma separated (up to 5): modern-cuisine, creative, classic-cuisine, japanese, italian, seafood-1096, vegetarian... An unknown slug answers 400.
price string Price bands, comma separated: affordable, mid-range, premium, luxury (or 1-4).
new boolean true: only restaurants new in this year's Guide.
language string Language of the texts: en (default), fr, de, es, it, ja, zh...
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/michelin/v1/restaurants?location=fr%2File-de-france%2Fparis" \
  -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.