A Buffalo permit issued this week may be real even when the City’s open-data search does not show it yet. The Department of Permit & Inspection Services (DPIS) data inventory describes its Permits dataset as issued permits from January 2, 2007 to the present, but says permits issued in the latest two weeks have been left out. Check the issue date and the record class before using a blank result to decide what happened at a City of Buffalo address. The dataset is an index of issued permits, not a live guarantee about today’s application status.
Search the permit dataset the City names
From the City inventory, open the Permits dataset. The City says to choose Actions and Query/Search for available datasets, including a street-address query. Enter the City address carefully and compare any candidate’s address, permit type, issue date and identifying number with the project you are checking. Keep the query terms and date of your search in your notes. The case below illustrates an alternative, direct official API query. Its street-name prefix and 12-row cap limit the result; it is not a complete address history.
If the issue date is within roughly two weeks of your search, the inventory itself supplies a likely reason for an absent row. Recheck after the stated exclusion window has passed, or use the City’s records route sooner when the answer is time-sensitive. If the work is older than January 2, 2007, the inventory’s stated dataset start date does not establish that the City has no older permit file. Ask for the older record rather than treating this feed as the whole archive. Our old-permit lookup guide explains that older-file fork.
A City Hall address result still needs a project check
On October 4, 2026, we checked the City of Buffalo Permits API for stored street names beginning 65 NIAGARA, sorted by issue date and capped at 12 results. The selected rows below used 65 NIAGARA SQ. That is a useful lead, but the prefix request did not test every address variant or establish a complete history for City Hall.
- PLUM24-9600101, issued April 23, 2024, describes capping two kitchen sinks and replacing one on City Hall’s ninth floor. Its permit number and work description are more informative than the shared street field alone.
- GC24-9593014, issued March 25, 2024, describes a ninth-floor public meeting room. The description says plans were filed through IDT and to see attachments; we did not retrieve an attachment or inspect the plans.
- ELEC24-9615780, issued September 10, 2024, has the same stored
65 NIAGARA SQvalue but describes signals on Leroy and Montclair, among other streets. Do not assign that traffic-signal work to City Hall merely because the address column matches.
For a promising row, save its apno, issue date, work description and address as displayed. Then ask DPIS for the particular permit, plan or inspection record you need. The API’s expdate is an expiration field, not evidence of a passed final inspection or present lawful use.
Two official descriptions also give different starting points: the current City data inventory says January 2, 2007 and excludes the latest two weeks, while the Permits dataset metadata describes permits from January 2, 2000. We did not verify the earliest available row or measure a publication lag. Use the City inventory’s stated window as a search caveat, and request a specific older or recent record when that distinction matters.
Do not mix a permit with another DPIS dataset
The same City inventory lists General Inspections, Code Violations, planning and zoning approvals, rental records and 311 service requests as separate datasets. A complaint or inspection response may be related to construction, but it is not the issued permit. Likewise, a planning approval is a different agency decision from a building permit. Match each result to the question it can answer and keep its record number and date separate.
One especially easy trap is occupancy. The inventory labels its Multiple Dwelling Certificate of Occupancy dataset “Coming Soon” and warns that some underlying files have not been digitized. Do not cite that row as a live public CO search or assume a missing CO entry means a building lacks lawful occupancy. If occupancy is the question, request the relevant certificate or ask DPIS which current record holds it. A permit issued for work and a certificate of occupancy answer different questions; see our certificate-versus-permit guide.
What to do after a blank result
Make a simple decision log rather than repeating the same search:
- The exact Buffalo address searched.
- The dataset name.
- The approximate date and work type.
- Whether you have an application or issued-permit number.
- Whether the issue date could still fall inside the latest-two-weeks exclusion.
If the address has a unit or an older spelling, include that variant in a follow-up request, but do not invent a parcel number or treat a contractor match as the same property.
The City inventory says information not found through open data may be requested through its FOIL portal. Ask for the specific permit, plan, inspection or CO document and state what you searched. For example, “I need the issued building permit and final inspection for work at this address around March; the public Permits dataset did not show a row when checked on this date.” If you already have a permit number, include it. If you only need to know whether a freshly issued permit exists, describe the two-week publication lag and ask for the current record rather than calling the feed erroneous.
A blank dataset result can reflect a publication window, an address mismatch, a different record class or an older file outside the feed’s described span. It does not prove that no permit was issued. A visible issued permit does not show that inspections passed or that the project is complete. Seek the later inspection or occupancy document when that is the question; our final-inspection guide explains the distinction.
Housing complaints sit in Buffalo's 311 datasets, which split in May 2024; see Buffalo housing complaint records across the May 2024 split.
Last checked October 4, 2026 (2026-10-04 UTC). One anonymous, prefix-limited Permits API request returned 12 rows; selected rows above were reviewed. This was not a complete or exact-address history. No attachment or inspection record was opened, and no FOIL request or agency contact was submitted.