Data source

Data from Yelp, delivered clean.

4 datasets pulled from Yelp's releases, checked field by field and shipped the way you want them — daily, weekly, or hourly, your call.

  • 4 datasets
  • 1 industry
  • Real rows on request

What Datadory delivers from Yelp

4
Restaurants United States - 11 metropolitan areas · One coherent multi-year snapshot

Yelp structured datasets

Restaurants United States and Canada core Yelp markets · Current-state records - ratings

Yelp Places API (Fusion successor)

Restaurants Worldwide - every continent · Dated snapshot builds

Overture Maps Places

Restaurants Global - 100M+ points of interest across 200+…

Foursquare Places API

Pick a catch, see the rows.

Name any Yelp dataset and we send real rows from it — not a screenshot of rows. 1,744 datasets. Pick your catch.

Get a sample

API, files, or your warehouse. Daily, weekly, or hourly.

Straight answers about Yelp data

How large is the Yelp review corpus?

6,990,280 full-text reviews covering 150,346 businesses across 11 U.S. metropolitan areas, completed by 200,100 captioned photos and user, check-in and tip families. Every review joins to both its author and its venue, so the corpus reads as one connected graph rather than loose text.

Do the two Yelp datasets overlap?

They complement rather than duplicate. The corpus supplies depth - prose, reviewers, check-ins, photos - frozen at one stated vintage. The live record supplies state - current rating, price band, hours and closure flag per business. Sentiment work pairs the two: scores and counts from the live side, the language underneath from the corpus.

Can one delivery include both text and current ratings?

Yes. Datadory ships both records through one contract, joined where they meet, so a venue list drawn from the live grid carries its review prose from the corpus without a second vendor relationship. Name the metros or cities and the sample comes back cut that way, rows and dictionaries included.

How fresh is Yelp data delivered through Datadory?

Freshness follows your chosen cadence, not a fixed schedule - daily, weekly, or hourly, your call. The corpus is a single coherent multi-year snapshot whose vintage is stated in your sample report; the live record restates current state on every pull, so movement between pulls is signal rather than staleness.