BuildZoom contractor permits API

Use the BuildZoom contractor permits API to retrieve building-permit records associated with a selected contractor. Provide source record ID (id); refine the result with result sort mode (sort). Each permit entry preserves project address, date, work description and the recorded valuation or permit identifiers, providing the source evidence behind a contractor's published project activity. Review a contractor's permit history, compare project locations and dates and examine the recorded work descriptions. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Contractor id from /buildzoom/v1/contractor or /buildzoom/v1/contractors.
Optional parameters (7)
score (default, most notable first) or date (newest first).
Multiple of 20 (default 0).
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON exports are not exposed.
Native CSV/NDJSON record selector; it has no effect on this JSON-only product.

Sample response

{
  "cached": false,
  "count": 20,
  "credits_used": 1,
  "id": 90650427,
  "next_offset": 20,
  "offset": 0,
  "permits": [
    {
      "address": "106 Karola Dr, Sebring, FL, 33870",
      "building_type": null,
      "date": "2026-09-22",
      "description": "Remove and replace w/shingle",
      "fee": null,
      "permit_number": "ROOF2609-0074",
      "permit_type": "Residential",
      "property_url": "https://www.buildzoom.com/property-info/106-karola-dr-sebring-fl-33870",
      "status": "issued",
      "title": "Roofing",
      "valuation": null
    },
    {
      "address": "8620 124th Way N, Seminole, FL, 33772",
      "building_type": null,
      "date": "2026-09-01",
      "description": "Re-roof replace with standing seam metal",
      "fee": null,
      "permit_number": "EBP-26-09740",
      "permit_type": "Reroof metal/alum...",
      "property_url": "https://www.buildzoom.com/property-info/8620-124th-way-seminole-fl",
      "status": "final",
      "title": "Roofing",
      "valuation": 21000
    },
    "… 18 more"
  ],
  "sort": "date"
}

Response result

Response structure

Inferred from examples
  • cachedboolean
  • countinteger
  • credits_usedinteger
  • idinteger
  • next_offsetinteger
  • offsetinteger
  • permits(object | string)[]
    • addressstring
    • building_typenull
    • datestring
    • descriptionstring
    • feenull
    • permit_numberstring
    • permit_typestring
    • property_urlstring
    • statusstring
    • titlestring
    • valuationnull | integer
  • sortstring

Loading related APIs…

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use BuildZoom contractor permits API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.