/njtax/properties

POST /api/njtax/properties

Price: 1 credit

Get a New Jersey assessment record by its MOD-IV property id, a m4.cgi detail URL or a district/block/lot path: owner name and mailing address, property class, location, lot size, year built, zone and acreage, the latest deed sale, the full SR1A sale history and the yearly tax-list assessment history

How to use it

The property id is the MOD-IV key returned by njtax/properties/search; a m4.cgi URL or a district/block/lot[/qual] path also resolve. Owner name and mailing address are published here, with the deed book and page, sale history and yearly assessed values.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — New Jersey property id: the MOD-IV key from a njtax/properties/search row, a m4.cgi detail URL, or a district/block/lot[/qual] path (examples: "200100206____00001_________M", "https://taxrecords-nj.com/pub/cgi/m4.cgi?district=2001&l02=200100206____00001_________M", "2001/206/1"; minLength: 1)
• district string (default: "")
• l02 string (default: "")

Response

• @type string (default: "NjtaxProperty")
• id string required
• url string required
• district_code string required
• municipality string nullable
• county string nullable
• block string nullable
• lot string nullable
• qual string nullable
• property_class string nullable
• class4_code string nullable
• property_location string nullable
• owner_name string nullable
• owner_mailing_address string nullable
• square_feet integer nullable
• year_built integer nullable
• style string nullable
• land_description string nullable
• building_description string nullable
• acreage number nullable
• zone string nullable
• epl_code string nullable
• map_page string nullable
• account_number string nullable
• mortgage_account string nullable
• additional_lots string nullable
• prior_block string nullable
• prior_lot string nullable
• prior_qual string nullable
• tax_codes string nullable
• exemption_description string nullable
• tax_current number nullable
• tax_prior number nullable
• updated_at integer nullable
• last_sale object nullable
  • @type string (default: "NjtaxSale")
  • date integer nullable
  • deed_book string nullable
  • deed_page string nullable
  • price integer nullable
  • nu_code string nullable
  • ratio number nullable
  • grantee string nullable
• sale_history array (default: [])
  • @type string (default: "NjtaxSale")
  • date integer nullable
  • deed_book string nullable
  • deed_page string nullable
  • price integer nullable
  • nu_code string nullable
  • ratio number nullable
  • grantee string nullable
• assessment_history array (default: [])
  • @type string (default: "NjtaxAssessment")
  • year integer nullable
  • property_location string nullable
  • land_value integer nullable
  • improvement_value integer nullable
  • total_value integer nullable
  • exemption integer nullable
  • property_class 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 — No New Jersey assessment record under that property 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.

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.