/swiggy/dishes/search

POST /api/swiggy/dishes/search

Price: 20 credits

Search Swiggy dishes by keyword near a location (latitude/longitude in India). Filter by veg/non-veg, rating and price range; sort by relevance, rating or price. Each result is a dish (name, price, image, veg marker, variants, add-ons, rating) with its restaurant.

How to use it

Search Swiggy dishes by keyword (e.g. 'pizza', 'biryani') at a location (lat/lng in India). Filters: veg (veg/non_veg), rating_4_plus, price (under_100/rs_100_to_250/rs_251_to_500/rs_500_plus). Sort: relevance, rating, price_low_to_high, price_high_to_low. Each result has dish (id, name, price, final_price, is_veg, image, rating, variants, addons) and restaurant (id, name, url, image, rating, google_rating, cuisines, area, cost_for_two, delivery_time).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lat number required — Latitude (India) (examples: 12.9351929; min: -90; max: 90)
• lng number required — Longitude (India) (examples: 77.6244807; min: -180; max: 180)
• keyword string required — Dish search keyword (examples: "pizza", "biryani"; minLength: 1)
• sort string — Sort order (default: "relevance"; one of: "relevance", "rating", "price_low_to_high", "price_high_to_low")
• veg string nullable — Filter by veg / non-veg (one of: "veg", "non_veg")
• rating_4_plus boolean — Only dishes rated 4.0+ (default: false)
• price string nullable — Filter by dish price range (one of: "under_100", "rs_100_to_250", "rs_251_to_500", "rs_500_plus")
• count integer required — Max number of dishes to return (min: 1)

Response

• @type string (default: "SwiggyDishResult")
• dish object required
  • @type string (default: "SwiggyDish")
  • id string required
  • name string required
  • category string nullable
  • description string nullable
  • image string nullable
  • in_stock boolean (default: true)
  • is_veg boolean nullable
  • price number nullable
  • final_price number nullable
  • currency string (default: "INR")
  • rating number nullable
  • rating_count integer nullable
  • is_bestseller boolean (default: false)
  • badge string nullable
  • variants array (default: [])
    • @type string (default: "SwiggyDishVariant")
    • id string nullable
    • name string required
    • options array (default: [])
  • addons array (default: [])
    • @type string (default: "SwiggyDishAddon")
    • id string nullable
    • name string required
    • min_addons integer nullable
    • max_addons integer nullable
    • max_free_addons integer nullable
    • choices array (default: [])
  • parent_id string nullable
• restaurant object nullable
  • @type string (default: "SwiggyDishRestaurant")
  • id integer required
  • name string required
  • url string nullable
  • image string nullable
  • rating number nullable
  • rating_count integer nullable
  • google_rating number nullable
  • google_rating_count integer nullable
  • cuisines array (default: [])
  • area string nullable
  • locality string nullable
  • address string nullable
  • cost_for_two number nullable
  • cost_for_two_text string nullable
  • delivery_time integer nullable
  • delivery_time_text string nullable
  • distance_km number nullable
  • parent_id string nullable
  • offer string nullable
  • is_open boolean (default: false)
  • is_promoted boolean (default: false)

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 — The entity was not found, or a precondition failed 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.