Liquor License New Openings Tracker — 9 States + Chicago Pre-Opening Leads

A multi-state liquor-license lead feed for hospitality vendors, delivered as events:

Event (event_type)	What happened	Feed	Who acts on it
new_application	A liquor-license application was filed — the earliest public signal that a bar, restaurant or store is opening, typically 60–90 days before doors open	pending	distributors, POS/payments, insurance, suppliers
newly_issued	The license was issued — doors open imminently. Texas issued licenses also carry opened_verified: whether the permit has started filing mixed-beverage tax receipts, i.e. whether it is provably selling (new in 1.1)	active	the same buyers, plus anyone who wants proof of opening, not just a permit
closing_detected	A license expired, was surrendered, cancelled or revoked, or is lapsing without a renewal — a venue going dark (new in 1.1; TX, OR, Chicago)	closing	distributors (churn), CRE brokers (vacancy), insurers (lapsed coverage), competitors (site pickup)
status_change	A tracked license or application changed status between two delta runs	any	pipeline hygiene
inventory	A roster row (inventory mode) or the first delta run's baseline	any	one-off lists

Every event row is one normalized, sales-ready record straight from the official state (or city) registry — no logins, no keys.

• Texas (TABC) — active licenses + pending original applications (data.texas.gov)
• New York (SLA) — active licenses + pending applications (data.ny.gov)
• Florida (DBPR ABT) — licensed-file extract, active licenses (myfloridalicense.com)
• California (ABC) — issued licences + open applications from ABC's daily data export, with every CA application flagged as a new premises or a transfer at an existing licensed premises (see "California" below)
• Washington (LCB) — new-license application notices from the LCB's statewide 30-day report, with contact phone and named applicants
• Oregon (OLCC) — liquor applications still in progress (data.oregon.gov)
• Connecticut (DCP) — pending liquor permits, with the permittee and the backer's address (data.ct.gov)
• Colorado (LED) — recently approved liquor licenses (data.colorado.gov)
• Missouri (ATC) — new liquor licenses (data.mo.gov)
• Chicago, IL — newly issued city liquor licenses (data.cityofchicago.org)

All sources are official, keyless open-data endpoints — no logins, no keys.

Coverage

Measured live on 2026-09-25. "Rows" is what the source holds for the feed as this actor scopes it.

Key	Source	Feeds	Freshness (newest date seen)	Rows	Notes
TX	TABC License Information + Pending Original Applications (data.texas.gov)	active, pending, closing	daily	closing: 2,144 status changes in the 90 days to 2026-09-26	active rows carry opened_verified from the Comptroller's Mixed Beverage Gross Receipts (naix-2893, 3.85M filings, newest period 2026-09-30)
NY	SLA Active Licenses + Pending Applications (data.ny.gov)	active, pending	daily	—	unchanged; no closing feed (current-active list only)
FL	DBPR ABT bd4006lic.csv	active	daily	—	no pending feed published; no closing feed (no terminal status column)
CA	ABC DailyExport-CSV.zip	active, pending	each business morning	~129k export rows	pending has no date (file-number order); no closing feed (surrendered licences carry no date)
WA	LCB statewide "New License Applications" report	pending	2026-09-25	279 liquor notices / 30 days	renewals, discontinuances and cannabis-only notices removed (see below); no county; no closing feed (see "Checked and not added")
OR	OLCC Liquor Applications Received (qad4-bnxp) + OLCC Liquor Non-Renewals (mhc6-qsxj)	pending, closing	2026-09-24 / daily	232 open / 870 non-renewals (505 expired, 365 lapsing)	no separate city, no applicant name, no application id on applications; non-renewals carry licence number (all but one row), licensee and local governing body
CT	DCP Liquor Permits, status PENDING (gwv2-eswx)	pending	refreshed daily	339	no date published; brand-label registrations removed
CO	LED Recently Approved Liquor Licenses (htyp-tqzh)	active	2026-08-31	504	rolling ~3-month window; no county
MO	ATC New Liquor Licenses (dymb-xy5c)	active	2026-09-24	1,372	includes out-of-state solicitor licences
IL-CHICAGO	City of Chicago Business Licenses, liquor rows (r5kz-chrr)	active, closing	2026-09-24 / 2026-09-25	7,359 issued since 2002 (99 since 2026-06-01) / 3,900 cancelled or revoked (29 in the last 90 days)	city only, not statewide Illinois; no county

