CA Labor Commissioner Judgments, Wage Claims, Port Drayage List
Pricing
$0.03 / 1,000 results
California Labor Commissioner enforcement data with the dollar amounts: every judgment with its total owed, status, court and NAICS, the LC 2810.4 port drayage unsatisfied-judgment list with its history, the wage-claim index, and free debarment feeds from WA, NJ, CO, IL and OR.
Leave empty to collect every fast dataset: judgments, the current port drayage list, and the five free multi-state feeds. The wage-claim sweep and the port drayage history are excluded from that default because they are long runs, so name them explicitly when you want them.
[]One flat row per source record, or one row per deduplicated employer across every collected source with the amounts and compliance flags rolled up. Records mode streams rows to the dataset as it goes and fits a full run in the default 1024 MB. Entities mode holds the whole corpus in memory until the end to build the rollup, so give a full entities run 4096 MB; it also starts over rather than resuming after a platform migration, because nothing is written until the end.
Re-enumerate judgments by judgment status and wage claims by calendar month over the same date windows the sweep covered, compare the two passes, merge anything only the second pass found, and write the comparison to the VERIFICATION record in the default key-value store. The judgment check runs one query per status per window, so it costs several times the primary sweep. The wage-claim recount runs one query per month of data it actually saw, about 356 on a full run back to 1997, roughly a minute at the default pacing.
Year slicing starts here. The judgment corpus starts on 2000-04-07, and a separate catch-all slice always covers everything before 2000 so data-entry typos still surface. Raising this skips the years in between.
Where day-by-day slicing starts. The corpus itself reaches back to 1997, and those earlier records are collected by one fixed catch-all slice that splits itself as needed, about 37 requests for roughly 31,000 records instead of the 4,750 that day slicing them would cost. Raising this skips the years in between: setting 2026-08-01 sweeps that day onward plus the catch-all, and does not sweep 2010 to July 2026. That is what makes a narrowed run fast.
First month of the port drayage back-fill. The endpoint replays the list as of any past date, one request per month.
Off by default. Wage-claim rows also exist for the claimant side of a case, and those rows name individual workers rather than businesses. Turn this on only if you have a reason to hold personal data.
Politeness delay each worker waits after a request.
Maximum number of simultaneous requests.
Escape hatch. Leave empty to use the stored value. The actor already self-heals from the framework id every response reports, so you only need this if Salesforce changes something deeper.