/njparcels/search/address

POST /api/njparcels/search/address

Price: 5 credits

Search New Jersey parcels by street address across one county or the whole state: parcel key, street address, municipality, county, property type and owner mailing address. Owner name is redacted at the source

How to use it

The index matches street names only, not city or ZIP. The source returns at most 50 rows per query, so narrow by county and street to cover an area. Pass property_type ['commercial','industrial','apartment'] for commercial real estate. Feed a returned pams_pin to njparcels/property for the full record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• address string required — Street-address text to match against NJ parcel street names; city/ZIP are not matched (examples: "101 S Broad St", "Main Street", "Broadway"; minLength: 1)
• county string — County to search; '##' is all of New Jersey. Accepts a county name, its two-digit code, or a region (NJ, CJ, SJ, SH) (default: "##"; examples: "##", "Essex", "07")
• property_type array nullable — Keep only rows whose property type is in this list (case-insensitive). Commercial real-estate classes are commercial, industrial and apartment (examples: ["commercial","industrial","apartment"])
• count integer required — Max number of parcels to return (min: 1; max: 50)
• county_code string (default: "##")
• type_filter array (default: [])

Response

• @type string (default: "NjparcelsSearchRow")
• pams_pin string required
• district string required
• block string required
• lot string required
• qual string nullable
• url string required
• address string nullable
• municipality string nullable
• county string nullable
• property_type string nullable
• owner_name string nullable
• owner_address string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.