Quickstart

Magic-link signup at permitcore.io/signup. No credit card required for the free tier. After signing in, your API key lives at Account → API Keys. Keys can be created and rotated via either the account dashboard or the programmatic key endpoints.

2. Set up your environment

Export your key. Never commit it — treat it like a database password.

export PERMITCORE_API_KEY=pk_...

3. Make your first request

Your first call is /v1/permits — the core listing endpoint. Fetch recent New York City permits. (To filter to a buyer segment, use the /v1/permits/target endpoint with &target_segment=<segment> — /v1/permits itself has no cohort query parameter.)

curl "https://api.permitcore.io/v1/permits?jurisdiction=nyc&per_page=10" \
  -H "Authorization: Bearer $PERMITCORE_API_KEY" \
  -H "Accept: application/json"

const res = await fetch(
  "https://api.permitcore.io/v1/permits?jurisdiction=nyc&per_page=10",
  {
    headers: {
      Authorization: `Bearer ${process.env.PERMITCORE_API_KEY}`,
      Accept: "application/json",
    },
  },
);
const data = await res.json();
console.log(data.items);

import os
import httpx

r = httpx.get(
    "https://api.permitcore.io/v1/permits",
    params={"jurisdiction": "nyc", "per_page": 10},
    headers={
        "Authorization": f"Bearer {os.environ['PERMITCORE_API_KEY']}",
        "Accept": "application/json",
    },
)
r.raise_for_status()
print(r.json()["items"])

4. Read the response

You’ll get back a page of permits in items, plus pagination:

{
  "items": [
    {
      "canonical_uid": "1:BT-202601090",
      "jurisdiction_slug": "nyc",
      "address_full": "82 ASP 1ST FLOOR, Manhattan, NY 10009",
      "permit_type_normalized": "alteration",
      "work_class": "alteration_minor",
      "cohort": "commercial_alteration",
      "valuation_usd": 18400,
      "issued_date": "2026-05-27"
    }
  ],
  "pagination": { "page": 1, "per_page": 10, "has_more": true }
}

Each permit carries a rich, structured record — address + geocode, classification (cohort, work_class, permit_type_normalized), scope, valuation, contractor, dates, data-quality flags, and enrichment. See GET /v1/permits for the full field list and every query parameter. To filter to a buyer segment, call GET /v1/permits/target?jurisdiction=nyc&target_segment=<segment>; paginate either endpoint with &page= (or, on /v1/permits, an opaque &cursor= for deep paging). Want the per-segment counts for a jurisdiction instead of the permit rows? Use GET /v1/jurisdictions//cohorts/distribution.

5. What next

Cohort taxonomy

The canonical 23 segments + what each one covers.

Authentication

Key formats, header conventions, security best practices.

Rate limits

Per-tier quotas + how to handle 429 responses.

Data licensing

Commercial-use terms + attribution for paid tiers.

API reference

Full endpoint catalog with request/response shapes.

Need help

Open the API reference for endpoint shapes + the errors page for retry semantics.
For account, billing, or integration support, email kian@permitcore.io — include your key prefix (first 12 characters) and the x-request-id from the failing response for fastest triage.

Introduction

Concepts

API Reference

Reference

2. Set up your environment

3. Make your first request

4. Read the response

5. What next

Cohort taxonomy

Authentication

Rate limits

Data licensing

API reference

Need help

​1. Sign up for an API key

​2. Set up your environment

​3. Make your first request

​4. Read the response

​5. What next

Cohort taxonomy

Authentication

Rate limits

Data licensing

API reference

​Need help

1. Sign up for an API key

2. Set up your environment

3. Make your first request

4. Read the response

5. What next

Need help