What each new source cannot tell you is left null, never guessed:

• WA — the report publishes a notification date (when the LCB notified the local authority), not the filing date: it goes in application_date with recency_basis: "lcb_notification_date". No county, no application status. The LCB's own page carries the banner "This report contains errors due to a known data transfer issue"; the visible error is that 1,976 of 2,407 records in its "new applications" section are renewals, which this actor removes, along with 120 liquor-sales discontinuances and 32 cannabis/tobacco-only notices.
• OR — no application id and no applicant name are published; the city sits inside a one-line address, so city is null and a city filter is matched against that address. Only applications still open (not Approved / Inactive / Withdrawn / Cancelled / Expired / Rejected) are returned. OLCC files a change of ownership as a "New Application" too, so application_kind is only set for amendments.
• CT — pending permits carry no date at all. Rows are ordered by the credential's sequence number (recency_basis: "credential_sequence_proxy"; sequences are per permit class, so this is approximate) and a sinceDate cannot be applied to CT (the leg is reported as failed, never silently emptied). 111 pending "LBD" rows are brand-label registrations (product names, not premises) and are excluded. Duplicate credential rows are collapsed with the count in source_duplicate_rows.
• CO — 98 of the list's rows carry impossible issue years (2048–2262) and would otherwise sort first; only rows issued on or before the run date are returned. Person registrations ("Associated Person") and tobacco licences are excluded.
• MO — the source publishes its date as MM/DD/YYYY text, which a server can only sort month-first, so the whole list (~1.4k rows) is read and ordered by the real date.
• Chicago — only first-term (ISSUE) liquor licences in issued status; renewals (70,687 rows) are excluded. Rows carry state: "IL" and jurisdiction: "Chicago".

Checked and not added (2026-09-25)

Candidate	Why not
Pennsylvania (PLCB)	Only the PLCB+ interactive licence search form (plcbplus.pa.gov/pub/Default.aspx?PossePresentation=LicenseSearch); no bulk list or open-data dataset.
Illinois statewide (ILCC)	The licence lookup is a Salesforce Experience page behind reCAPTCHA; no bulk list. Chicago's own city data is covered instead.
Michigan (MLCC)	A weekly Master-License-List.xlsx exists (35,872 licences, updated 2026-09-17) but carries no date of any kind, so it cannot say which licences are new; left for a delta-only leg later.
Ohio (Division of Liquor Control)	Permit lookup is a search application (host did not answer from here); no bulk file found.
Montgomery County, MD (ABS)	1,084 licensees, no date column at all.
New Orleans	Alcohol Beverage Outlets dataset last updated 2025-08-17 (over a year old).
Washington renewal / local-authority datasets on data.wa.gov	Renewals are not openings; the local-authority letters dataset holds only the latest batch (11 rows).
Closing feed for NY, FL, CA, WA, CO, MO, CT (2026-09-26)	NY publishes the current active list only (an expiration date there is a renewal date, not a closing). FL's licensed-file extract has no terminal status. CA's export marks surrendered licences but carries no surrender date, so "newest closings first" cannot be built. WA's LCB report does have a DISCONTINUED LICENSES section (450 records) but publishes the licence type only as a numeric privilege code ("450, ") with no published code table (the fee page is a 404) — cannabis and liquor discontinuances cannot be told apart, and a cannabis retailer closing sold as a bar closing is exactly the wrong answer this actor must never give. CO, MO and CT publish approved / new / pending lists only. Asking any of them for feed: "closing" reports the reason on every row (run_legs_failed_reason) rather than returning an empty success.

The closing feed — venues going dark (new in 1.1, 2026-09-26)

{"states": ["TX", "OR", "IL-CHICAGO"], "feed": "closing", "maxResults": 200} returns licences that have expired, been surrendered, cancelled or revoked, or are lapsing without a renewal, newest first. It is a separate feed: feed: "all" still means pending + active, exactly as before, so an existing schedule never receives closing rows it did not ask for.

