St. Louis Permit Activity: 1,221 City Records in 30 Days

The City of St. Louis public permitting portal returned 1,221 City records dated July 15 through August 14, 2026 when we retrieved it on August 14. Plumbing, mechanical, and electrical permits made up 96% of that rolling 30-day record set.

That is useful market context for a trade contractor, supplier, facilities team, or restoration company deciding where to spend research time. It is not a list of consumer enquiries, open bids, or exclusive opportunities. The records show what the City published; they do not show whether a property owner is shopping for a contractor or whether a listed party is still involved in a project.

The 30-day trade mix

The City separates this public feed into electrical, mechanical, plumbing, sprinkler, and demolition endpoints. We combined the five City endpoints, removed repeat source permit identifiers, and kept records whose City action date fell in the rolling 30-day window.

The result is a narrow, practical picture of activity that the portal publishes in these five disciplines. It is not a complete measure of all construction in St. Louis. General building, planning, occupancy, and other City workflows can be published through different systems or on different schedules.

What the public records contained on this retrieval

For this retrieval, 1,219 of 1,221 records included a project address and owner name, 1,221 included a contractor company name, and 1,157 included a non-zero project-cost field. Those are source fields, not independently verified contact or decision-maker records. A name in a public permit can be an applicant, owner, contractor, or other reported role depending on the City workflow; the role shown on the individual record matters.

That distinction changes how teams should use the data:

• A mechanical supplier can use current permit activity to understand territory and project mix before choosing which accounts or areas to research.
• A complementary trade can filter for project types relevant to its work, then check the City record and its own lawful sales process.
• A property-services team can use a published address and scope as a research starting point, not as evidence of a buyer's intent.

The records do not establish that a project is unawarded, that the owner wants a quote, or that an unsolicited contact is appropriate. Public availability is not consent for mass outreach.

Method and scope

This is a reproducible snapshot, not a claim that the City updates every field at the same time every day.

• Publisher: City of St. Louis public permit application.
• Retrieved: August 14, 2026.
• Source window: July 15–August 14, 2026, using each record's published approval or current-result date.
• Feeds reviewed: the City's electrical, mechanical, plumbing, sprinkler, and demolition permit endpoints.
• Jurisdiction rule: populated project-city fields had to identify St. Louis, Missouri. This excludes the separately governed St. Louis County portal.
• Deduplication: the City's permit number is the record key where it is present. Demolition records use the City's stable demolition permit identifier, kept in a separate key namespace.
• Important limitation: the source is a rolling window. A record can leave a source feed after the window changes, and City publication dates are not a promise about construction stage or sales readiness.

You can inspect the current source context and record availability on PermitGrab's St. Louis permit page. The official St. Louis permit application remains the authority for individual records, City rules, and corrections.

Choose the right research workflow

A mechanical supplier can use supplier territory research to compare published activity by trade and market. A restoration, insulation, controls, or maintenance team can use complementary-service project research to evaluate the documented project context before its own lawful research. For a GC, design-build, estimating, or consulting team, project-team research keeps the public scope and named role in view. None of those workflows treats a City record as a bid invitation, a purchase commitment, or permission to contact.

How to evaluate the signal before acting on it

Before spending sales or operations time on any public-record feed, answer four questions:

1. Is the jurisdiction right? City and county systems often cover different places, even when they share a name.
2. What date does the source publish? A filing, approval, inspection, and issue date can describe different moments in a project.
3. Which role does the field represent? Do not relabel an applicant or owner as the performing contractor without evidence in the record.
4. Does the workflow fit the business? Permit activity can help with market research and project context; it is not a substitute for a compliant prospecting process or a consumer request for service.

For a broader explanation of the field and scope checks, see how to evaluate public permit data before allocating sales time.

The takeaway

The City of St. Louis published a current, trade-specific 30-day record set on August 14, and the largest components were plumbing, electrical, and mechanical activity. That makes the feed a credible source for project and territory research when the user checks the underlying record, its date, and its role labels.

It does not turn a public filing into a guaranteed lead. The useful advantage is knowing exactly what the source contains—and what it does not—before deciding whether it belongs in a team's workflow.