2,500 free credits — no credit card required. Start building
Independent restaurants, by market, with the phone, email and website resolved and the rating attached. Built per row, so a single neighbourhood is as valid an order as a country.
17 credits per enriched row · $21.04–$32.30 per 1,000 · no minimum order
Hospitality turns over faster than almost any other local category. A bought restaurant database is measurably wrong within a quarter: places close, change hands, drop their site, or get renamed under new owners.
That is the argument against buying a static list and the argument for a call you can re-run. Each request collects at the moment you make it, so the list reflects the market this week rather than whenever the vendor last refreshed.
The fields that matter for hospitality outreach come attached: review count as a proxy for size, rating as a proxy for how the conversation will go, and whether they have a website at all.
Swap the query for the segment you sell to — cafes, pizzerias, fine dining, food trucks — and the location for the market you cover.
curl "https://sensecollect.com/v1/maps/search?query=restaurants&location=Austin&limit=100&verify=true" \ -H "x-api-key: $SENSECOLLECT_KEY"Everything you would otherwise collect by opening twenty listings in twenty tabs.
Separate calls for pizzerias, sushi, cafes and bars give you four lists you can write four different opening lines for. One generic list gets one generic email.
metrics.reviews separates the forty-seat independent from the chain outlet without another data source. Under a hundred reviews is usually an owner-operator you can actually reach.
A place at 3.6 has a different problem from a place at 4.8. Both are worth contacting; they are not worth contacting the same way.
/v1/maps/no-website returns only restaurants with no website on file — the shortest path to a web-design or ordering-system pitch.
A watch on restaurants in your city reports new listings the day they appear. A restaurant that opened last week has budget and no incumbent supplier.
Per row, with no minimum order. A single postcode is a valid order.
What restaurant-focused teams ask first.
Most vendors sell a static extract with a minimum order in the thousands of dollars, and hospitality data decays fast enough that you are buying a snapshot. Here you build the list yourself per city, per cuisine, at the moment you need it, and pay by the row — a hundred restaurants in one city costs ${rowsCostUsd(100, GOOGLE_MAPS_ENRICHED_CREDITS_PER_RESULT)} enriched.
Where one is findable. Map listings carry a phone and sometimes a website but no email, so enrichment visits the restaurant's own site and resolves a contact address there. Add verify=true and only rows with a deliverable address are returned and charged.
Call /v1/maps/no-website with query=restaurants and your city. The response contains only places with no site on file, which is the standard prospect list for web design, online ordering and reservation tools.
Create a watch on restaurants in your market. It re-runs the search on a cadence and reports only what changed, so a newly listed restaurant shows up as an added record. Watch runs cost no credits — you pay only when you pull the rows behind them.
Not from map listings — they carry the business, not the owner. What comes back is the business contact. For independents that is usually the owner's line anyway, and personal_only=true keeps named-person email addresses while dropping shared inboxes like info@.
The collection is public business data; the outreach is where the rules live. B2B email in the EU and UK still sits under GDPR and PECR, US commercial email under CAN-SPAM, and a business phone number can still be personal data. Get your own position straight before the first send.
2,500 free credits on signup, no card. Enough for around 147 enriched restaurant rows.