Swiggy API endpoint
Use Crawlora's Swiggy Restaurant Menu API to extract supported public Swiggy data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/swiggy/restaurant/menuReturns one restaurant's full menu grouped into categories, plus its restaurant summary. Every item carries a name, description, category, price, discounted_price when currently discounted, veg/non-veg flag, stock status, an image, and Swiggy's own per-dish rating and review count where it carries one. A category nested under a parent group on the live site (e.g. "Whopper" under "Burgers, Wraps & Tacos") is flattened to one level: its title is the parent's, with subcategory set to its own name. The response also carries the restaurant's current promotions in offers, the same block /swiggy/restaurant returns. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| restaurant_id | string | Yes | Restaurant id, from /swiggy/search's id field | ||
| latitude | number | Yes | Caller latitude (required by Swiggy's own menu API) | ||
| longitude | number | Yes | Caller longitude (required by Swiggy's own menu API) | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/swiggy/restaurant/menu" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.
For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.
You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"restaurant": {
"id": "5938",
"name": "Burger King",
"city": "Bangalore",
"cuisines": [
"Burgers",
"American"
],
"cost_for_two": "₹350 for two",
"rating": 4.1,
"total_ratings": 41000,
"is_open": true,
"hours_status": "Open now"
},
"offers": [
{
"title": "FLAT 50% OFF",
"description": "ON SELECT ITEMS",
"tag": "FLAT DEAL"
}
],
"categories": [
{
"title": "Burgers, Wraps & Tacos",
"subcategory": "Whopper",
"items": [
{
"id": "112372940",
"name": "Crispy Veg Double Patty Burger",
"category": "Burgers, Wraps & Tacos",
"price": 99,
"discounted_price": 79,
"is_veg": true,
"in_stock": true,
"image_url": "https://media-assets.swiggy.com/swiggy/image/upload/fl_lossy,f_auto,q_auto/FOOD_CATALOG/IMAGES/CMS/2025/11/20/5965c1c3-c079-41d7-a35e-5394b0822f6d_cb654bd9-dccd-4493-85a0-dc6cf1007653.jpg"
}
]
}
]
}
}Request schema
No body schema
Response schema
#/definitions/swiggy.menuResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | Code is the HTTP status code or a custom code used to indicate the result of the request @example 200 | |||
| data | swiggy.MenuResponse | No | ||||
| data.categories | array | No | ||||
| data.categories[].items | array | No | ||||
| data.categories[].items[].category | string | No | ||||
| data.categories[].items[].description | string | No | ||||
| data.categories[].items[].discounted_price | number | No | ||||
| data.categories[].items[].id | string | No | ||||
| data.categories[].items[].image_url | string | No | ||||
| data.categories[].items[].in_stock | boolean | No | ||||
| data.categories[].items[].is_veg | boolean | No | ||||
| data.categories[].items[].name | string | No | ||||
| data.categories[].items[].price | number | No | ||||
| data.categories[].items[].rating | number | No | Rating and TotalRatings are Swiggy's own aggregate score and review count for this individual dish, the same two fields a restaurant carries. Omitted when the dish has no rating yet. Only the headline aggregate is returned -- individual reviews and reviewer identity are out of scope for this platform. | |||
| data.categories[].items[].total_ratings | integer | No | ||||
| data.categories[].subcategory | string | No | ||||
| data.categories[].title | string | No | ||||
| data.offers | array | No | ||||
| data.offers[].coupon_code | string | No | ||||
| data.offers[].description | string | No | ||||
| data.offers[].tag | string | No | ||||
| data.offers[].title | string | No | ||||
| data.restaurant | swiggy.Restaurant | No | ||||
| data.restaurant.address | string | No | ||||
| data.restaurant.area | string | No | ||||
| data.restaurant.city | string | No | ||||
| data.restaurant.cost_for_two | string | No | ||||
| data.restaurant.cuisines | array | No | ||||
| data.restaurant.delivery_time_minutes | integer | No | ||||
| data.restaurant.dishes | array | No | Dishes are the menu items that actually matched a /swiggy/search query, carried only by Swiggy's own "Dishes" search tab (tab=dish). Empty on the restaurant tab, on a plain nearby browse, on a collection browse, and on /swiggy/restaurant -- none of those upstream shapes carry per-restaurant dish matches. | |||
| data.restaurant.dishes[].category | string | No | ||||
| data.restaurant.dishes[].description | string | No | ||||
| data.restaurant.dishes[].discounted_price | number | No | ||||
| data.restaurant.dishes[].id | string | No | ||||
| data.restaurant.dishes[].image_url | string | No | ||||
| data.restaurant.dishes[].in_stock | boolean | No | ||||
| data.restaurant.dishes[].is_veg | boolean | No | ||||
| data.restaurant.dishes[].name | string | No | ||||
| data.restaurant.dishes[].price | number | No | ||||
| data.restaurant.dishes[].rating | number | No | Rating and TotalRatings are Swiggy's own aggregate score and review count for this individual dish, the same two fields a restaurant carries. Omitted when the dish has no rating yet. Only the headline aggregate is returned -- individual reviews and reviewer identity are out of scope for this platform. | |||
| data.restaurant.dishes[].total_ratings | integer | No | ||||
| data.restaurant.external_rating | swiggy.ExternalRating | No | ||||
| data.restaurant.external_rating.count | string | No | ||||
| data.restaurant.external_rating.rating | number | No | ||||
| data.restaurant.external_rating.source | string | No | ||||
| data.restaurant.hours_message | string | No | ||||
| data.restaurant.hours_status | string | No | HoursStatus/HoursMessage are Swiggy's own live open/close callout for this outlet ("Open now" / "Closes 11:30 pm"); OpeningHours is its weekly schedule. Only the restaurant detail and menu responses carry these -- search and collection listing cards do not, so they are empty on /swiggy/search results. | |||
| data.restaurant.id | string | No | ||||
| data.restaurant.image_url | string | No | ||||
| data.restaurant.is_open | boolean | No | ||||
| data.restaurant.is_promoted | boolean | No | IsPromoted reports whether Swiggy itself labels this a promoted (sponsored, paid-placement) result rather than an organic one. Present and true only for those; Swiggy marks none on a plain nearby browse. | |||
| data.restaurant.latitude | number | No | ||||
| data.restaurant.locality | string | No | ||||
| data.restaurant.longitude | number | No | ||||
| data.restaurant.name | string | No | ||||
| data.restaurant.offers | array | No | Offers are the promotions Swiggy shows on this restaurant's own listing card in a search, browse, or collection result -- the headline discount and its condition, its badge, and any separate free-delivery benefit. Absent when the card shows no promotion, and on /swiggy/restaurant and /swiggy/restaurant/menu, whose responses carry the restaurant's fuller offer list at the top level instead. | |||
| data.restaurant.offers[].coupon_code | string | No | ||||
| data.restaurant.offers[].description | string | No | ||||
| data.restaurant.offers[].tag | string | No | ||||
| data.restaurant.offers[].title | string | No | ||||
| data.restaurant.opening_hours | array | No | ||||
| data.restaurant.opening_hours[].day | string | No | ||||
| data.restaurant.opening_hours[].hours | string | No | ||||
| data.restaurant.phone | string | No | ||||
| data.restaurant.postal_code | string | No | ||||
| data.restaurant.rating | number | No | ||||
| data.restaurant.rating_count | string | No | ||||
| data.restaurant.total_ratings | integer | No | ||||
| data.restaurant.unavailable_message | string | No | UnavailableMessage is Swiggy's own reason this listed restaurant cannot be ordered from right now ("Currently not taking orders for this location", "Opens next at 5 pm, today", "Temporarily closed for delivery"). Absent for a restaurant that is currently orderable. Note it is not simply the inverse of is_open: a restaurant Swiggy reports as open can still be unavailable for the requested location. | |||
| msg | unknown | No | Msg is the message that describes the result of the request @example "Request successful" |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/swiggy/restaurant/menu" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms