Skip to main content
Building codes and other regulatory requirements are different across every one of the over 30,000 US jurisdictions. Keeping track of which rules apply where is manual, error-prone, and time-consuming. Fordje Connect gives you programmatic access to building code, zoning, permitting, licensing, utility interconnection requirements, and other regulatory data organized by jurisdiction — so you can look up, compare, and export requirements across any Authority Having Jurisdiction (AHJ) your organization subscribes to.

​
What you’ll find in Fordje

AHJs are the cities, counties, states, and utilities that write and enforce building codes, zoning rules, permitting requirements, and interconnection standards. Every piece of data in Fordje is tied to a specific AHJ. Your organization subscribes to the AHJs relevant to your work, and Fordje Connect scopes all data to that subscription. Learn more about AHJs
Data points are the individual code requirements tracked in Fordje. A data point is a specific question about a jurisdiction’s code — like “What is the minimum insulation R-value?” or “Is a permit required for re-roofing?” Each data point has a value that can differ from one AHJ to another. Learn more about data points
Collections are saved configurations that define which data points to pull. Think of a collection as a reusable template — you define the set of questions once, then run it against any group of AHJs to get answers. Collections are created in the Fordje platform and executed through Fordje Connect. Learn more about collections
Reports are side-by-side comparisons of code requirements across jurisdictions. Use reports to generate comparison matrices (AHJs on one axis, data points on the other) or export data as CSV for use in your own tools. Learn more about reports
Categories are regulatory topics — like Permitting, Inspections, or Building Standards — used to organize data points. Filter by category to focus on the code requirements relevant to your work. Learn more about categories

​
How Fordje handles jurisdictional laddering

Building codes often layer across multiple levels of government. A project in Los Angeles, for example, may need to comply with requirements from the City of Los Angeles, Los Angeles County, and the State of California — each of which can adopt its own codes. Utility interconnection requirements add another layer on top of that. Fordje resolves this laddering for you behind the scenes. When you pull data points for an AHJ, the values you receive already account for the full chain of parent jurisdictions. You get the complete, resolved answer — no need to manually trace which level of government a requirement comes from.

​
How access works

1

Your organization subscribes to specific AHJs through Fordje

2

An admin creates an API key in the Fordje platform

3

Your API key inherits that subscription — every API call is automatically scoped to the jurisdictions you have access to

Quickstart

Make your first API call and see real jurisdiction data.

Authentication

Set up your API key to start making requests.

API Reference

Detailed endpoint documentation for all available data.

AHJs

How jurisdictions, access scoping, and laddering work.