Is there an API for Accela Citizen Access permits?

Not from Accela directly — Citizen Access is a portal, not an API. PermitStack normalizes 14,649,422 permits from 155 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: 26,098,254 permits from 346 EnerGov jurisdictions, normalized to the same fields as Socrata and ArcGIS cities. 295 of those 346 are Tyler-hosted tenants whose host has refused our requests since 2026-08-18, so their data stops around 2026-08-07; each is labelled with its own 'data through' date and an access note.

What about Click2Gov cities?

Covered too — 1,781,617 permits from 21 CentralSquare Click2Gov jurisdictions.

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 42,529,293 permits across 522 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. Currency varies by jurisdiction and is published per jurisdiction: most are re-read nightly, but 296 currently sit behind a host that refuses our requests and are labelled as such, with the date their data runs through.

Closed-portal coverage

Permitting system	Jurisdictions	Permits
Tyler EnerGov / CSS	346	26,098,254
Accela Citizen Access	155	14,649,422
CentralSquare Click2Gov	21	1,781,617
Total	522	42,529,293

Counts as of 2026-09-30. 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 522 jurisdictions are the half that usually gets skipped. Same fields and the same categories as the rest, with currency labelled per jurisdiction rather than assumed.

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.