/swiggy/collections

POST /api/swiggy/collections

Price: 1 credit

Get the restaurants in a Swiggy cuisine/dish collection by collection id at a location (latitude/longitude in India). Returns restaurant cards with name, rating, cuisines, cost for two, delivery time and offers.

How to use it

Get restaurants inside a Swiggy collection (e.g. Biryani=83639, Dosa=80424) at a location (lat/lng in India). Each result has id, url, name, image, rating, cuisines, cost_for_two, delivery_time, locality and offer.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• collection_id integer required — Swiggy collection id (examples: 83639, 80424; >: 0)
• lat number required — Latitude (India) (examples: 12.9351929; min: -90; max: 90)
• lng number required — Longitude (India) (examples: 77.6244807; min: -180; max: 180)
• count integer required — Max number of restaurants to return (min: 1)

Response

• @type string (default: "SwiggyRestaurantCard")
• id integer required
• url string required
• name string required
• image string nullable
• locality string nullable
• area 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")
• delivery_time integer nullable
• delivery_time_text string nullable
• distance_km number nullable
• is_open boolean (default: false)
• next_close_time string nullable
• parent_id string nullable
• is_promoted boolean (default: false)
• offer string nullable
• google_rating number nullable
• google_rating_count integer 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 — Collection not found or empty 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.