Boulder CO Restaurant Inspections Scraper β 2013β2026 Snapshot
Pricing
from $2.10 / 1,000 inspections
Boulder CO Restaurant Inspections Scraper β 2013β2026 Snapshot
Scrape Boulder County, CO restaurant inspections Jan 2013 β Jul 2026 (16,346 inspections at snapshot; static snapshot, no updates) via data.colorado.gov: score, result, violations or inspector comments, address, coordinates. Boulder, Longmont, Lafayette, Louisville. Filter by city, name, date.
Pricing
from $2.10 / 1,000 inspections
Rating
0.0
(0)
Developer
John
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
19 hours ago
Last modified
Categories
Share
The Boulder County restaurant inspections scraper gives you one row per restaurant inspection (inspector comments grouped) for Boulder County, Colorado, straight from Boulder County via the official State of Colorado open-data portal (data.colorado.gov). No login or coding needed: run it in your browser, on a schedule, or through the Apify API, and export results as JSON, CSV or Excel.
Get restaurant and food facility inspections for Boulder County, Colorado (Boulder, Longmont, Lafayette, Louisville, Niwot, Lyons and more) as clean JSON, CSV or Excel. The data comes from Boulder County through the official State of Colorado open-data portal (data.colorado.gov dataset 6ytb-f2cq, Sept 2025 β Jul 2026, and historical dataset tuvj-xz3m, Jan 2013 β Aug 2025).
This is a one-time snapshot that will not update. Both source datasets are marked "Never" / "Static" for updates by the state portal. The data runs from 2013-01-02 to 2026-07-21 and contains 16,346 inspections at snapshot (633 from 6ytb-f2cq + 15,713 from tuvj-xz3m). No inspections after 2026-07-21 will appear.
What you get
The source publishes one row per inspector comment. This actor groups them so that each row is one inspection: one facility + inspection type + final inspection date + score + result, with all inspector comments (violations and notes) in a comments list. Rows are sorted newest final inspection first (stable tiebreak on facility ID and :id).
The historical file (2013 β Aug 2025) is published as one row per checklist item; the actor groups those into one row per inspection (facility + date + type) too. Historical rows have a violations list (items marked Out / Out-High / Out-Medium / Out-Low / Full / Half) instead of free-text comments, result is null (not published), plus facilityType and facilityCategory. The dataset field tells you which file each row came from. facilityType and facilityCategory are always present (null for Sept 2025+ rows, which don't publish them).
Linking a facility across both files: the two files use different businessId schemes, so the same facility has two IDs (e.g. PHO KITCHEN BAR & GRILL is FA0003878 in the historical file and FA0001508 in the current one). Use facilityKey instead: the normalized facility name + street address (uppercase, punctuation removed, street suffixes abbreviated such as ROAD β RD, unit/suite words and a trailing unit number dropped, e.g. 1219 ROCK CREEK CIR 1 β 1219 ROCK CREEK CIR; N/S/E/W directionals ignored). Chains keep one key per address, so different locations never merge, e.g. PHO KITCHEN BAR GRILL|2900 BASELINE RD. It's a best-effort match: renamed facilities, or ones whose address is spelled differently, won't link.
Sample output (real run)
{"businessId": "FA0001669","facilityName": "SEBS PIZZAS (MOBILE)","address": "1219 ROCK CREEK CIRCLE 1","city": "LAFAYETTE","state": "CO","zip": "80026","inspectionType": "Routine","firstInspectionDate": "2025-09-03","finalInspectionDate": "2026-07-21","score": 25,"result": "Pass","commentCount": 2,"comments": ["3-501.16(A)(2) Cold holding\nPrep refrigerator ambient air temperature 59 degrees F. \n\nMaintain 41Β°F and below cold holding. Ambient temperature in the unit was 107 degrees F.\n\nUnit filled with ice and at ambient temperature of 79 deg. F, the air temperature of the unit was brought down to 35 de...","4-203.12 Temperature Measuring Devices, Ambient Air\nThermometer not available in the prep cooler.\n\nProvide and accurate air thermometer to monitor temperature."],"latitude": 39.97449,"longitude": -105.07242,"source": "Boulder County Public Health via data.colorado.gov"}
Use cases
- Food-safety consultants, pest control and cleaning services:
resultContains: "Reinspection"lists facilities that failed and must be re-inspected. - Restaurant suppliers and equipment repair: comments mention broken coolers, thermometers, hand sinks.
- Journalists and researchers: compare scores across Boulder County towns.
How to scrape Boulder County restaurant inspections
- Click Try for free (or Start) on this page. A free Apify account is enough.
- Leave the prefilled input to get a quick sample, or set the filters described below.
- Set maxItems to cap how many rows (and how much) a run returns.
- Click Start and wait a few seconds to a minute.
- Download the results as JSON, CSV or Excel, or connect them to Google Sheets, Zapier, Make or a webhook.
Input
| Field | Description |
|---|---|
| inspectedSince | Optional real date, YYYY-MM-DD, applied to the final inspection date. Invalid dates fail fast with a clear message. |
| cities | e.g. BOULDER, LONGMONT (case-insensitive) |
| nameContains | Facility name text |
| resultContains | Reinspection or Pass (only Sept 2025 β Jul 2026 rows have a result, so this skips history) |
| includeHistory | Default on: add the 15,713 inspections from 2013 β Aug 2025 |
| maxItems | Default 200 |
Pricing (pay per event)
$3 per 1,000 inspections ($0.003 each) plus Apify's minimal $0.00005 start fee. Example: 200 inspections = 200 Γ $0.003 + $0.00005 β $0.60.
Data caveats
Data is provided as published by Boulder County. This is a static snapshot (portal update frequency: Never/Static), newest inspection 2026-07-21. The two files use different formats and scoring checklists, so scores are not directly comparable across them; 2020 has few inspections (COVID). A full 16k-inspection pull reads ~657k source rows and may take several minutes (default timeout is 600 s). score is points as published (higher means more issues). firstInspectionDate / finalInspectionDate are passed through unchanged even where they look out of order. City names are passed through as published (mixed case).
License and disclaimer
The source dataset is Public Domain (data.colorado.gov). This actor uses only the official public open-data API and is not affiliated with or endorsed by Boulder County, Boulder County Public Health or the State of Colorado.
FAQ
How much does it cost to scrape Boulder County restaurant inspections?
You pay $0.003 per result ($3 per 1,000) plus a $0.00005 start fee, and nothing else. Apify's free plan includes $5 of monthly credit, which covers about 1,600 results. See Pricing above for a worked example.
Is it legal to scrape Boulder County restaurant inspections?
This Actor reads public records from Boulder County via the official State of Colorado open-data portal (data.colorado.gov), using only public endpoints (no login, no CAPTCHA bypass, no private accounts). See the source/license section above for the dataset's terms. You are responsible for how you use the data; this is not legal advice.
How fresh is the data?
Each run reads the source live, so you get whatever the agency has published at that moment. How often the agency updates, and any known lag, is described in the data caveats/notes section above.
Can I use it via API, on a schedule, or with Google Sheets?
Yes. Every Apify Actor has a REST API and client libraries for Python and JavaScript. You can schedule daily or weekly runs, and send results to Google Sheets, Slack, Zapier, Make, n8n, webhooks, or an AI agent via the Apify MCP server.
I need another city, county or field. Can you add it?
Open an issue on the Issues tab with the city or data source you need. We build new public-records scrapers regularly.
More public-records scrapers by Groundplanes
Same clean output, pay-per-result pricing and official public data sources:
Restaurant & food inspections
- Maricopa County (Phoenix) Restaurant Inspections Scraper
- Las Vegas Restaurant Inspections & Grades Scraper (SNHD)
- Pittsburgh Restaurant Inspections Scraper (Allegheny County)
- Delaware Restaurant Inspections Scraper β Statewide Violations
- Montgomery County MD Restaurant & Food Inspections Scraper
- NY State Restaurant Inspections Scraper β NYSDOH, Non-NYC
Code violations & distressed property leads
- Pittsburgh Code Violations Scraper β Distressed Property Leads
- Orlando FL Code Enforcement Scraper β Code Violation Leads
- New Orleans Code Violations Scraper β Code Enforcement Leads