/gurunavi/restaurants

POST /api/gurunavi/restaurants

Price: 5 credits

Get full Gurunavi (楽天ぐるなび) restaurant details by id (e.g. 'g720500') or restaurant URL: name, address, geo, cuisines/genres, description, telephone/fax, price range and average budgets, access directions, opening hours, closed days, seats, banquet/charter capacity, payment methods, electronic money, amenities, private rooms, usage scenes, foreign language support, menu services (all-you-can-eat/drink, vegetarian, birthday perks), lunch services, Wi-Fi/power, parking, child-friendly facilities, pets, takeout, dress code, restrooms, other facilities, selling points, shop topics, cancellation policy, homepage and reservation links.

How to use it

Fetch a single Gurunavi (楽天ぐるなび) restaurant by id (e.g. 'g720500') or a full restaurant URL. Returns name, image/images, cuisines, genres, description, telephone, fax_number, address (street/locality/region/postal_code/country), latitude/longitude, price_range, budget_average, budget_banquet, access, open_hours, closed_days, is_reservable, payment_methods, electronic_money, service_charge, seats, banquet_max, charter_capacity, amenities, has_private_room, private_rooms, is_smoking_allowed, usage_scenes, foreign_languages, menu_services (all-you-can-eat/drink, vegetarian, birthday perks), lunch_services, wifi_power, parking, kids, pets, takeout, dress_code, restroom, other_facilities, issues_invoice, selling_points, topics, cancellation_policy, homepage_url, reserve_url and map_url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• restaurant string required — Gurunavi restaurant id (e.g. 'g720500') or a full restaurant URL (examples: "g720500", "https://r.gnavi.co.jp/g720500/"; minLength: 1)

Response

• @type string (default: "GurunaviRestaurant")
• id string required
• url string required
• name string nullable
• image string nullable
• images array (default: [])
• cuisines array (default: [])
• genres array (default: [])
• description string nullable
• telephone string nullable
• fax_number string nullable
• address object nullable
  • @type string (default: "GurunaviRestaurantAddress")
  • street string nullable
  • locality string nullable
  • region string nullable
  • postal_code string nullable
  • country string nullable
• latitude number nullable
• longitude number nullable
• price_range string nullable
• budget_average string nullable
• budget_banquet string nullable
• access string nullable
• open_hours string nullable
• closed_days array (default: [])
• is_reservable boolean nullable
• payment_methods array (default: [])
• electronic_money array (default: [])
• service_charge string nullable
• seats string nullable
• banquet_max string nullable
• charter_capacity string nullable
• amenities array (default: [])
• has_private_room boolean nullable
• private_rooms array (default: [])
• is_smoking_allowed boolean nullable
• usage_scenes array (default: [])
• foreign_languages array (default: [])
• menu_services array (default: [])
• lunch_services array (default: [])
• wifi_power array (default: [])
• parking string nullable
• kids array (default: [])
• pets string nullable
• takeout string nullable
• dress_code array (default: [])
• restroom array (default: [])
• other_facilities array (default: [])
• issues_invoice boolean nullable
• selling_points array (default: [])
• topics array (default: [])
• cancellation_policy string nullable
• homepage_url string nullable
• reserve_url string nullable
• map_url 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 — Restaurant not found (well-formed id but the restaurant page does not exist) 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.