Tabelog restaurant profile

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

One Tabelog restaurant: id, name, link, genres, rating, review count, price range, address (Japanese), locality, region, postal code, coordinates, phone and reservation phone, reservation notes, transportation, business hours and closed days, dinner and lunch budgets and the budget from reviews, payment methods, seats, maximum party, private rooms and private use, smoking, parking, facilities, set menus, drinks, food, occasions, location, services, family policy, dress code, website, opening day, remarks, image, breadcrumbs and every detail row as shown.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
urlrequired string The restaurant's tabelog.com link (English or Japanese edition), from /tabelog/v1/search. Example: https://tabelog.com/en/tokyo/A1301/A130103/13292459/

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

Example

curl "https://api.api.sh/tabelog/v1/restaurant?url=https%3A%2F%2Ftabelog.com%2Fen%2Ftokyo%2FA1301%2FA130103%2F13292459%2F" \
  -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.