Update AHJ
Update custom property values on an AHJ. The body custom map is keyed by property keyName — fetch the available keys via GET /properties?record_type=ahj.
Built-in AHJ fields (under Community Data in the UI) are read-only and cannot be updated through this endpoint.
Pass null to clear a value.
Authentication
Path parameters
Query parameters
Request
Custom field values keyed by property keyName. Pass null to clear a value. Unknown keyNames are rejected with a 400 — fetch valid keys via GET /properties?record_type=ahj.
Response
AHJID UUID (when known).
Full AHJ name (e.g. “City of San Francisco”).
Two-letter country code (e.g. “US”).
Two-letter state code (e.g. “CA”).
Full state name (e.g. “California”).
For sub-county jurisdictions, the containing county name.
AHJ Registry composite code (e.g. “TX-4805000”).
True for company-private jurisdictions, false for global catalog entries.
How permit submissions are accepted (online, in-person, etc.).
Auto-computed from ashraeMinTempC. Used for NEC 690.7 max-Voc string sizing.
Auto-computed from ashraeMaxTempC. Used for thermal derating in PV performance modeling.
Custom field values keyed by property keyName. This includes only customer-defined custom columns (see GET /properties?record_type=ahj). Built-in catalog AHJ fields (turnaround, website, fees, notes, etc.) are exposed as top-level fields on the AHJ object and are read-only.
