Pest Control License Scraper

Pest Control License Scraper turns 16 separate state government license lookups — normally a slow, manual, one-state-at-a-time chore — into a single structured dataset of every actively licensed pest control business across Colorado, Delaware, Florida, Indiana, Kentucky, Maine, Michigan, Minnesota, Missouri, New Mexico, New York, North Carolina, Ohio, Oregon, Texas, and Virginia. Every record comes straight from a state's own public license-lookup site (no login, no paywall) — this Actor just automates the lookup, page by page, including five states that only render their data through a live browser or an embedded report rather than a plain webpage. Run it on the Apify platform to get scheduled refreshes, instant API/webhook access to results, automatic proxy rotation, and full run monitoring — no server or browser to maintain yourself. Just 11 of the 16 states already add up to over 30,000 individual license records — see the real per-state counts below.

This is an independent, unofficial tool. It is not affiliated with, endorsed by, or operated on behalf of any state government, agency, or board named in this README — it only reads pages those agencies already publish for free, public lookup.

Why use Pest Control License Scraper?

Turn newly issued licenses into a live deal-sourcing feed

A state license board is often the first public trace that a new pest control business exists — before it has a website, before it appears in any business directory, before a competitor even notices. Schedule this Actor to run weekly or monthly and diff each pull against the last one, and you get a rolling feed of brand-new market entrants and freshly renewed operators: an early-mover signal most sourcing teams currently pick up by accident (a referral, a trade show) instead of systematically.

State license boards are also the only reliably up-to-date public registry of every actively licensed pest control business in a state — most of these companies are small, local, and otherwise invisible to standard business databases. Put together, that makes this data useful for:

• PE roll-up sponsors & M&A advisors sourcing acquisition targets in fragmented, high-margin local-service verticals — build a state-by-state target list ranked by license tenure, category mix, or expiration (a proxy for renewal/attrition risk), and refresh it on a schedule to catch new entrants as they appear.
• Franchise recruiters identifying independent operators who might convert to a franchise banner — including ones too new or small to show up in a paid business database yet.
• Distributors & suppliers (chemicals, equipment, insurance) building a prospect list of every licensed business in their territory, updated as new licenses are issued.
• Insurers & underwriters verifying a business actually holds an active license before binding a policy.
• Market researchers sizing the number of active operators, license churn, or category mix (termite/WDO vs. lawn & ornamental vs. fumigation) by state or county.

The scale, in real numbers

These aren't estimates — they're actual counts pulled from each state's own system: New York 8,203 · Ohio 5,035 · Texas 5,721 (commercial + noncommercial business reports) · Kentucky 2,862 · Virginia 2,581 · Maine 1,982 · North Carolina 1,662 (business-level license type alone) · Colorado ~1,172 · Oregon 985 · Delaware 669 · Minnesota 262. That's already over 30,000 records across just 11 of the 16 states — and it doesn't include Florida or Michigan, whose Power BI-based rosters are the largest in this build, or Missouri, Indiana, and New Mexico, all of which support statewide (not just per-county) queries.

Why not just check each state site yourself?

Because it doesn't scale past one state. Sixteen boards means sixteen different search forms, column layouts, and pagination styles — and five of them (Delaware, Florida, Michigan, North Carolina, Oregon) only expose their data through a JavaScript-heavy portal or an embedded Power BI report that a plain HTTP request can't read at all, so a simple "view page source" approach silently returns nothing. Building and maintaining that yourself — across 16 government systems that each redesign on their own schedule — is realistically a multi-week engineering project, then an ongoing maintenance burden. This Actor already did that work and gets fixed centrally when a state changes something; you get one consistent schema across all of them instead of the upkeep.

How to use Pest Control License Scraper

1. Click Try for free (or Run) on this Actor's page.
2. In the Input tab, pick which state(s) to pull from the states list — or leave the default to start with New York.
3. Optionally narrow the results with a searchTerm, licenseTypeFilter, or statusFilter, and set maxItemsPerState to cap how many records to pull per state.
4. Click Start and watch the run log — each state logs how many records it found.
5. When the run finishes, open the Output tab to preview, or export the dataset as JSON, CSV, Excel, or HTML.

No coding is required to run it from the Console; developers can also call it via the Apify API or SDKs to integrate results into a CRM, spreadsheet, or data warehouse.

Input

All fields are optional except states. See the Input tab for the full form, or pass JSON directly:

{
    "states": ["NY", "FL", "TX"],
    "searchTerm": "",
    "licenseTypeFilter": [],
    "statusFilter": ["Active"],
    "maxItemsPerState": 500
}

