Build a restaurant database from live Google Maps
Fixed files go stale. Pull fresh records straight from Google Maps.
What data do you get?
That exact call came back in about a second with 5 complete records. Set limit up to 100 restaurants per search, and add stars=true for each spot's 1-to-5 review histogram.
How do you get started?
No code needed. From zero to a CSV of restaurants in about two minutes:
- 1
Create a free account. Try it free, no card needed.
- 2
Type a search in the playground. Something like restaurants in Portland. The restaurants land in a table.
- 3
Click export. Download the CSV and open it in Sheets or Excel. Done.
Developers: skip the playground. Copy your key from the dashboard and run the curl above. Same data, as JSON.
The full listing, ready for a database
Every record comes complete. No field tiers, no extra charge for hours or ratings:
Where Google shows them, records also carry the listing's attribute lists: service options (delivery, takeout, outdoor seating), dining options, amenities, and payment types.
The catch: Google Maps listings never include an email address, so these records don't either. The section below covers how to get a verified email for the owner.
From one search to the whole city
One search returns up to 100 restaurants, and a city holds more. CrustAPI sweeps the whole metro and hands back every restaurant, deduplicated into one citywide table.
Billing notes: empty searches cost nothing. Maps bills per business and enriched People per full profile, so check the estimate when choosing a result limit.
Who uses this data?
| Who | What they build | The fields that matter |
|---|---|---|
| Food suppliers and distributors | A call list for every restaurant in the delivery zone | Phone, address, categories, and hours (so reps call between rushes) |
| POS and restaurant SaaS sales | Territory lists ranked by how busy a spot looks | Review count as a traffic proxy, rating, website, plus a verified owner email from LinkedIn people search (beta) |
| Analysts and researchers | Market maps: cuisine mix, density, and rating spread by area | Categories, lat/lng, rating, and the permanently-closed flag |
How much does a restaurant database cost?
You pay the Maps rate for each restaurant a search returns. Eighty Maps results cost $0.1568 at standard prices. Empty searches are free. Here is the deposit pricing:
| Deposit | Google Search / 1,000 requests | Maps / 1,000 businesses | LinkedIn reads / 1,000 requests | People, Jobs, Refresh / 1,000 units |
|---|---|---|---|---|
| $10+ | $1.00 | $1.96 | $6.00 | $1.96 |
| $149+ | $0.76 | $1.49 | $4.50 | $1.49 |
| $549+ | $0.56 | $1.10 | $3.30 | $1.10 |
| $1,999+ | $0.41 | $0.80 | $2.45 | $0.80 |
| $6,500+ | $0.33 | $0.65 | $1.95 | $0.65 |
| $27,500+ | $0.28 | $0.55 | $1.65 | $0.55 |
| $50,000+ | $0.26 | $0.50 | $1.50 | $0.50 |
| $100,000+ | $0.20 | $0.40 | $1.50 | $0.40 |
Every eligible account gets $6 of free usage monthly. Each deposit keeps its prices until spent; paid funds never expire. People and Jobs bill per successful search, Refresh per accessible profile. Full profiles in People use the read rate per full profile. See all billing details.
Larger deposits unlock lower endpoint prices. Each deposit keeps its prices until spent. See the full deposit table on the pricing page. Prices in USD, ex-tax.
Funds are prepaid and never expire, so whatever a project doesn't use waits for the next one.
Add the reviews, then find the owner
Swap type=maps for type=reviews to pull the actual Google reviews for any restaurant in your table: rating, text, author, and date, sorted and paginated, in about 0.3 seconds per call.
When the job is outreach, the Maps record gets you the restaurant and the LinkedIn people search endpoint (beta) gets you the person. It searches public LinkedIn profiles and returns a verified email on people results.
Related: Google Maps Scraper API · Google Reviews API · LinkedIn People Search API (beta)
When something else is the better pick: if you need a prebuilt national list today, a dataset vendor's ready-made CSV gets you started faster, stale rows and all. If you're building live map features inside an app, Google's official Places API is built for exactly that; here's how they compare. This page is for people who want fresh records they own and can keep.
Common questions
No. Google Maps listings carry a phone number and a website, and never an email address, so maps records here don't include one. When you need a decision maker's email, use the LinkedIn people search endpoint (beta) instead; it searches public profiles and returns a verified email on people results.
Every query is scraped live from Google Maps at request time, typically in about a second. Hours, ratings, review counts, and closed flags reflect what Google shows at the moment you ask, so nothing in your table has to be older than your last run.
One search returns up to 100 restaurants, but a city holds more. CrustAPI sweeps the whole metro and returns every restaurant, deduplicated for you, past Google's ~100-per-search cap. You pay one charge per restaurant returned, and a search that comes back empty is free.
Maps costs $1.96 per 1,000 businesses at standard prices, down to $0.40 for the largest deposit. Empty and failed searches are free. Every eligible account gets $6 of free usage monthly. Paid funds never expire.
The response is plain JSON, so it drops into Sheets, Clay, a CRM, or a database with no transformation. There are no storage limits on our side; the rows you pull are yours to keep and build on. Non-coders can run the same searches in the playground at /app.
Logged-out, public-only collection has repeatedly defeated computer-fraud and contract claims, while Google's Terms prohibit automated access that violates instructions like robots.txt. We handle the collection; what you get is restaurant data that's public on the map for anyone to see.
Clay
Start with one city
The free plan covers a real citywide restaurant list. Run one search and look at the JSON that comes back.
Try for free