Try any of 3860 endpoints — live.
Pick an endpoint, load a working example, tweak the params, and send — no signup to try. Results render the way the data deserves; raw JSON, headers & code are one tab away.
List a city's restaurants, optionally narrowed to one cuisine, locality or curated collection, or to the restaurants that deliver. Returns up to 9 rows — that is the source's own ceiling per listing and it does not page, so breadth comes from varying city/cuisine/locality/collection rather than from a page number. Every row carries `is_promoted`, because on a plain city listing all 9 rows are paid placements.
The Zomato city slug, as it appears in the site's own URLs: 'ncr' (Delhi NCR), 'mumbai', 'bangalore', 'hyderabad', 'chennai', 'kolkata', 'pune', 'jaipur'. Inventory is strictly per city — eight cities measured shared zero restaurants with each other.
Narrow the city to one cuisine, using Zomato's own cuisine slug. Measured to bite: Delhi NCR 25,603 listed → 12,847 north-indian, 9,994 chinese, 4,379 pizza, and every returned row really carried that cuisine (9/9 on each). Common slugs: north-indian, south-indian, chinese, pizza, burger, biryani, desserts, cafe, fast-food, italian, continental, mughlai.
Narrow the city to one neighbourhood, using Zomato's locality slug ('saket', 'connaught-place-delhi', 'koramangala'). This changes which restaurants come back (measured: 9 of 9 rows different, and the rows really sat in that area) but the source's own `source_total_results` counter does NOT move for it and stays city-wide.
One of Zomato's curated city collections ('best-cafes', 'breakfast', 'insta-worthy'). These are the cleanest rows on the site: /ncr/best-cafes returned 0 paid placements out of 9, where the plain city listing returned 9 out of 9.
Which side of Zomato to list. 'delivery' genuinely narrows the city (Delhi NCR 25,603 → 2,107 and every row different). 'dining' is the site's default view — it is accepted for clarity but does not narrow anything, which is why it is the default.
curl -X POST https://api.reefapi.com/zomato/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"city":"ncr"}'Press Send request to see the live result here.
Not sure what to send? Ask Reef AIWhat you can run here, without an account
ReefAPI is one HTTP gateway to 632 live web-data APIs covering 3860 endpoints across 13 categories. Every endpoint answers with the same JSON envelope, so one integration reaches all of them. Each response reports what it cost and when the source was read.
No signup, no API key and no card are required to try an endpoint on this page. Anonymous calls run on a shared demo key, capped at 15 calls per hour per visitor. Pick an API, fill the parameters and the real response comes back from the live source, not from a canned sample. A free account lifts the cap and gives you 1,000 credits and your own key.
Browse every API in the catalog, read an endpoint's fields and example response in the docs, or see per-call credit costs on the pricing page.
Coverage by category
| ecommerce | 350 |
| classifieds | 116 |
| real-estate | 29 |
| media | 25 |
| utilities | 18 |
| jobs | 18 |
| developer-tools | 18 |
| reviews | 15 |
| social | 15 |
| search-seo | 11 |
| travel | 8 |
| other | 5 |
| finance | 4 |