POST /api/njparcels/property
Price: 1 credit
Get a New Jersey parcel by district/block/lot key or property URL: address, municipality, county, property type, last sale date and price, deed book and page, assessed land/improvement/total value, annual property taxes, owner mailing address and parcel centroid; optionally the boundary polygon
Parcel keys come from the href in njparcels/search rows. Owner name is redacted statewide at the source; only the owner mailing address is published. Set include_geometry for the parcel boundary.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)parcel string required — NJParcels parcel key (district_block_lot[_qual]), district/block/lot path, or property URL (examples: "1707_29_6", "1707/29/6", "https://njparcels.com/property/1707/29/6"; minLength: 1)include_geometry boolean — Also fetch the parcel boundary polygon from the GeoJSON API (one extra request) (default: false)district string (default: "")block string (default: "")lot string (default: "")qual string nullable@type string (default: "NjparcelsParcel")pams_pin string requireddistrict string requiredcounty string nullablemunicipality string nullableblock string requiredlot string requiredqual string nullableurl string requiredaddress string nullableproperty_type string nullableowner_name string nullableowner_address string nullableowner_city string nullableowner_zip string nullablelast_sale_date integer nullablelast_sale_price number nullabledeed_book string nullabledeed_page string nullableassessed_total number nullableassessed_land number nullableassessed_improvements number nullableannual_taxes number nullablelatitude number nullablelongitude number nullablegeometry object nullable@type string (default: "NjparcelsGeometry")type string requiredcoordinates array (default: [])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 — NJParcels has no parcel under that id 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.