POST /api/njtax/properties/search
Price: 10 credits
Search New Jersey assessment records within one municipality by property class, latest-sale date range and maximum total assessed value; returns the owner name, property class, property location, municipality and the MOD-IV property id for each match. Pass the id to njtax/properties for the owner mailing address, lot size, deed and sale history and yearly assessment history
Municipality codes are four digits (two-digit county + two-digit municipality) and come from the county assessor dropdowns; a municipality part of 00 (2000) searches that whole county, and county-wide rows carry no property_class. There is no cross-county query. For commercial owners use property_class 4A (commercial), 4B (industrial) or 4C (apartment). Owner name is in each row; the mailing address and sale history need njtax/properties by the returned id.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)district string required — New Jersey municipality code (four digits: two-digit county 01-21 + two-digit municipality); a municipality part of 00 searches the whole county (examples: "2001", "0906", "2000"; minLength: 4; maxLength: 4)count integer required — Max number of property rows to return (min: 1; max: 20000)property_class string nullable — Assessment property class to filter by (examples: "4A", "4B", "4C", "2")sale_date_from integer nullable — Keep only properties whose latest recorded sale is on or after this datesale_date_to integer nullable — Keep only properties whose latest recorded sale is on or before this dateassessed_value_max integer nullable — Keep only properties with total assessed value at or below this amount (USD) (min: 0)@type string (default: "NjtaxPropertyRow")id string requireddistrict string requiredcounty string nullableblock string nullablelot string nullablequal string nullableproperty_class string nullableproperty_location string nullableowner_name string nullableurl string required422 — 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.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.