We extract restaurant coordinates, critic reviews, Heatmap features, and neighborhood guides from Eater. Delivered as clean JSON, CSV, or Parquet to S3 or BigQuery on your cadence.
Structured, schema-consistent data across all major object types — delivered clean, typed, and ready to query.
Complete list of extractable fields for Restaurant Maps objects from eater.com. All fields typed and schema-versioned.
"map_id": "eater-38-nyc", "map_title": "The 38 Essential Restaurants in New York City", "restaurant_name": "Tatiana by Kwame Onwuachi", "rank_position": 1, "address": "10 Lincoln Center Plaza, New York, NY 10023", "latitude": 40.7725, "longitude": -73.9835, "cuisine_tags": "['Afro-Caribbean', 'American']"
| # | map_id | map_title | city | publish_date | author | restaurant_name |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Restaurant Metadata objects from eater.com. All fields typed and schema-versioned.
"name": "Lilia", "neighborhood": "Williamsburg", "city": "New York", "price_tier": "$$$", "cuisine_type": "Italian", "status": "Open", "reservation_url": "https://resy.com/cities/ny/lilia"
| # | restaurant_id | name | address | neighborhood | city | phone |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Critic Reviews objects from eater.com. All fields typed and schema-versioned.
"article_id": "eater-ny-review-12948", "headline": "A New Era for Brooklyn Dining", "author": "Ryan Sutton", "restaurant_name": "Blanca", "rating_stars": 4, "recommended_dishes": "['Aged Duck', 'Pasta Tasting']", "publish_date": "2026-03-14T08:30:00Z"
| # | article_id | headline | subheadline | author | publish_date | restaurant_name |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for City News Feed objects from eater.com. All fields typed and schema-versioned.
"post_id": "news-84721", "city_slug": "chicago", "category": "Openings", "headline": "A Massive Food Hall Lands in the West Loop", "author": "Ashok Selvam", "tags": "['Food Halls', 'West Loop', 'New Openings']", "mentioned_restaurants": "['Time Out Market', "Gott's Roadside"]"
| # | post_id | city_slug | category | headline | author | publish_timestamp |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Chef & Industry Intel objects from eater.com. All fields typed and schema-versioned.
"chef_name": "Rene Redzepi", "restaurant_group": "Noma Projects", "location": "Copenhagen", "article_type": "Interview", "headline": "Life After Noma", "opening_date": "None", "source_url": "https://eater.com/noma-future"
| # | article_id | chef_name | restaurant_group | location | article_type | headline |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Our Eater scraper navigates the Vox Media Chorus CMS to pull structured metadata, geospatial coordinates, and editorial text from dynamic maps and articles.
Capture the essential restaurant lists across all city subdomains. Track additions, removals, and rank changes over time.
Monitor new openings and trending spots by extracting data from monthly Eater Heatmaps.
Extract precise latitude and longitude coordinates from embedded Mapbox integrations.
Extract critic ratings, review text, author details, and recommended dishes from full-length articles.
Map restaurants to precise local districts and boroughs as defined by Eater editors.
Capture outbound links to Resy, OpenTable, SevenRooms, and direct booking platforms.
Target specific subdomains like ny.eater.com, london.eater.com, or sf.eater.com to isolate regional data.
Track restaurant closures and industry shifts by parsing historical articles and updated lists.
Render dynamic layout blocks in the Chorus CMS to capture data hidden from standard HTTP requests.
Brief in. Clean data out.
Provide target cities, map types (Eater 38, Heatmaps), or article categories. We design the extraction schema.
We configure Playwright crawlers to handle Chorus CMS rendering, map API interception, and pagination.
Schema validation, coordinate accuracy checks, and null-rate monitoring before full launch.
JSON, CSV, or Parquet pushed to your S3 bucket or BigQuery dataset on agreed cadence.
Extracting data from Vox Media properties requires navigating heavy JavaScript frameworks and dynamic map integrations. Here is how we ensure reliable data delivery.
Eater relies on Mapbox and Google Maps for its interactive lists. The raw coordinates are often hidden from the DOM. We intercept the underlying XHR/Fetch requests during page load to extract exact latitude and longitude data directly from the map payloads.
Vox Media uses a proprietary CMS (Chorus) that heavily relies on JavaScript to render article components, image galleries, and embedded lists. We run full Playwright browser sessions to ensure all dynamic content is fully hydrated before extraction.
Eater news feeds and category pages use infinite scroll rather than traditional pagination. Our crawlers simulate human scrolling behaviour to trigger subsequent API calls, ensuring complete extraction of historical articles.
Eater segments content across subdomains (e.g., chicago.eater.com). We manage routing across all active city portals, normalising the output into a single unified schema so your data science teams do not have to write custom parsers for each city.
Restaurants frequently enter and exit the Eater 38 or Heatmaps. We maintain state across pipeline runs, emitting diffs when a restaurant is added or removed, allowing you to track dining trends over time.
Retail developers use restaurant density and trending Heatmap locations as proxies for foot traffic and neighbourhood gentrification.
Delivery platforms identify trending and newly opened restaurants to prioritise for sales outreach and exclusive partnerships.
Concierge services and travel aggregators enrich their local guides with curated recommendations from Eater 38 lists.
Restaurant groups track mentions, critic reviews, and sentiment to benchmark their properties against local competitors.
Private equity firms track urban dining trends, closures, and openings as leading indicators of local economic health.
Platforms like OpenTable and Resy track un-partnered trending spots to target for software sales.
"Eater dictates urban dining trends. Extracting its maps and reviews transforms editorial opinion into a structured geospatial dataset for market analysis."
Parsing Vox Media's Chorus CMS requires executing heavy JavaScript and intercepting map rendering APIs. DataFlirt handles the complex DOM extraction and geospatial coordinate mapping so your data science teams receive clean, queryable restaurant metadata without maintaining fragile scrapers.
Everything supported by our eater.com scraper — rendered SPA elements, auth walls, rate-limit evasion and beyond.
Open-source tooling on proven cloud infra — no vendor lock-in, full observability.
Playwright intercepts and renders Vox Media's proprietary dynamic blocks to ensure all restaurant metadata is exposed to the DOM.
Network traffic analysis during page load captures raw Mapbox API payloads, yielding precise coordinate data.
Pipelines run on AWS infrastructure with Airflow managing scheduling, retries, and SLA alerting. State is stored in PostgreSQL.
Data delivered to where your team already works — no new tooling required.
About eater.com scraping, legality, and pipeline operations.
Ask us directly →Scraping publicly available information from Eater is generally permissible under applicable law. DataFlirt targets only public, non-authenticated editorial and map data. We do not circumvent authentication walls or extract private user data.
Eater embeds maps using providers like Mapbox. We intercept the network requests made by the browser during page load to extract the raw JSON payloads containing exact latitude and longitude data.
Yes. We maintain historical state across pipeline runs. When a restaurant is removed from an updated list, our change detection system flags the removal in the output diff.
Yes. We crawl all active regional portals including ny.eater.com, la.eater.com, london.eater.com, and chicago.eater.com, normalising the data into a single schema.
We can configure pipelines to check for Heatmap updates daily or weekly, ensuring you capture new trending spots as soon as editors publish them.
Yes. We capture outbound URLs directing to reservation platforms like Resy, OpenTable, and SevenRooms, which is useful for lead generation and platform analysis.
20-minute scoping call. Pilot dataset within the week. Production within two. Whether you need a one-off export of the Eater 38 across all cities or continuous tracking of trending Heatmaps, we scope, build, and operate the pipeline.
