New Orleans Code Violations Scraper — Code Enforcement Leads
Pricing
from $2.10 / 1,000 violations
New Orleans Code Violations Scraper — Code Enforcement Leads
Scrape City of New Orleans code enforcement violations via the official open-data API: case number, property address, violation date, code section, violation (weeds, sanitation, rodents, roofs, exterior) and full code text. Updated daily. Distressed-property, motivated-seller and contractor leads.
Pricing
from $2.10 / 1,000 violations
Rating
0.0
(0)
Developer
Groundplane Labs
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Features
Share
The New Orleans code violations scraper gives you one row per code enforcement violation for New Orleans, Louisiana, straight from the City of New Orleans via the official data.nola.gov open-data API. 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 City of New Orleans code enforcement violations as a clean, filterable list: case number, property address, violation date, code section, violation name (weeds, sanitation, sidewalks, rodent harborage, exterior surfaces, roofs, motor vehicles ...) and the full code text. Data comes from the official open-data API (data.nola.gov dataset 3ehi-je3s, "Code Enforcement All Violations"). The dataset is refreshed daily (newest violation at the November 2026 audit: 2026-11-09).
What you get
By default each row is one violation as published by the City of New Orleans (violationId is unique; 273,908 since 2008 at audit). One case (caseNumber, one property inspection) usually has several violations. Set onePerCase: true to get one row per case (its newest violation, plus violationCount). Rows are sorted newest violation first with a stable :id tiebreak, so large runs never skip or repeat rows.
Sample output (real run)
{"caseNumber": "26-11774-MPM","caseId": "338003","violationId": "1052742","address": "3746 Preston Pl","violationDate": "2026-10-16","violationDateTime": "2026-10-16T13:40:15.000","codeSection": "26-157","violation": "157 Sanitation","description": "All exterior property and premises shall be maintained in a clean, safe and sanitary condition, free from any accumulation of trash, litter, debris, garbage, waste, rubbish or other similar material. Every occupant of a structure shall dispose of all rubbish in a clean and sanitary manner by placing such trash in approved container(s), as provided in Chapter 138 of the Code of the City of New Orleans.","source": "City of New Orleans Code Enforcement via data.nola.gov"}
Use cases
- Real-estate investors / wholesalers: properties with recent code violations, e.g.
violationContains: ["Roofs", "Exterior Surfaces"],onePerCase: true. - Contractors (lawn care, junk removal, pest control, roofing, painting):
violationContains: ["Weeds"],["Rodent"],["Roof"],["Paint"]. - Researchers and journalists: violation trends by type and street.
How to scrape New Orleans code violations
- 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 |
|---|---|
| violatedSince | Optional real date, YYYY-MM-DD. Invalid dates fail fast with a clear message. Empty = all, newest first |
| violationContains | Violation name (partial), e.g. Weeds, Sanitation, Rodent, Roof; or code section (exact): 26-160 also matches 26-160(a), but 26-16 does not match 26-160 to 26-169 |
| locationContains | Address text, case- and punctuation-insensitive, e.g. Elysian Fields; St. Charles = St Charles |
| onePerCase | Default false. On = one row per case (newest violation) with violationCount |
| maxItems | Default 200 (rows, or cases when onePerCase is on) |
Pricing (pay per event)
$3 per 1,000 rows ($0.003 each) plus Apify's minimal $0.00005 start fee. Example: 200 violations = 200 × $0.003 + $0.00005 ≈ $0.60; one month of violations (about 1,100 at audit) ≈ $3.30, or about 280 cases with onePerCase ≈ $0.84. If a run hits your max charge limit, it stops cleanly and reports how many rows it delivered.
Data caveats
Data is provided as published by the City of New Orleans. Addresses are as typed by the city (no ZIP, no coordinates in the source). description is the generic code text for that section, not the inspector's notes. A violation record is an inspection finding, not a final judgment; the dataset does not include hearing outcomes or fines. With onePerCase, violationCount is the exact total number of violations on that case in the source (all dates and types, counted with a grouped query), even if your filters matched only some of them.
License and disclaimer
Source: City of New Orleans Open Data (data.nola.gov, public records). This actor uses only the official public open-data API and is not affiliated with or endorsed by the City of New Orleans.
Run status
Every run ends Complete: or PARTIAL: with the rows scanned, matched and delivered, and the source's newest violation date. PARTIAL: lists the concrete reason (stale source, skipped or value-issue rows); the Issues line below is appended only when a reason is caused by the source. Hitting maxItems is stated inside the message; hitting your max charge limit ends PARTIAL with no Issues line, because that cap is yours.
Canary input (labeled)
{"violationContains": ["Weeds"], "maxItems": 5}
Expected: Complete: 5 of 32031 matched row(s) delivered, capped at maxItems 5 while the source stays as fresh as at audit (counts as of 2026-11-10; the totals grow as the city publishes).
Troubleshooting
- Stale data: if the source's newest violation date is over 14 days old, the run ends PARTIAL, names that date, and appends the Issues line below. The city refreshes the dataset daily, so a stale result means the source, not your filters.
- Zero matches: a healthy source with no matching rows ends
Complete: 0 rows matched your filters, with the source total stated. An empty source fails loudly instead. - Caps: hitting
maxItemsis stated inside the Complete message. Hitting your max charge limit ends PARTIAL with the rows delivered counted, and no Issues line, because that cap is yours, not the source's. - Invalid rows or values: rows the source ships in an unexpected shape are skipped and counted in a PARTIAL message; a single bad violation date ships as null and is counted the same way.
- If this keeps happening, please open an issue on this actor's Issues tab and we'll fix it fast.
Changelog
- 0.2 (2026-11-10, deep audit): core-column sentinel on an unfiltered probe, per-row validation with counted value issues (strict violation dates, text-type rule), Complete/PARTIAL status contract with scanned, matched and delivered counts, source freshness check, fleet retry standard, strict maxItems parsing. Healthy output is unchanged from 0.1.
- 0.1 (2026-10-17): first release.
FAQ
How much does it cost to scrape New Orleans code violations?
You pay $0.003 per result ($3 per 1,000) plus a $0.00005 start fee, and nothing else. That is the free-plan price: on paid Apify plans you pay less per result (Bronze 10%, Silver 20%, Gold and above 30% off). 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 New Orleans code violations?
This Actor reads public records from the City of New Orleans via the official data.nola.gov open-data API, 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
- Boulder CO Restaurant Inspections Scraper — 2013–2026 Snapshot
- Montgomery County MD Restaurant & Food Inspections Scraper
- NY State Restaurant Inspections Scraper — NYSDOH, Non-NYC
- Boston Restaurant Inspections Scraper — Health Violations
- Santa Clara County Restaurant Inspections Scraper — San Jose
Code violations & distressed property leads
- Pittsburgh Code Violations Scraper — Distressed Property Leads
- Orlando FL Code Enforcement Scraper — Code Violation Leads