City of Charlotte
Accela NC LiveQuery public building permit status for City of Charlotte via the SignedOff API.
Quick Start
This jurisdiction uses the Accela platform. Include jurisdiction=aca:charlotte to skip auto-detection and route directly.
Sample Response
Integration Notes
- City of Charlotte uses the shared Accela platform. Include the jurisdiction=aca:charlotte parameter to avoid ambiguous responses.
- Permit data is cached for 4 hours. The
data_freshnessobject in every response shows when the data was last fetched from the portal. - Pro and Enterprise plans can use
force_refresh=trueto bypass the cache and fetch live data.
The SignedOff API provides programmatic access to City of Charlotte building permit data from its official public source. Developers receive structured status and data-freshness fields, plus inspections and workflow detail when the official source publishes them without repeating manual lookups. Available fields remain source-specific, and the official jurisdiction record is authoritative.
Jurisdiction API FAQ
City of Charlotte permit API questions
How do I check City of Charlotte permit status by API?
Send the permit number to the SignedOff status endpoint. The response returns structured status and data-freshness details from Accela, plus additional fields when the official source publishes them.
What permit number format does City of Charlotte use?
A representative City of Charlotte permit number is ZUP-2026-00621. Permit formats can vary by record type and issue year, so applications should preserve letters, digits, and separators exactly as issued.
How fresh is City of Charlotte permit data?
SignedOff caches permit responses for up to four hours and reports the last refresh time in every response. Pro and Enterprise requests can use force_refresh=true when an immediate portal check is needed.
Does the City of Charlotte Permit API require a jurisdiction parameter?
Yes. Include jurisdiction=aca:charlotte to route directly to the shared Accela portal and avoid an ambiguous response.