This restaurant API returns live listings for any city as clean JSON: name, cuisine category, address, phone, website, rating, review count, hours. One credit per restaurant returned.
The restaurants as CSV first, ready for Sheets or a CRM:
Sample rows as CSV, exactly as exported · phones unmasked in the API response
| name | cuisine | address | phone | rating | reviews |
|---|---|---|---|---|---|
| Corner Restaurant | Restaurant | 110 E 2nd St, Austin, TX 78701 | (512) 608-44•• | 4.8 | 18185 |
| Caroline | American restaurant | 621 Congress Ave Suite 101, Austin, TX 78701 | (512) 982-67•• | 4.8 | 15010 |
| Corinne Austin | Restaurant | 304 E Cesar Chavez St, Austin, TX 78701 | (737) 787-70•• | 4.8 | 6186 |
| Aba Austin | Mediterranean restaurant | 1011 S Congress Ave Bldg 2 Suite 180, Austin, TX 78704 | (737) 273-01•• | 4.7 | 8264 |
| Salty Sow | American restaurant | 1917 Manor Rd, Austin, TX 78722 | (512) 391-23•• | 4.6 | 3279 |
| Industry | Restaurant | 1211 E 5th St. Ste 150, Austin, TX 78702 | (512) 564-86•• | 4.5 | 1746 |
And one restaurant as JSON:
Each restaurant arrives complete, so a market scan or a lead list needs exactly one request per city.
Pair the listing data with the reviews endpoint to pull what diners actually wrote, not truncated excerpts.
One complete review from that pull, July 27, 2026. The snippet field carries the whole text:
Each review carries the rating, date, full text, reviewer profile, and any photos, with sort options and pagination; the July 27 pull returned 20 full reviews on the first page. Menu photos, sentiment analysis, competitor monitoring: it is all in the text.
The buyers are rarely diners. They are teams selling to restaurants or studying them.
Restaurant-tech sales teams pull city lists to feed a CRM: every restaurant with a phone, a website, and a rating is a qualified row. Market analysts compare cuisine mix and rating distributions across metros. Site-selection teams check density around a candidate address using the coordinates. Researchers track openings and closings by re-pulling a market and diffing against permanentlyClosed. If you need a packaged list instead of an API, the restaurant database page covers that route.
What this is not: a menu, reservation, or delivery API. If you need table availability, live menus, or order status, that is different plumbing owned by the booking and delivery platforms. This returns the restaurant listing layer: who exists, where, how they rate, and how to reach them.
A city scan that returns 20 restaurants costs 20 credits. Review pulls are 1 credit per search.
Place searches bill 1 credit per business returned, and a search that returns nothing costs nothing. Start free with 3,000 credits every month, no card. Paid packs are prepaid and self-serve: 25k for $49 · 100k for $149 · 500k for $549 · 2.5M for $1,999 · up to 250M, ex-tax. That is about $1.96 per 1,000 records at the entry pack, falling to roughly $0.40 per 1,000 at the largest. Credits never expire.
Related: Restaurant database · Yelp Fusion API · Google Reviews API · POI API · Google Maps scraper API
One request returns a city of restaurants with ratings and contacts attached. Try yours on the free tier, no card.
Get 3,000 free credits