DEV Community: Loomwise

Texas Building Permit Leads: 10,910 Permits from Austin, San Antonio, Collin County and More

Loomwise — Wed, 21 Oct 2026 14:06:26 +0000

Texas cities publish their building permits as open data, but each uses a different portal and schema. Austin is on Socrata and San Antonio on CKAN; Tyler and Hutto use ArcGIS, and Collin County's permits come from its appraisal district. I pulled 30 days from all six and normalized them into one table.

Window: permits issued Sep 20 to Oct 19, 2026. Total: 10,910 permits.

By source

Source	Permits (30 days)	With contractor name	Median job value*	Top work categories
Austin	4,412	42%	$1,000	Electrical (1430), Plumbing (1073), Mechanical / HVAC (743)
San Antonio	4,860	27%	$300,000	Addition / alteration (991), Sign (225), Scaffold / shed / fence (80)
Collin County (appraisal district)	674	5%	$19,188	New construction (330), Roofing (73), Structural / foundation / earthwork (46)
Tyler	486	40%	$12,000	Electrical (141), Plumbing (106), Mechanical / HVAC (51)
College Station	417	0%	$12,262	Mechanical / HVAC (88), Plumbing (77), Electrical (68)
Hutto	61	0%	n/a	New construction (18), Plumbing (8), Mechanical / HVAC (6)

* Median of the permits that report a value. Austin often puts the project-level value on every sub-permit, or $0–$1 on trade permits, so treat its values as rough. San Antonio reports a value on only about 1% of permits.

What kind of work

Work category (normalized)	Permits
Other	3919
Electrical	1643
Addition / alteration	1604
Plumbing	1303
Mechanical / HVAC	927
New construction	842
Sign	244
Demolition	153
Roofing	104
Scaffold / shed / fence	85
Structural / foundation / earthwork	61
Solar	19

"Other" is mostly San Antonio's trade and minor-repair permits, where the permit type alone doesn't say what the work is.

Who is pulling the permits

The most active contractor businesses across the six sources, by business name as published:

Contractor	Permits in 30 days
DOUBLE H LANDSCAPE, LIMITED	98
IES Residential, Inc.	67
In Charge Electrical Services, LLC	61
Victory Plumbing Company	60
Texas Multifamily Solution, LLC	41
Protex Plumbing & Mechanical, LP	40
AEI Electric LLC	40
Charge Pro LLC	38
MJS ENTERPRISES,INC.	36
Clark Wilson Builders INC.	35

This is the B2B angle on permit data. Suppliers, rental yards and staffing firms want to know who is busy right now.

The biggest projects

Austin had several nine-figure permits in the window. These include a public project at 500 E 3rd St ($418.6M listed), a SMART Housing development at 8801 McCann Dr ($245M, Swinerton Builders) and a sports facility at 7401 Loyola Ln ($140M). Large projects appear on many sub-permits, so deduplicate by address before you add values up.

Turning this into leads

Filter by work category (roofing, HVAC, new construction) and a minimum value.
Group by contractor name to find active GCs and subs, or by address to find live job sites.
Re-run weekly. Permits are a time-sensitive signal.

Collin County's data comes from the appraisal district and covers cities like Plano, McKinney, Frisco and Allen. It is heavy on new residential construction: 330 of 674 permits.

Get the same table

All six Texas sources are in the Building Permits Scraper, which covers 47 US cities and counties in one schema. Set "states": ["TX"] to get just these. Each source is also free to query on its own portal, and the README links every dataset.

Jira Cloud has no default comment visibility. Here are 4 workarounds (and a free app)

Loomwise — Tue, 20 Oct 2026 15:29:01 +0000

Every new Jira Cloud comment is "Viewable by All Users" unless someone remembers the lock icon. Atlassian's request for a default (JRACLOUD-9091) sits at 990 votes and is still "Gathering Interest". If your projects include clients or contractors, one forgotten click leaks an internal note.

What actually works today:

Click the lock every time. Free, error-prone.
Automation rule that re-restricts after posting. The rule actor must be a real user in the target role (Atlassian treats the Automation user not joining roles as expected behaviour, JSWCLOUD-22454). Notifications go out before the fix.
REST API POST /rest/api/3/issue/{key}/comment with a visibility object. Atlassian's own KB workaround for team-managed projects (JRACLOUD-83171).
Use JSM if you can: it has real internal vs. reply-to-customer comments.

I build small Forge apps under the name Loomwise, and wrote a free one for this: Loomwise Private Comments restricts new comments to a role or group you choose per project, and runs entirely on Atlassian (Forge, no data leaves your site). Full guide and install: https://loomwise.app/jira-private-comments/

