API

Build on Entitlement Intelligence

The LocalCode API gives qualified platforms and data teams access to structured development regulations, source-backed regulatory findings, amendment history, and jurisdiction intelligence for feasibility and entitlement workflows.

Request API Access →View API Documentation

Explore the draft developer documentation and OpenAPI reference.

Source Verification · tx-austinjson

{
  "section_id": "25-2-773",
  "section_title": "Permitted Uses — MF-3",
  "jurisdiction": "tx-austin",
  "feasibility_signals": {
    "regulatory_domain": "zoning_land_use",
    "rule_type": "use_permission",
    "entitlement_relevance": true
  },
  "source_verification": {
    "effective_date": "2022-03-14",
    "source_ordinance": "20220127-069",
    "source_url": "https://data.localcode.ai/sources/tx-austin/20220127-069.pdf"
  },
  "amendments": [
    {
      "ordinance": "20231109-152",
      "date": "2023-11-09",
      "description": "Updated permitted use language"
    }
  ]
}

What the API Exposes

The Entitlement Intelligence Layer

Structured data surfaces for feasibility, source verification, amendment awareness, and jurisdiction context.

Source Verification

Code provisions, source ordinances, amendment history, official documents, and verification evidence.

Development Regulations

Structured section text, hierarchy, effective dates, and development-relevant rule metadata.

Jurisdiction Intelligence

Coverage metadata, jurisdiction context, and supported regulatory domains.

Change Events

Structured amendment and change payloads for workflows that need to know when development rules change.

Endpoints

Developer Preview API Surface

Draft v1 endpoint groups focused on jurisdictions, code sections, ordinances, legislative chain, source verification, sources, and search.

GET/v1/jurisdictions

Jurisdictions

List supported jurisdictions and coverage metadata.

GET/v1/code-sections/{id}

Code Sections

Retrieve structured code section text, hierarchy, status, and provenance fields.

GET/v1/ordinances/{id}

Ordinances

Access ordinance metadata, source links, adoption details, and related code impacts.

GET/v1/legislative-chain

Source Verification

Trace relationships between development rules, ordinances, amendments, authority, and source evidence.

GET/v1/source-verification

Source Verification

Check official source references, verification status, confidence, and evidence links.

GET/v1/sources

Sources

Retrieve source records for official code pages, ordinance PDFs, and jurisdiction materials.

GET/v1/search

Search across supported jurisdictions, code sections, ordinances, and provenance metadata.

View full API documentation →

Integration Patterns

Three Ways Teams Use LocalCode Data

From entitlement intake to amendment monitoring to platform integration — the same source-backed data layer supports multiple feasibility workflows.

Pattern 01 · Platform Integration

Add Entitlement Intelligence to Your Platform

Platforms serving real estate development, land acquisition, entitlement, or legal workflows can integrate LocalCode to surface development regulations, source verification, amendment history, and jurisdiction intelligence alongside existing property or project data.

0101 Retrieve development rules for a supported jurisdiction or section
0202 Display source-backed regulatory findings in your UI
0303 Subscribe to change events for relevant jurisdictions
0404 Use structured attributes to route issues for entitlement or legal review

platform-integrationjson

{
  "section_id": "25-2-773",
  "section_title": "Permitted Uses — MF-3",
  "jurisdiction": "tx-austin",
  "feasibility_signals": {
    "regulatory_domain": "zoning_land_use",
    "rule_type": "use_permission",
    "entitlement_relevance": true
  },
  "source_verification": {
    "effective_date": "2022-03-14",
    "source_ordinance": "20220127-069",
    "source_url": "https://data.localcode.ai/sources/tx-austin/20220127-069.pdf"
  },
  "amendments": [
    {
      "ordinance": "20231109-152",
      "date": "2023-11-09",
      "description": "Updated permitted use language"
    }
  ]
}

Pattern 02 · Amendment Monitoring

Know About Rule Changes Before They Become Project Risk

Subscribe to change events for jurisdictions that matter to your users. When relevant municipal rules change, receive structured payloads that help teams identify affected sections, attributes, and feasibility signals before the change is missed during feasibility or entitlement review.

01POST /webhooks with your endpoint URL and jurisdiction list
02Receive event payloads within 72hr of council publication
03Parse changes[] array for affected sections and attributes
04Surface alerts to users affected by the change

amendment-monitoringjson

{
  "event": "section.amended",
  "jurisdiction": "tx-austin",
  "section_id": "25-2-773",
  "section_title": "Permitted Uses — MF-3",
  "effective_date": "2023-11-09",
  "ordinance_number": "20231109-152",
  "changes": [
    {
      "attribute": "permitted_uses",
      "prior_value": ["multifamily", "residential-care"],
      "new_value": ["multifamily", "residential-care", "short-term-rental"],
      "source_ref": "§ 25-2-773(B)(4)"
    }
  ],
  "diff_url": "https://api.localcode.ai/v1/diffs/tx-austin/20231109-152",
  "timestamp": "2023-11-09T14:22:17Z"
}

Pattern 03 · Entitlement Intake & Site Feasibility

Entitlement Intake & Site Feasibility

Use LocalCode data when a site or project enters your intake workflow. Surface relevant municipal rules, amendment history, jurisdiction context, and source-backed feasibility signals before a team spends time on full entitlement review.

0101 Submit jurisdiction, code section, project context, or supported site identifiers
0202 Retrieve relevant development regulations and structured feasibility signals
0303 Compare regulatory findings against the intended project use or strategy
0404 Flag issues requiring entitlement, legal, or consultant review

entitlement-intake-&-site-feasibilitybash · json

curl -X POST https://api.localcode.ai/v1/parcels/batch \
  -H "Authorization: Bearer lc_live_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "jurisdiction": "tx-austin",
    "parcel_ids": ["APN-1001", "APN-1002", "APN-1003"]
  }'

Technical Specs

Built to the Standard You Expect

OpenAPI 3.1 Spec

Import directly into Postman, Insomnia, or any OpenAPI-compatible client. Full schema documentation included.

<100ms P95 Latency

Served from edge infrastructure, cached per jurisdiction. Batch endpoints optimized for high-volume workflows.

SDK (Coming Soon)

TypeScript and Python clients. Drop-in integration for analytics pipelines and PropTech platforms.

Webhook Retries

Automatic retry with exponential backoff. Delivery logs and event replay available in the dashboard.

Authentication

Bearer Token, Standard HTTP

All requests are authenticated with a Bearer token in the Authorization header. Keys are scoped per environment (sandbox vs. production) and per tier.

API access is manually approved. We review applications and issue keys to qualified platforms and integrators. See pricing →

Authenticationbash

# All API requests
curl https://api.localcode.ai/v1/... \
  -H "Authorization: Bearer lc_live_sk_xxxxxxxxxxxx"

# Sandbox (no billing)
curl https://api.localcode.ai/v1/... \
  -H "Authorization: Bearer lc_test_sk_xxxxxxxxxxxx"

Ready to Integrate Entitlement Intelligence?

API access is manually approved. Tell us what workflow, platform, or data product you are building, and we will evaluate your application directly.

Request API Access →Request a Demo