State	Source	closing_kind values	closing_date is	Ordering
TX	TABC License Information, license_status in Expired / Expired - Original Required / Surrendered / Cancelled / Temporarily Surrendered	expired, surrendered, cancelled, temporarily_surrendered	the date the licence entered that status (status_change_date)	newest status change first
OR	OLCC Liquor Non-Renewals	expired (OLCC says license_expired: Yes), not_renewed (on the non-renewal list, expiry not yet passed or not yet marked)	the renewal date the licence was not renewed by (expiration_date)	nearest to the run date first (recency_basis: "days_from_run_date"): licences lapsing in a few days, then those that lapsed most recently — a plain newest-date-first order put 20 odd rows marked expired against a 2027 renewal date on top
IL-CHICAGO	City of Chicago Business Licenses, liquor rows with license_status AAC / REV	cancelled, revoked	license_status_change_date	newest first

What the rows tell you, and what they do not:

• closing_stage is past when the closing date has passed and upcoming when it is still ahead — Oregon lists licences before their renewal date lapses (on 2026-09-26, 345 licences were listed unrenewed against a 2026-09-30 renewal date), which is a pre-closing signal. license_expiration_date is the licence's own expiration as published.
• TX "Suspended" is not a closing (an enforcement action) and is excluded. "Expired - Original Required" means the licence lapsed long enough that a brand-new application is needed — TABC processes these in batches about 30 days after the expiration date, so many rows share one closing_date.
• OR publishes no separate city: city is OLCC's local governing body when it is a city, county when it is a county (JACKSON COUNTY → county JACKSON). renewal_status_raw, renewal_received_date and inactive_date are carried where OLCC publishes them (5, 5 and 22 of 870 rows on 2026-09-26). One row has no licence number; its delta key falls back to (trade name, premises address, licence type).
• Chicago cancelled licences usually sit on a RENEW term row (application_type_raw), not an ISSUE row, so the closing feed is not restricted to first-term rows the way the active feed is.
• Before any closing row is fetched, each source is count-probed: its own scoping must match at least a floor (OR 200, TX 5,000, Chicago 500 rows — all well under the live counts) and a negative control must match 0. A source that fails the probe is reported as failed on every row; if every requested source fails, the run fails and bills nothing.
• In mode: "delta" a closing key first seen after the baseline is emitted as event_type: "closing_detected".

Billing on closing rows. Every row of every feed carries the Result event at the actor's unchanged price. From 2026-10-11 a closing-feed row additionally carries one closing-detected event ($0.03 list, discounted on paid plans) — Apify requires 14 days' notice before a new event takes effect, so until that date closing rows bill the Result event only. The event is charged before the row is written, and every row states what it was billed as in billed_event (result or result+closing-detected), so you can see which applied. Rows of the pending and active feeds never carry the extra event, so an existing schedule's invoice is unchanged by this release. If the run's charge limit is reached mid-feed, the closing rows that could not be charged are not emitted (the run log says how many).

Texas opened_verified — a licence is a permit; a receipts filing is proof (new in 1.1)

Every Texas active row is joined to the Texas Comptroller's Mixed Beverage Gross Receipts filings (data.texas.gov/resource/naix-2893, 3.85 million monthly filings): the permit number is TABC's licence type + licence id (MB200143114), which is exactly the Comptroller's tabc_permit_number. Switch it off with "verifyOpenings": false.

opened_verified	Meaning	receipts_status
true	at least one monthly period with receipts > 0 has been filed — the venue is provably selling	receipts_filed
false	the permit class owes the tax, at least two obligation periods have come due since issue (a period is due 20 days after its month end), and no period carries receipts	no_filing_after_due_periods, filed_zero_receipts_only
null	too early to tell (not_yet_due, filed_zero_receipts_not_yet_due), the issue date is unknown, or the permit class never files — beer/wine retailers (BG/BE), package stores (P/Q/BQ) and wholesalers have no mixed-beverage obligation, so their silence proves nothing (not_subject_to_mixed_beverage_tax)	as listed, plus receipts_predate_license_only (every filing is older than this licence), not_requested, not_applicable (TX pending/closing rows), not_checked_deadline, lookup_failed, source_unavailable, source_drift

Only the classes that actually file — measured on the August 2026 period: MB 17,755 / RM 1,917 / N 577 / NE 266 / D 240 / NT 48 / NB 10 / TB 3 / FB 1, and nothing else — are ever judged. On 40 recently issued permits, 28 had filings; all 12 without were BG/BE, which is why those read null, never false.