Questions or edge cases: hello@loomwise.app.

New Washington Contractor Licenses in October 2026: 422 Businesses, by City and Trade

Loomwise — Tue, 20 Oct 2026 15:03:17 +0000

Washington State publishes every contractor license it issues as open data. I pulled the licenses that took effect this month and broke them down. The goal: show who is getting licensed, where, and how you can use the list if you sell to contractors.

Data window: licenses with an effective date from Oct 1 to Oct 19, 2026. Source: WA Department of Labor & Industries, Contractor License Data - General on data.wa.gov. Filter: businesses only. Sole proprietors and records that look like personal names are removed.

The headline numbers

422 business contractor licenses took effect in the first 19 days of October, and every one lists a business phone number. About 100 more records in the same window were dropped because they are individuals or have no legal-entity marker in the name.

Caveat: the "effective date" marks the start of the current license term, so the list mixes brand-new businesses with renewals. A UBI (state business ID) you haven't seen before is the best signal that a business is new.

License type	Licenses
Construction Contractor	394
Electrical Contractor	23
Plumbing Contractor	5

Business type	Licenses
LLC	395
Corporation	26
Partnership	1

Specialties

Primary specialty	Licenses
General	322
Residential	11
Painting/Wallcovering	10
Landscaping	8
Floor Covering And Counter Tops	5
Concrete	4
Roofing	4
Heating/Vent/Air-Conditioning And Refrig (Hvac/R)	4
Tile, Ceramic, Mosaic, Natural And Mfg Stone	4
Pressure Washing	4

Most construction contractors register as "General". To find trade-specific leads such as roofers, HVAC or concrete, also check the second specialty and the business name.

Where they are

Business city	Licenses
Spokane	29
Vancouver	28
Seattle	19
Everett	18
Lynnwood	16
Tacoma	15
Bothell	13
Auburn	11
Renton	8
Olympia	7
Puyallup	7
Spokane Valley	7

Business address state	Licenses
WA	369
OR	21
ID	15
CO	3