• states — which state boards to query (see the Data table below for the full list).
• searchTerm — filters by business/licensee name where the state doesn't support it natively, results are filtered after fetching.
• licenseTypeFilter — restrict to specific license categories.
• statusFilter — restrict to specific statuses (default: Active only).
• maxItemsPerState — upper bound on records pulled per state per run (default 500).

Output

Each result is one license record, pushed to the dataset in real time as each state finishes. Example item:

{
    "state": "FL",
    "licenseNumber": "JB6655",
    "licenseeName": "\"BO KNOWS\" PEST CONTROL INC",
    "businessName": "\"BO KNOWS\" PEST CONTROL INC",
    "licenseType": "General Household Pest and Rodent Control, Termite and Other WDO Control",
    "status": "Active",
    "city": "PORT SAINT JOE",
    "county": "Gulf",
    "address": "609 10TH ST",
    "issueDate": "1998-07-27",
    "expirationDate": "2026-07-31",
    "disciplinaryFlag": false,
    "sourceUrl": "https://aeslicensing.fdacs.gov/Reports/PBI---Company-License/",
    "scrapedAt": "2026-07-09T23:05:57.718Z"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel from the Output tab, or pull it programmatically via the Dataset API.

Data table

Field	Description
state	Two-letter state postal code
licenseNumber	State-issued license/registration number (or the state's closest equivalent identifier)
licenseeName	Name on the license record
businessName	Business/DBA name, when the state exposes one separately from the licensee name
licenseType	License category or class (e.g. termite/WDO, lawn & ornamental, fumigation)
status	Active, Expired, or another state-specific status label
city / county	Business location, where published
address	Street address, where published
issueDate / expirationDate	ISO YYYY-MM-DD dates, where published
disciplinaryFlag	Reserved for future disciplinary-action data; currently always false (no state in this build exposes a matching field)
sourceUrl	The exact page/report the record was read from
scrapedAt	UTC timestamp the record was collected

States covered: CO, DE, FL, IN, KY, ME, MI, MN, MO, NM, NY, NC, OH, OR, TX, VA. Two additional codes (AL, MD) are accepted as input but currently return no data — both boards are confirmed public but blocked by a bot-mitigation layer (Cloudflare Turnstile on MD; a persistent server-side error on AL) that this Actor does not attempt to bypass.

How much does it cost to scrape state pest control license data?

This Actor runs on Pay Per Event pricing: $2.00 per 1,000 results, plus a small $0.02 flat fee per run — that's the whole bill. Platform compute costs are included in that price, not billed separately, so the number you see before you run it is the number you pay; five of the sixteen states (DE, FL, MI, NC, OR) drive a real headless browser under the hood and cost more to run than the other eleven, but that's absorbed into the flat per-result price rather than passed through as a variable line item. A default run (500 records per state) costs a few dollars; pulling a full state's roster (e.g. New York's 8,000+ records) costs roughly the same as a cup of coffee. Apify Store subscribers on paid plans get this Actor's price automatically discounted — up to 75% off at the top tier. Apify's free tier is normally enough to try every state at a modest maxItemsPerState.

Tips for scraping state license boards efficiently

• Start with a small maxItemsPerState (e.g. 50) to sanity-check a state before committing to a full pull.
• Run the Cheerio-based states (CO, IN, KY, ME, MN, MO, NM, NY, OH, TX, VA) separately from the five browser-driven states (DE, FL, MI, NC, OR) if you want faster turnaround — the Cheerio states finish in seconds, while the Playwright states take longer per record (pricing is the same flat rate either way, this only affects run time).
• Use statusFilter: [] (empty) to pull every status the state publishes, not just Active.
• Schedule recurring runs (daily/weekly) via Apify Scheduler to track new licenses and renewals over time — pair with a dedupe step on licenseNumber if you want a rolling incremental feed.

FAQ

Is this legal? This Actor only reads pages state agencies already publish for free, public lookup — the same pages a person could browse and read by hand. It does not create accounts, submit forms with personal data, or bypass any login, paywall, or CAPTCHA. You're responsible for using the output in line with each state's terms of use and applicable law.

Why do some states have fewer fields than others? Each state publishes a different amount of detail — some list a full street address, others only a county; some expose separate business and licensee names, others only one. The Actor never invents a value; a missing field is null.

Why does disciplinaryFlag always say false? None of the 16 states in this build expose a disciplinary/enforcement-action field on their public license-lookup pages. It's kept in the schema for forward compatibility if a state adds one, or a future update adds a state that does.

A state stopped returning data / a site changed. State sites occasionally redesign or move. Please open an issue on this Actor's Issues tab with the state code and what you're seeing, and it'll get investigated.

Can you add another state, or build a custom feed for my exact use case? Yes — reach out via the Issues tab or Apify's contact options to discuss a custom build (additional states, extra fields, dedupe/enrichment, or delivery straight into a CRM).