The row also carries first_receipts_period (the month the venue started selling), latest_receipts_period, receipts_periods_filed / receipts_periods_positive (a $0 filing is a filing, not a sale — 2 of the 28 joined permits had only $0 periods), trailing_12_receipts (USD over the 12 periods ending on receipts_latest_complete_period), and receipts_rank_in_county / receipts_rank_in_county_of (rank by trailing-12 receipts among permits with receipts in the same Comptroller county code, receipts_county_code; Harris = 101). The newest period is still filling until the 20th of the following month (123 rows for 2026-09-30 against 20,817 for 2026-08-31 on 2026-09-26), so the trailing window ends on the newest complete period, and receipts_source_as_of says how current the dataset was. receipts_predate_license: true flags a permit number whose receipts history starts before this licence's issue date — TABC re-issued the number to a continuing business. When every positive period predates the issue date (measured live: a permit issued 2026-09-25 whose only filing is from 2012), the receipts belong to the previous holder and the verdict is null with receipts_status: "receipts_predate_license_only", never true.

The join is corroborating, not load-bearing: it runs under its own 120-second deadline, and any failure (source down, drift, deadline) becomes a disclosed receipts_status with a null verdict — it never fails the run and never bills anything extra. Two obligation periods is a deliberate threshold: a permit issued mid-month has its first return due seven weeks later, and a single missed month is not evidence of anything.

