Is there an API for Accela Citizen Access permits?

Not from Accela directly — Citizen Access is a portal, not an API. PermitStack normalizes 9,469,060 permits from 136 Accela tenants into one REST API with the same schema as every other source.

Can I get Tyler EnerGov permit data programmatically?

Yes, through PermitStack: 20,350,267 permits from 330 EnerGov jurisdictions, refreshed daily and normalized to the same fields as Socrata and ArcGIS cities.

What about Click2Gov cities?

Covered too — 944,155 permits from 17 CentralSquare Click2Gov jurisdictions.

How current is closed-portal data?

Refreshed daily. Every jurisdiction carries a published data-status label and a 'data through' date, so staleness is visible rather than hidden.

Is there an API for Accela, EnerGov or Click2Gov permits?

Short answer: not from the vendors. Those systems publish building permits through citizen-facing portals — a search form and a results page — with no public API behind them. That is why most permit datasets quietly stop at whichever cities happen to run an open-data portal.

PermitStack covers them anyway. Today that is 30,763,482 permits across 758 jurisdictions whose only public interface is one of these three systems, normalized into the same schema and the same REST API as every Socrata or ArcGIS city, and refreshed daily.

Closed-portal coverage

Permitting system	Jurisdictions	Permits
Tyler EnerGov / CSS	330	20,350,267
Accela Citizen Access	136	9,469,060
CentralSquare Click2Gov	17	944,155
Total	483	30,763,482

Counts as of 2026-08-05. See coverage for the per-jurisdiction list, each with its own data-status label and 'data through' date.

Why this coverage is unusual

Open-data portals are the easy half of the country. A city running Socrata or ArcGIS publishes a machine-readable endpoint, and any permit dataset can pick it up. The other half — large metros included — runs a vendor portal with no such endpoint, so they get skipped, and the gap rarely shows up in a coverage count because nobody lists what they are missing.

These 758 jurisdictions are the half that usually gets skipped. Same fields, same categories, same daily refresh as the rest.

Run this query on your own city Free API key, 100 requests a day, no credit card.

What you get

Identical shape to every other source: permit number, type, work description, status, filed and issued dates, address, valuation, and contractor of record where the source publishes one. No special casing per city — the point of normalizing is that your code does not need to know which vendor a jurisdiction runs.

curl -H "X-API-Key: pk_your_key" \
  "https://api.permit-stack.com/v1/permits/search?city=Sanford&state=FL&per_page=25"

Check coverage for a specific city, or read the API reference.