Skip to main content
This guide walks you through your first few API calls to Fordje Connect. By the end, you’ll have retrieved jurisdiction data, queried code requirements, and generated a comparison report.

Prerequisites

  • You need an API key from your Fordje account. If you don’t have one, contact your organization administrator.
  • Your API key determines which Authority Having Jurisdiction (AHJ) records you can access — you’ll only see data for jurisdictions your organization subscribes to.
Python examples use the requests library — install it with pip install requests.JavaScript examples use top-level await and the built-in fetch API, which requires an ES module environment. In Node.js 18+, either add "type": "module" to your package.json or save files with the .mjs extension. Alternatively, wrap the code in an async function.
1

See your jurisdictions

Let’s start by seeing which AHJs your organization has access to.
You’ll receive a response like this:
Each AHJ has an id you’ll use in later requests, along with its name, type (city, county, or state), state_code, and geoid (its Census GEOID — see looking up AHJs by geoID).
2

Look up code requirements

Now let’s query some actual code data. Data points are the individual code requirements tracked in Fordje — things like permit requirements, insulation values, or inspection rules.Plug these data points into your sales, design, engineering, or permitting tool so you have accurate data points exactly where you need them. Or pull a full set into your CRM at the start of a project.You can filter data points by AHJ IDs, state, or category. Here’s how to pull data points for two specific jurisdictions:
You’ll receive a response like this:
Each item pairs an AHJ with a data point type and the latest published value for that jurisdiction. When available, the response also includes source metadata such as reference and section.
You can also filter by state_codes (e.g., state_codes=CA) or category_ids to narrow results to a specific topic like Permitting or Inspections. See the data points concept page for all available filters.
3

Pull a curated set with collections

Once you know which data points matter for your workflow, save them as a collection in the Fordje platform. Then execute that collection through the API to pull exactly the data you need — no extra filtering required.
You’ll receive a response like this:
The response includes only the data points defined in the collection, scoped to the AHJs you specified. Use collections to standardize the data you pull across projects — define once, run anywhere.
To see which collections your organization has set up, call GET /v1/collections. See the collections concept page for details.
4

Compare across jurisdictions

One of the most powerful features of Fordje Connect is comparing code requirements across multiple jurisdictions at once. Reports let you build a matrix — jurisdictions on one side, code requirements on the other.Quickly see where you can easily expand into or provide a full list of requirements for all current projects to your teams.
You’ll receive a response like this:
Each row is an AHJ, and each key in values maps to a data point type ID. The cell object contains the published value and any available source metadata.
You can also export report data as CSV using the POST /v1/reports/export endpoint. See the reports concept page for details.

Next steps

Authentication

Learn how API keys work and how to keep them secure.

AHJs

How jurisdictions, access scoping, and laddering work.

Rate limiting

Usage limits and tips for efficient API calls.

API Reference

Full endpoint docs with request and response details.