Who buys these leads (who it's for)

• Beverage distributors & brand reps — reach a new bar before the first order is placed.
• POS, payments & reservation platforms — new restaurants buy their stack in the pre-opening window.
• Insurance agents (liquor liability, GL) — every new license needs coverage, often as a condition of the license.
• Food-service suppliers, equipment dealers, linen/hood-cleaning services — pre-opening procurement.
• Commercial real-estate & market analysts — track hospitality openings by city/county.
• AI sales agents — use it as an MCP tool to keep a CRM topped up with pre-opening leads.

Example input

{
  "states": ["TX", "NY"],
  "mode": "inventory",
  "feed": "pending",
  "maxResults": 200
}

West-coast pre-opening leads: {"states": ["WA", "OR", "CA"], "feed": "pending", "maxResults": 150}.

Lead-feed setup: schedule the actor daily with "mode": "delta" and "feed": "all" (pending + active), and a second daily schedule with "feed": "closing" for the venues going dark: {"states": ["TX", "OR", "IL-CHICAGO"], "feed": "closing", "mode": "delta", "maxResults": 500}.

Revenue-verified new bars in Harris County: {"states": ["TX"], "feed": "active", "county": "Harris", "maxResults": 100} — filter the output on opened_verified: true.

Fixed in 1.1 (2026-09-23): delta mode now keeps its baseline between runs. Before 1.1 the baseline was written to the run's own temporary storage, so every delta run started empty, re-emitted its whole slice as event_type: "inventory", and billed it again, and no change event could ever fire. The baseline now lives in a named store (liquor-license-new-openings-tracker-baseline) under a key built from your states, feed, city, county and sinceDate, so two differently-filtered schedules never overwrite each other. Existing delta schedules get one more "inventory" run to seed the baseline, then real change events from the run after. The first run seeds a baseline (event_type: "inventory"); every later run emits only new_application, newly_issued, and status_change events — each one a fresh lead. WA keeps only 30 days and CT publishes no dates, so for those two a daily delta schedule is the way to catch every new application.

Other useful inputs: "city": "Austin", "county": "Bronx", "sinceDate": "2026-06-01".

Several states in one run

• maxResults is shared fairly. Each source gets an even share of what is left, so a source that returns fewer rows than its share passes the rest to the next one. (Before 2026-09-25 the cap was split up front: {"states":["TX","NY"],"feed":"pending","city":"Brooklyn","maxResults":10} returned 5 rows, because Texas's unused half was thrown away.) A source never queried because the cap was already used up is listed in run_legs_not_queried.
• A state that does not publish the feed you asked for is reported, not dropped. {"states":["FL","TX"],"feed":"pending"} returns the Texas rows with run_complete: false and run_legs_failed_reason: "FL/pending: no \"pending\" feed published (has: active)". (Before 2026-09-25 Florida simply vanished and the run read run_complete: true.) The run only fails if no requested state can answer.
• A filter a source cannot apply is refused for that source, not ignored. county is published by TX, NY, FL, CA and MO only; asking for county: "King" with WA fails the WA leg (disclosed on every row) instead of returning all of Washington as if it were King County.

sinceDate must be YYYY-MM-DD

sinceDate is a date predicate: it is spliced into the live Socrata $where clause on the Socrata legs and compared against issue_date / application_date on the file-based legs. Both comparisons are on ISO date strings, so a value in any other format does not error — it silently returns the wrong set.

Accepted: 2026-01-15 and 2026-1-15 (single digits are padded). Leave it blank or omit it for no date filter — that is not an error and is not a default.

Anything else fails the run before any source is contacted, so nothing is billed. Slash forms are rejected on purpose rather than guessed: 05/06/2026 is genuinely ambiguous between US month/day and EU day/month order, and guessing produces a plausible wrong window instead of a visible error.

Measured against a 3-row fixture (2020-06-15, 2023-03-01, 2025-02-10) where the correct answer for a 2023-01-01 floor is 2 of 3:

You send	What it used to return	Why
01/15/2023	3 of 3 — the whole set, labelled as filtered	"01/…" sorts below every "20xx-…", so the predicate is true for everything
Jan 2023	0 of 3 — "nothing matched since Jan 2023"	"Jan…" sorts above every "2…", so the predicate is false for everything

Two more worth knowing, both now rejected or corrected: unpadded 2023-1-1 returned 1 of 3, silently dropping every month 01–09 (it is padded to 2023-01-01 before use); and 2023-13-45 — an impossible calendar date that satisfies a shape-only pattern check — returned 1 of 3, a plausible-looking wrong subset.

This matters most to AI agents calling the actor as an MCP tool: a date is exactly the value an agent formats however it likes, and neither failure mode is visible in the output.

Output fields

Each record is one license or application:

Field	Meaning
state	TX / NY / FL / CA / WA / OR / CT / CO / MO / IL (Chicago rows are IL with jurisdiction: "Chicago")
feed	pending (application — pre-opening lead) or active (issued)
event_type	inventory, new_application, newly_issued, status_change
business_name	Trade name / DBA (falls back to owner/legal name)
owner_name	Owner / legal entity (null where not published, e.g. OR)
premise_address, city, county, zip	Licensed premises location (null where the source does not publish the part)
license_number	License, permit, credential or application id (null for OR, which publishes none)
license_class_raw / license_class_label	State class code + decoded label
business_type	Decoded: bar, restaurant, package_store, manufacturer, wholesaler, club, other
status / previous_status	Current status (+ prior status on status_change events). CT: the permit's review stage. WA: null (not published)
issue_date / application_date	Normalized YYYY-MM-DD (WA: LCB notification date)
source, source_url	Upstream registry provenance
run_legs_requested / run_legs_ok / run_legs_failed / run_legs_failed_reason	Which state/feed sources this run asked for, which answered, which failed and why (including a state that does not publish the requested feed)
run_complete	true only when every requested source answered. false means at least one failed or could not answer, so a missing state is not "no licences there"
run_legs_not_queried	Sources never queried because maxResults was already used up by earlier sources (not a failure)
mailing_address	Mailing/owner address where published: CA licensee mailing address, CT backer address. Null elsewhere
source_data_as_of	CA: the date printed on ABC's daily export. Null for other states
application_kind	new_premises (a genuinely new licence / premises) or existing_licensed_premises (a transfer, relocation or change on an existing licence). Set for CA pending, WA, and OR amendments; null where the source cannot tell
application_type_raw	The source's own application / action type (WA NEW APPLICATION / ASSUMPTION / CHANGE OF LOCATION …, OR New Application / Amendment …, Chicago ISSUE). Null elsewhere
recency_basis	How "newest first" was decided: issue_date, date_received (OR), lcb_notification_date (WA), file_number_proxy (CA pending), credential_sequence_proxy (CT); closing feed: status_change_date (TX), license_status_change_date (Chicago), days_from_run_date (OR). Null for TX/NY/FL active and pending
source_duplicate_rows	CA and CT: how many source rows were collapsed into this one (1 = unique). Null elsewhere
phone	Contact phone (WA). Null elsewhere
applicants	Named applicants / permittee (WA, CT). Null elsewhere
jurisdiction	City for a city-level source (Chicago); null for statewide sources
closing_kind	Closing feed: expired, not_renewed, surrendered, temporarily_surrendered, cancelled, revoked. Null on other feeds
closing_stage	Closing feed: past (the date has passed) or upcoming (an OR licence lapsing on a future renewal date). Null without a date
closing_date	Closing feed, YYYY-MM-DD: TX status-change date, OR expiration/renewal date, Chicago status-change date
license_expiration_date	Closing feed: the licence's own expiration date as published
renewal_status_raw / renewal_received_date / inactive_date	OR closing rows, where OLCC publishes them (Payment Pending; YYYY-MM-DD). Null elsewhere
billed_event	result (every row) or result+closing-detected (a closing-feed row that also carried the closing-detected event)
receipts_permit_number	TX active: the Comptroller permit number used for the receipts join (licence type + id, e.g. MB200143114)
opened_verified	TX active, three-valued: true receipts filed, false due periods passed with no receipts, null cannot say (see the section above)
receipts_status	Why opened_verified reads what it does (vocabulary in the section above). Null on non-TX rows
first_receipts_period / latest_receipts_period	TX: first and latest monthly period (month end) with receipts > 0
receipts_periods_filed / receipts_periods_positive	TX: monthly periods with any filing / with receipts > 0. 0 = looked up, none; null = not looked up or not a taxable class
trailing_12_receipts	TX: total receipts (USD) over the 12 periods ending on receipts_latest_complete_period
receipts_rank_in_county / receipts_rank_in_county_of	TX: rank by trailing-12 receipts among permits with receipts in the same county code (1 = largest) / that count
receipts_county_code	TX: the Comptroller's numeric county code on the filings (Harris = 101)
receipts_latest_complete_period / receipts_source_as_of	TX: the newest complete obligation period (window end) / the newest period present in the dataset at run time
receipts_predate_license	TX: true when receipts start before this licence's issue date (permit number re-issued to a continuing business)

Use as an MCP tool

This actor is callable by AI agents (Claude, Cursor, etc.) via mcp.apify.com — the input and output schemas are fully described at field level, so an agent can query "new bar applications in San Antonio since June" and pipe the leads into a CRM without custom glue code.

FAQ

How early are pending-application leads? States require the license before alcohol service, and applications are filed while the venue is in build-out — typically 60–90 days pre-opening (varies by state and class).

Which feed should I use for lead generation? feed: "pending" for the earliest signal (TX, NY, CA, WA, OR, CT); feed: "all" + mode: "delta" on a daily schedule to also catch the moment a license is actually issued (newly_issued). CO, MO and Chicago publish issued licences only.

Is California included? Yes, from 1.1. The CA leg reads ABC's own daily data export (DailyExport-CSV.zip, refreshed each business morning, about 129,000 rows), downloaded once per run for both feeds:

• active: licences with status Active, newest issue date first. sinceDate filters on the issue date. On 2026-09-23 the export held 102,839 active licences, 540 of them issued in the prior 30 days.
• pending: open applications (surrendered ones excluded), newest ABC file number first. ABC publishes no application date at all, so rows carry application_date: null and recency_basis: "file_number_proxy" (file numbers rise over time). A sinceDate cannot be applied to CA pending: rather than silently returning nothing, that source is reported as failed on every row (run_legs_failed). To catch new CA applications, schedule mode: "delta".
• application_kind is the field that matters for lead generation: of 18,868 open CA applications on 2026-09-23, 11,182 were new premises and 7,686 were transfers or changes at a premises that already holds a licence. Filter on new_premises for pre-opening leads.
• One ABC file can carry several licence types (a restaurant's type 47 plus a caterer's permit); each is its own row. Rows the export repeats for the same type, file and licence/application flag are collapsed, and the count is shown in source_duplicate_rows.
• Licence types are decoded from ABC's published list. A code not on that list keeps its raw value, gets a null label and is typed other, never guessed.

What does Florida cover? The FL leg reads the DBPR ABT licensed-file extract bd4006lic.csv (active beverage licenses; the sample profession file). Sibling extracts (bd4005/bd4002 — additional beverage series) and a pending signal are planned for v1.1. FL contributes to the active feed only.

What happens if my states/feed combination matches no source? The run fails before any network call and bills nothing, with a message naming the problem — e.g. states: ["FL"] with the default feed: "pending" fails with No "pending" feed for FL (has: active) — use feed "active" or "all". If at least one requested state can answer, the run proceeds and the others are listed in run_legs_failed on every row. A zero-row SUCCESS is reserved for the case where every requested source was actually queried and honestly returned nothing.

How is business_type decoded? Per-state maps: CA ABC licence types from ABC's own list (41/47→restaurant, 40/42/48/61→bar, 20/21/85→package_store, 17/18 and importers→wholesaler, 01/02/23/74…→manufacturer, 50/51/52→club), TX TABC permit codes (MB→bar, RM→restaurant, P/Q→package_store, W/X→wholesaler, N→club, BB/BW/G→manufacturer…), NY SLA class descriptions (Restaurant, Tavern, Grocery/Liquor Store, Wholesale, Farm/Winery…), FL series patterns (…COP→bar, …SRX→restaurant, …APS/PS→package_store, 11xx→club), CT credential prefixes confirmed by DCP (LIR/LRW→restaurant, LCA/LCW→bar, LIP/LGB→package_store, LIC/LPC→club), and keyword rules on the published licence names for WA, OR, CO, MO and Chicago. Unknown codes are kept raw and typed other — nothing is dropped.

Does an empty result cost anything? Pricing is per result record. A delta run where nothing changed emits 0 records and costs only the platform's minimal run overhead.

What does a closing row cost? The Result price every row has always carried, plus — from 2026-10-11, after Apify's 14-day price-change notice — one closing-detected event ($0.03 list price, discounted on paid plans). Only rows of the closing feed carry it; billed_event on every row says which. Pending and active rows are billed exactly as before 1.1.

Can I get closings for New York, Florida, California or Washington? Not yet — their sources do not publish a dated terminal status (see "Checked and not added"). Asking for them reports the reason on every row of the run; if none of the requested states can answer, the run fails before any request and bills nothing.

Why does opened_verified read null on a Texas beer-and-wine bar? Because a BG/BE licence has no mixed-beverage tax obligation, so the absence of a filing is not evidence. Only MB, RM, N, NE, NB, NT, D, FB and TB permits are ever judged; the rest read receipts_status: "not_subject_to_mixed_beverage_tax".

Is this legal to use? All data comes from official state and city open-data portals published for public reuse. Verify license details with the issuing authority before relying on them for compliance decisions; this is a lead-generation and monitoring tool, not legal advice.

Related actors

Other lead feeds from the same catalogue for the same buyer: distributors, insurance agents, POS and food-service sellers working new hospitality openings. The Where both cover column lists only the places both actors actually serve (see each actor's own Coverage table).

Actor	What it adds for you	Example workflow	Where both cover
Parcel Owner Lookup	The owner of record and owner mailing address of the building behind a licence, from the official assessor roll	A new licence at a Denver premises: pass premise_address to Parcel Owner Lookup to reach the landlord as well as the operator (useful for CRE brokers and property insurers)	Colorado (41 counties, incl. Denver), Connecticut, New York (statewide incl. NYC), Chicago (Cook County), Houston (Harris County, TX)
City Business License Leads	Every other newly licensed business in five cities, with NAICS codes where the city publishes them	Liquor licences cover the bars; add the new restaurants, cafes and food businesses from the same cities in the same week. In Chicago both read the city's r5kz-chrr dataset: this actor keeps first-term liquor licences, City Business License Leads returns every licence type	Chicago, Los Angeles and San Francisco (CA), New York City, Seattle (WA)
Secretary of State Business Monitor	Formation date, status and registered agent of the LLC or corporation named as owner_name	A pending application names an LLC: search that name in the state registry to see how new the entity is and who its registered agent is	CO, CT, NY (OR is covered by both, but OLCC publishes no owner name, only the trade name)
KYB Company Verifier	A registry verification (found / not found / not checked) of the licensee entity	Before adding a new licensee to your CRM or extending trade credit, confirm the owner entity is registered (NY and OR check active entities only)	CO, CT, NY (OR likewise, trade name only)
Childcare Provider Leads	A second vertical for the same outbound motion: licensed childcare programs with phone, email and named director	Insurance, food-service and POS sellers already working liquor leads can run childcare centres in the same states	TX, NY, CA, WA, CT