/swiggy/restaurants

POST /api/swiggy/restaurants

Price: 10 credits

Get full Swiggy restaurant details by numeric id or restaurant URL (latitude/longitude in India): name, cuisines, rating, cost for two, full address, geo coordinates, phone, delivery time, opening hours, FSSAI license, offers and serviceability.

How to use it

Fetch a single Swiggy restaurant by numeric id (e.g. '966182') or a full restaurant URL (lat/lng in India required). Returns id, name, cuisines, rating, rating_count, cost_for_two, address, locality, city, latitude/longitude, phone, delivery_time, opening_hours, license_no, offers, restaurant_category and serviceability.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• restaurant string required — Restaurant numeric id or a full restaurant URL (examples: "966182", "https://www.swiggy.com/city/bangalore/blue-tokai-coffee-roasters-rest966182"; minLength: 1)
• lat number required — Latitude (India) (examples: 12.9351929; min: -90; max: 90)
• lng number required — Longitude (India) (examples: 77.6244807; min: -180; max: 180)

Response

• @type string (default: "SwiggyRestaurant")
• id integer required
• url string required
• name string required
• alias string nullable
• image string nullable
• cuisines array (default: [])
• rating number nullable
• rating_count integer nullable
• cost_for_two number nullable
• cost_for_two_text string nullable
• currency string (default: "INR")
• address string nullable
• locality string nullable
• area string nullable
• city string nullable
• state string nullable
• postal_code string nullable
• latitude number nullable
• longitude number nullable
• phone string nullable
• delivery_time integer nullable
• min_delivery_time integer nullable
• max_delivery_time integer nullable
• delivery_time_text string nullable
• distance_km number nullable
• serviceability string nullable
• is_open boolean (default: false)
• next_close_time string nullable
• parent_id string nullable
• restaurant_category string nullable
• is_multi_outlet boolean (default: false)
• has_bestseller_items boolean (default: false)
• license_no string nullable
• timing_status string nullable
• timing_message string nullable
• opening_hours array (default: [])
  • @type string (default: "SwiggyOpeningHours")
  • day string required
  • hours string nullable
• offers array (default: [])

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 (valid id but no restaurant at this location) 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.