About 1 in 8 licensees has an out-of-state address, mostly in Oregon (the Portland–Vancouver metro) and Idaho (the Spokane–Coeur d'Alene area).

Who this list is useful for

Insurance, bonding and surety agents. A WA contractor license requires a bond and liability insurance, so every licensee has just bought both.
Payroll, bookkeeping and software vendors looking for young small businesses.
Supply houses and equipment-rental reps working a territory by ZIP prefix (980/981 for Seattle–Bellevue, 992 for Spokane).
General contractors recruiting licensed subs.

Pull it yourself

The dataset is on Socrata, so it has a free SODA API:

curl 'https://data.wa.gov/resource/m8qx-ubtq.json?$where=licenseeffectivedate>="2026-10-01"&$limit=5000'

Then drop rows where the business type is an individual, and check each name for an entity marker (LLC, Inc, Corp...). Don't pull the principal-name column, which holds personal names.

If you'd rather not maintain that, I packaged the query, the business-only filter and the cleanup as a pay-per-result tool: WA Contractor License Scraper ($3 per 1,000 results). Schedule it daily to get each day's new licensees.

Not affiliated with Washington L&I. Data is public and changes daily, so verify a license with L&I before relying on it.

New Federal Contracts This Week: Issue #1 (2026-10-14 to 2026-10-19)

Loomwise — Tue, 20 Oct 2026 13:43:12 +0000

A free weekly roundup of new SAM.gov solicitations, built from SAM.gov's official public data with the Federal Contract Opportunities feed. Not affiliated with GSA or SAM.gov. Always confirm details on the notice itself.

This week: 2,330 new solicitations and combined synopsis/solicitations posted.

Who is buying

Agency	Notices
Dept Of Defense	1,915
Veterans Affairs, Department Of	124
Agriculture, Department Of	57
Interior, Department Of The	53
National Aeronautics And Space Administration	25
Energy, Department Of	24
Homeland Security, Department Of	21
Transportation, Department Of	20

Set-asides

Set-aside	Notices
No set-aside	1,254
Small Business Set Aside - Total	824
Service-Disabled Veteran-Owned Small Business (SDVOSB) Set-Aside (FAR 19.14)	129
Historically Underutilized Business (HUBZone) Set-Aside (FAR 19.13)	50
SBA Certified Women-Owned Small Business (WOSB) Program Set-Aside (FAR 19.15)	33
8(a) Set-Aside (FAR 19.8)	16
Small Business Set Aside - Partial	7

By industry (NAICS sector)

NAICS sector	Notices
33 Manufacturing	1,603
23 Construction	187
54 Professional/technical services	102
32 Manufacturing	87
56 Admin, support & facilities	74
53 Real estate & rental/leasing	67
81 Repair & other services	38
48 Transportation	35

Top places of performance

State	Notices
TX	49
CA	43
WA	27
MD	27
FL	24
DC	23
PA	23
VA	23

Picks: still open, closing soonest (due on or after 2026-10-27)

Service-disabled veteran-owned (SDVOSB) set-asides

53--NUT,MAIN GEAR SKID · Dept Of Defense · NAICS 332722 · location n/a · due 2026-10-27
31--BEARING,ROLLER,ROD END · Dept Of Defense · NAICS 332991 · location n/a · due 2026-10-27
15--PANEL,STRUCTURAL,AIRCR · Dept Of Defense · NAICS 336413 · location n/a · due 2026-10-27
6835-- BULK OXYGEN (Base+4 Option) · Veterans Affairs, Department Of · NAICS 325120 · Long Beach · due 2026-10-27
36-Month Electrical Distribution Testing · Veterans Affairs, Department Of · NAICS 221122 · GA · due 2026-10-27

Women-owned (WOSB/EDWOSB) set-asides

25--TOWBAR,MOTOR VEHICLE · Dept Of Defense · NAICS 336390 · location n/a · due 2026-10-29
30--CONNECTING LINK,RIGID · Dept Of Defense · NAICS 333613 · location n/a · due 2026-10-29
61--TRANSFORMER,POWER · Dept Of Defense · NAICS 334416 · location n/a · due 2026-10-29
59--CONNECTOR,PLUG,ELECTRI · Dept Of Defense · NAICS 334417 · location n/a · due 2026-10-29
10--EC ADAPTER ASSEMBLY · Dept Of Defense · NAICS 332994 · location n/a · due 2026-10-29

HUBZone set-asides

40--CHAIN,STUD LINK · Dept Of Defense · NAICS 332618 · location n/a · due 2026-10-27
53--PIN,SPRING · Dept Of Defense · NAICS 332510 · location n/a · due 2026-10-27
53--NUT,SELF-LOCKING,PLATE · Dept Of Defense · NAICS 332722 · location n/a · due 2026-10-27
68--CALIBRATING GAS MIXTUR · Dept Of Defense · NAICS 325120 · location n/a · due 2026-10-27
29--NOZZLE,FUEL,COMBUSTION · Dept Of Defense · NAICS 336412 · location n/a · due 2026-10-27

8(a) set-asides

13--140D0426Q0641 IDIQ for Law Enforcement Equipment · Interior, Department Of The · NAICS 332994 · location n/a · due 2026-10-29
711th HPW Mission Support Services MAC IDIQ · Dept Of Defense · NAICS 541990 · Wright Patterson AFB, OH · due 2026-10-30
Fort Leonard Wood BASOPS Solicitation · Dept Of Defense · NAICS 561210 · location n/a · due 2026-11-09
EOS Custodial Service · Dept Of Defense · NAICS 561720 · Joint Base MDL, NJ · due 2026-11-15
Recycling Services · Dept Of Defense · NAICS 562920 · location n/a · due 2026-11-16

Construction (NAICS 23)

Airfield Blast Shield · Dept Of Defense · NAICS 238120 · Dyess AFB, TX · due 2026-10-27
LAKE PONTCHARTRAIN & VICINITY (LPV), FORESHORE RISK REDUCTION REPAIRS, REACH-1, 2, 3, & 4 Jefferson Parish, Louisiana (ED 24-006) · Dept Of Defense · NAICS 237990 · LA · due 2026-10-27
Joe Pool Dam Slide Repairs · Dept Of Defense · NAICS 237990 · location n/a · due 2026-10-27
Lone Cone Chinking, GMUG NF, Norwood Road, Colorado · Agriculture, Department Of · NAICS 238390 · Norwood, CO · due 2026-10-27
WV-CANAAN VLY NWR-CHAIN LINK FENCE · Interior, Department Of The · NAICS 236220 · location n/a · due 2026-10-27

IT and computer services (NAICS 5415)

DA10--Circle CVI Software or equivalent in support of VA Portland Healthcare System Portland, Oregon · Veterans Affairs, Department Of · NAICS 541519 · Portland · due 2026-11-03
W50NH9-27-R-A006 (formally W50NH9-26-R-A019) Scalable Geospatial Intelligence (GEOINT) Architecture Information Technology (IT) Contractor Manpower Equivalent (CME) Support (Scalable GEOINT) · Dept Of Defense · NAICS 541519 · location n/a · due 2026-11-13

Get your own version

Want this filtered to your NAICS codes, set-asides and states, every morning? Run the Federal Contract Opportunities feed on a daily schedule. No SAM.gov API key needed; $2 per 1,000 results.

Data: SAM.gov Contract Opportunities public extract (U.S. government work). Counts cover the notice types Solicitation and Combined Synopsis/Solicitation.

Turning Contractor Registrations and Building Permits into a Sales Pipeline

Loomwise — Tue, 20 Oct 2026 12:50:51 +0000

By Loomwise

If you sell to contractors (materials, equipment rental, insurance and bonding, payroll, software), the best lead is a business that has just started a new kind of work. Two public datasets show exactly that, and both are free to query:

New contractor registrations. In New York State, contractors and subcontractors must register with the NYS Department of Labor's Bureau of Public Work and Prevailing Wage Enforcement before bidding on public work or starting a private project covered by prevailing wage. A new certificate means a business is getting ready for that kind of work. The registry is published as open data at data.ny.gov (dataset i4jv-zkey) and refreshed daily.
Newly issued building permits. A permit means a project has been approved and work is about to start at a specific address. Many large cities publish permits on Socrata or CKAN open-data portals, and some include the contractor's business name.

This tutorial turns both into one daily, de-duplicated lead list. You'll filter each source, join them on business name, schedule the run, and send the rows to your CRM or a sheet. You'll also see where the data has gaps.

Step 0: Write down who you're looking for

Settle three things before you touch any data:

Trade: electrical, roofing, solar, HVAC, paving and so on.
Territory: ZIP prefixes or cities.
Disqualifiers: do you want to skip businesses with a debarment or outstanding wage assessments, or are those exactly the ones you sell compliance services to?

Step 1: New registrations as a feed

The NY registry has a lot of fields. For prospecting, the useful ones are the certificate dates, location, and the compliance flags. The examples below use the input format of a ready-made Apify Actor for this registry (linked at the end). You could also query data.ny.gov's API directly.

Input: new electrical contractors in Western New York (ZIP codes starting with 14) over the last 90 days, active certificates only, debarred businesses skipped:

{
  "issuedWithinDays": 90,
  "keywords": ["electric"],
  "zipCodes": ["14"],
  "activeOnly": true,
  "excludeDebarred": true,
  "cleanRecordOnly": false,
  "includeContactDetails": true,
  "maxResults": 500
}

What the filters do:

issuedWithinDays is the certificate issue date window (0 = no limit). For a fixed range, use issuedFrom/issuedTo (YYYY-MM-DD) instead.
keywords matches words in the legal or DBA business name only, not the trade a business registered for. "Electric" finds Example Electric LLC but not Example Holdings LLC doing electrical work. Use several synonyms.
cities is an exact match (case-insensitive). zipCodes matches prefixes (112 = Brooklyn, 14 = Western NY).
businessTypes can be Corporation, LLC, LLP, Partnership, Association or Government.
excludeDebarred (default true) skips businesses that report a state or federal debarment. cleanRecordOnly goes further and keeps only businesses with no outstanding wage assessments, debarments, labor/tax-law determinations or safety violations.
mwbeOnly keeps only businesses that report being minority- or women-owned. This is useful for primes that need MWBE subs.

One output row. The field names are exact, but the values here are made up:

{
  "certificateNumber": "26-XXXXX-CR",
  "businessName": "EXAMPLE ELECTRIC LLC",
  "businessType": "LLC",
  "status": "Active",
  "issuedDate": "2026-10-16",
  "expirationDate": "2028-12-29",
  "businessAddress": "123 EXAMPLE STREET",
  "city": "Buffalo",
  "state": "NY",
  "zipCode": "14201",
  "businessPhone": "(555) 555-0100",
  "mwbeOwned": false,
  "hasWorkersCompInsurance": true,
  "hasOutstandingWageAssessments": false,
  "debarred": false,
  "hasSafetyStandardViolation": false,
  "apprenticeshipAssociated": true,
  "latitude": 42.89,
  "longitude": -78.87,
  "sourceUrl": "https://data.ny.gov/d/i4jv-zkey"
}

The full record also includes dbaName, hasLaborOrTaxLawViolation, workersCompExempt, debarment details (debarmentLaw, debarmentStartDate, debarmentEndDate) and apprenticeship fields. There are two ready-made dataset views: New contractors and Compliance flags.

Ways the flags turn into pitches:

hasWorkersCompInsurance: false or workersCompExempt: true: a lead for insurance and bonding.
apprenticeshipAssociated: false: a lead for apprenticeship programs and training providers.
hasOutstandingWageAssessments: true: a lead for certified-payroll and compliance tools. For primes vetting subs, it's a reason to ask questions first.

Privacy behavior, and why some businesses are missing on purpose. The feed is business-only. Officer names are never requested from the source. Sole proprietorships are always excluded. A row is kept only if the name carries a legal-entity designator (LLC, Inc., Corp., Co., Company, Ltd., LP, LLP, PC, PLLC, DPC, Joint Venture/JV). DBA names are kept only when they carry one too. The address and phone are the registered business address and phone, and includeContactDetails: false removes them. Each run's RUN_SUMMARY record shows how many non-entity rows were dropped. Keep in mind that the registry covers businesses registered for public-work and prevailing-wage projects. It is not a list of every contractor in New York, and it doesn't include NYC home-improvement licenses or local municipal licenses.

Step 2: New permits as a feed

City permit data differs a lot from city to city: field names, refresh schedules, and whether contractors are named at all. A unified schema saves you from writing nine parsers. Here's what the nine cities in the Actor below publish:

City	Refresh	Contractor business name
Chicago, IL	daily	yes
New York City, NY (DOB NOW)	daily	yes (permittee business)
Los Angeles, CA	weekly	not published
San Francisco, CA	daily	not published
Seattle, WA	daily	sometimes
Austin, TX	daily	yes
Boston, MA	daily	rarely (applicant companies only)
Cincinnati, OH	daily	yes
Baton Rouge, LA	daily	yes

Input: roofing and solar permits from the last 2 days in cities that name contractors, only permits that list a contractor business:

{
  "cities": ["chicago", "nyc", "austin", "cincinnati", "baton_rouge"],
  "issuedWithinDays": 2,
  "workCategories": ["Roofing", "Solar"],
  "onlyWithContractor": true,
  "maxResults": 500,
  "maxResultsPerCity": 150
}

workCategories is a normalized category (New construction, Addition / alteration, Demolition, Roofing, Solar, Electrical, Plumbing, Mechanical / HVAC, Fire protection, Sign, Scaffold / shed / fence, Structural / foundation / earthwork, Other). Categories are assigned by fixed keyword rules from each city's permit type and work class, with the description as a fallback. To filter on a city's own wording, use permitTypes (e.g. "Sidewalk Shed", "Commercial").
keywords matches the description, type or work class, e.g. restaurant, ADU, pool, battery.
minValuation keeps permits at or above a declared job value. Permits with no valuation are excluded when this is set, and NYC trade permits often have none.
maxResults is a total cap across cities, newest first. maxResultsPerCity stops one busy city from filling the whole list.

One output row. The field names are exact, but the values here are made up:

{
  "city": "Austin",
  "state": "TX",
  "permitNumber": "2026-XXXXXX RP",
  "permitType": "Building Permit - Residential",
  "workClass": "Repair",
  "workCategory": "Roofing",
  "description": "Reroof, tear off and replace shingles ...",
  "status": "Active",
  "appliedDate": "2026-10-10",
  "issuedDate": "2026-10-17",
  "valuation": null,
  "address": "100 EXAMPLE DR",
  "zipCode": "78701",
  "latitude": 30.27,
  "longitude": -97.74,
  "housingUnitsChange": null,
  "squareFeet": null,
  "contractorBusinessName": "Example Roofing LLC",
  "contractorRole": "General Contractor",
  "contractors": [{ "name": "Example Roofing LLC", "role": "General Contractor" }],
  "permitUrl": "https://...",
  "sourceUrl": "https://data.austintexas.gov/d/3syk-w9eu"
}

Cities publish different fields, and missing values are null, not guesses. The Contractor leads dataset view gives one line per contractor-permit pair. RUN_SUMMARY gives per-city counts and lists any city that was temporarily unavailable. One city being down doesn't fail the run.

Privacy behavior. Owner, applicant and individual-contractor name columns are never requested from the city APIs. Where a city mixes people and companies in one column (Chicago contacts, Boston applicants, Cincinnati company), a name is kept only if it has an entity designator. A string like ACME ELECTRIC CO / JOHN DOE is split and only the company part is kept. Emails and phone numbers in descriptions are masked. The address is the project site, never an owner's mailing address.

Step 3: Join the two on business name (NYC example)

NYC permits name the permittee business, and the NY registry lists businesses registered for public work. If you match the two, you get businesses with active private projects that are also set up for public work, which is a strong signal for suppliers. Names are never typed the same way twice, so normalize them before matching:

import re, json

DESIGNATORS = r"\b(LLC|L L C|INC|INCORPORATED|CORP|CORPORATION|CO|COMPANY|LTD|LP|LLP|PC|PLLC|DPC|JV|JOINT VENTURE)\b"

def norm(name: str | None) -> str:
    if not name:
        return ""
    s = name.upper().replace("&", " AND ")
    s = re.sub(r"[^\w\s]", " ", s)      # drop punctuation
    s = re.sub(DESIGNATORS, " ", s)      # drop LLC, INC, ...
    return re.sub(r"\s+", " ", s).strip()

registry = json.load(open("ny_registry.json"))  # exported dataset (JSON)
permits = json.load(open("nyc_permits.json"))

by_name = {norm(r["businessName"]): r for r in registry}
for r in registry:                              # also match on DBA names
    if r.get("dbaName"):
        by_name.setdefault(norm(r["dbaName"]), r)

matches = []
for p in permits:
    reg = by_name.get(norm(p.get("contractorBusinessName")))
    if reg:
        matches.append({
            "business": reg["businessName"],
            "certificateNumber": reg["certificateNumber"],
            "registeredOn": reg["issuedDate"],
            "permitNumber": p["permitNumber"],
            "workCategory": p["workCategory"],
            "projectAddress": p["address"],
            "permitIssued": p["issuedDate"],
            "permitUrl": p["permitUrl"],
        })

print(len(matches), "matched leads")

Exact matching after normalization misses some real matches and almost never makes a wrong one. If you need more recall, add a fuzzy matcher, and review its matches by hand before they go to sales. For the registry side of a join, use a wider window (issuedWithinDays: 0 or a year of issuedFrom), because a business may have registered long before its next permit.

Step 4: Run it daily without duplicates

Save each input as an Actor task in Apify Console, for example ny-new-electrical-wny and permits-roofing-solar.
Under Schedules → Create new, set a cron such as 0 7 * * *, pick your timezone, add both tasks, and enable the schedule. New schedules start disabled.
Use a 2-day window (issuedWithinDays: 2) so nothing falls between runs, then de-duplicate in your destination:
- registry key: certificateNumber
- permit key: city + permitNumber
Los Angeles refreshes weekly. If you include los_angeles, put it in a separate task with issuedWithinDays: 14 or more, run it weekly, and de-duplicate the same way. Otherwise LA will look empty most days.

To send rows to your tools, use each task's Integrations tab: Gmail (results attached as CSV/Excel), Google Drive file upload, Slack, webhooks, or Make/Zapier with a Google Sheets or CRM step. Daily SAM.gov Alerts in Your NAICS Codes (No API Key), the first post in this series, walks through each of these step by step.

Step 5: Do outreach like a professional

Lead with the signal. "Saw you just registered for public work in Erie County. Here's how we help prevailing-wage contractors with X" beats a generic pitch.
The data is business-only, so keep outreach business-only. Follow the email and calling rules that apply to you (for US businesses, at least CAN-SPAM for email and the TCPA and do-not-call rules for phone). Check with counsel if you're unsure.
Respect the sources' terms. The NY data is published under the OPEN-NY Terms of Use. If you republish Chicago data, Chicago's Data Terms of Use require a specific notice.
Don't treat a flag as a verdict. hasOutstandingWageAssessments and debarred are what the registry reports. Check the official record before you act on it.

The data gaps, all in one place

The NY registry covers public-work/prevailing-wage registrants only. Sole proprietors, and registrations whose name lacks an entity designator, are left out on purpose.
Registry keywords match names only.
LA permits refresh weekly. SF and LA don't publish contractor names. Seattle sometimes does, Boston rarely does.
NYC trade permits often lack a valuation, and minValuation drops permits without one.
workCategory is rule-based. Spot-check the categories you rely on, and use permitTypes when a city's own wording is more precise.

Disclosure: we built the two Actors used here, the New York Contractor Registry Feed ($3 per 1,000 results) and the US Building Permits Feed ($2 per 1,000 results), plus Apify's small Actor-start fee. Both read the official open-data APIs listed above, which you can also query yourself.

Update (Oct 2026): a data-backed follow-up for one state, New Washington contractor licenses in October 2026.

Daily SAM.gov Alerts in Your NAICS Codes (No API Key)

Loomwise — Mon, 19 Oct 2026 13:20:16 +0000

By Loomwise

If you sell to the federal government, the routine is the same every day: open SAM.gov, re-run your searches, and scan for anything new in your NAICS codes before the response window closes. This post covers three ways to automate that. Pick the one that matches how much you want to do with the data.

Approach	Cost	What you get	Best when
A. SAM.gov saved search + Notify	Free	An email with a link to your search results	You track one or two searches and just want a nudge
B. SAM.gov Get Opportunities API	Free (API key needed)	JSON per request	You're a developer and stay within your daily request limit
C. Scheduled feed from SAM.gov's public daily extract	Pay per result	Rows in email, a Drive file/Sheet or Slack	You want the actual notices, filtered, in your own tools

Before you start: list your NAICS codes

Write down the 6-digit NAICS codes you bid under. Your SAM.gov entity registration is a good starting point, and the official lookup is at census.gov/naics. Think about prefixes too: 5415 covers every 5415xx code (computer systems design and related services). If agencies tend to misclassify your kind of work, add a few keywords such as "janitorial" or "HVAC".

Option A: SAM.gov saved search with Notify (free)

This is built into SAM.gov, and a lot of people miss it.

Sign in to SAM.gov. You need a free account to save searches.
Search the Contract Opportunities domain. Set NAICS, set-aside, place of performance and notice type in the left-hand filters.
Click Actions → Save and name the search.
Open Saved Searches, click Actions next to the search, and choose Notify. Saving a search on its own sends no email.

The limit: the email points you to your search results and doesn't list which notices matched. You still click through and read every time.

Option B: the official API

GSA's Get Opportunities Public API (https://api.sam.gov/opportunities/v2/search) takes ncode (one NAICS code), ptype, typeOfSetAside, state, and a required postedFrom/postedTo range in MM/dd/yyyy format. It needs an API key from your SAM.gov account. GSA's user guide sets the default limit for a non-federal individual who isn't associated with an entity at 10 requests per 24 hours. Associated users and system accounts get more. Because each request takes one NAICS code, tracking a dozen codes can use up a small quota quickly. Docs: open.gsa.gov/api/get-opportunities-public-api.

Option C: a scheduled feed from the public daily extract (no API key)

SAM.gov also publishes a public daily data extract of all active opportunities in its Data Services section. Anyone can download it without an API key. The file is large, so the useful part is filtering it down to your codes, scheduling the filter, and sending the results somewhere you'll see them. The steps below use a ready-made Apify Actor that does this (linked at the end). The same pattern works for any scheduled Apify run.

Step 1: Build your input

This input returns open solicitations from the last two days in two facilities-services NAICS codes, small-business set-asides only, performed in Virginia, Maryland or DC:

{
  "naicsCodes": ["561720", "561730"],
  "setAsideTypes": ["SBA", "SDVOSBC", "WOSB"],
  "placeOfPerformanceStates": ["VA", "MD", "DC"],
  "noticeTypes": ["Solicitation", "Combined Synopsis/Solicitation", "Sources Sought"],
  "postedWithinDays": 2,
  "excludeExpired": true,
  "dedupeBySolicitation": true,
  "maxResults": 300,
  "includeSam": true,
  "includeGrants": false
}

What each field does:

naicsCodes takes exact codes or prefixes (5415 matches every 5415xx code).
keywords (not used above) matches any keyword in the title, solicitation number or full description, ignoring case. Use it with NAICS codes or instead of them.
setAsideTypes uses SAM.gov's codes. For example SBA (total small business), 8A, HZC (HUBZone), SDVOSBC, WOSB, EDWOSB, or NONE for unrestricted notices.
placeOfPerformanceStates takes two-letter codes. When this filter is set, notices without a listed place of performance are excluded. Leave it empty if you also want those.
noticeTypes is worth widening. Sources Sought and Presolicitation notices give you a heads-up before the solicitation drops.
postedWithinDays counts days including today, in UTC. 0 means no limit. You can use postedFrom/postedTo instead for a fixed range.
excludeExpired (default true) drops notices whose response deadline has passed. Notices with no deadline are kept.
dedupeBySolicitation keeps only the newest notice per solicitation number. SAM.gov posts amendments and follow-ups as separate records.
maxResults caps the total rows. You pay per result, so this also caps cost.

Step 2: Run it once and check a row

The first run is the test. Each result looks like this (the fundingInstrument, assistanceListings, awardCeiling and awardFloor fields are null for contracts and only filled in for grants):

{
  "id": "6196197ae63848ce93a86870cb18e0cd",
  "source": "sam.gov",
  "title": "Helena - Lewis and Clark National Forest Dry Pole Pit Rock Crushing Service",
  "solicitationNumber": "1240BE27Q0001",
  "agency": "AGRICULTURE, DEPARTMENT OF",
  "subAgency": "FOREST SERVICE",
  "office": "WALLOWA WHITMAN NATIONAL FOREST",
  "noticeType": "Combined Synopsis/Solicitation",
  "naicsCode": "237310",
  "classificationCode": "Z1LB",
  "setAsideCode": "SBA",
  "setAside": "Small Business Set Aside - Total",
  "postedDate": "2026-10-17",
  "responseDeadline": "2026-10-22T13:00:00-06:00",
  "archiveDate": "2026-11-06",
  "popCity": "Stanford",
  "popState": "MT",
  "popZip": null,
  "popCountry": "USA",
  "link": "https://sam.gov/workspace/contract/opp/6196197ae63848ce93a86870cb18e0cd/view",
  "descriptionSnippet": "Amendment 0001 - This amendment provides missing solicitation attachments, issues Government responses to offeror questions…",
  "fundingInstrument": null,
  "assistanceListings": null,
  "awardCeiling": null,
  "awardFloor": null
}

Contact names, emails and phone numbers are left out. Open link when you're ready to read the full notice and respond. Each run also writes a RUN_SUMMARY record with the source file's timestamp, so you can check how fresh the data is.

Step 3: Save it as a task

In Apify Console, click Save as a new task on the Actor page, give it a name (for example daily-facilities-va-md-dc), and paste the input above. Tasks are reusable saved configurations. Consultants can keep one task per client profile.

Step 4: Schedule it daily

SAM.gov regenerates the extract once a day, overnight US time, so a notice posted today usually appears the next morning. Schedule for the morning:

Schedules → Create new.
Set the cron expression 0 8 * * * (08:00 every day) and choose your timezone, for example America/New_York. Schedules handle daylight-saving changes.
Add → Actor task and choose your task.
Enable the schedule. New schedules start disabled.

Why postedWithinDays: 2 rather than 1? The window counts in UTC and the extract refreshes overnight, so a two-day window with de-duplication on id in your destination (Step 6) won't miss notices posted near midnight. The trade-off is that you pay again for repeat rows.

Step 5: Send results where you'll see them

Open the task's Integrations tab:

Email: add Send results email via Gmail, connect a Google account, set the subject and body, and attach the dataset as CSV or Excel. By default it fires only on successful runs.
Google Drive / Sheets: add Upload results to GDrive and pick the file name and format. Each successful run uploads a file to the Apify Uploads folder, and a CSV or XLSX file there opens in Google Sheets. To append rows to one running sheet instead, use Make or Zapier: an Apify "Watch Actor Runs" trigger, then "Get Dataset Items", then the Google Sheets "Add Rows" step. Apify's Make docs walk through exactly this.
Slack: add the Slack integration, connect your workspace, pick a channel and the "run succeeded" event. The message field accepts a Handlebars template, so you can post a link to the run's dataset, e.g. <https://console.apify.com/storage/datasets/{{resource.defaultDatasetId}}|Today's opportunities>. If a run fails, a second "run failed" message tells you to look.
Anything else: webhooks and the REST API let you send rows to a CRM, a bid board or a newsletter tool.

Step 6: Keep only what's new and keep costs predictable

De-duplicate on id in your destination (a "remove duplicates" step in Sheets, or an upsert in a database). Overlapping windows will then never show the same notice twice.
Leave dedupeBySolicitation on if you only want the latest version of each solicitation. Turn it off if you want to see every amendment.
Set maxResults and the run's maximum-charge option so one broad filter can't produce a surprise bill.

Tips that matter more than the tooling

Watch Sources Sought. They show what an agency plans to buy, and responding can shape the set-aside decision.
Use NAICS prefixes plus a few keywords. Contracting officers pick NAICS codes inconsistently, and a keyword match on the full description catches what the codes miss.
Read the deadline, not the posted date. responseDeadline carries its timezone offset, so sort by it.
Grants are separate. If you also pursue grants, setting includeGrants: true adds Grants.gov opportunities in the same schema. NAICS, set-aside, state and notice-type filters don't apply to grants, because Grants.gov doesn't publish those fields.

Disclosure: we built the Actor used in Option C, the SAM.gov Contract Opportunities Scraper & Feed. It costs $2 per 1,000 results, plus Apify's small Actor-start fee. Options A and B work fine on their own if you don't need it.