/crexi/properties

POST /api/crexi/properties

Price: 1 credit

Get full Crexi commercial property details by id or detail URL: name, address, status, property type and subtype, asking price, price per sqft, cap rate, pro-forma cap rate and NOI, square footage, net rentable area, units, year built, buildings, stories, zoning, lot size, ceiling height, loading docks, ownership, opportunity zone, marketing description, investment highlights, image, latitude/longitude and the full typed summary detail list.

How to use it

Fetch a single Crexi commercial real estate property by numeric id or detail URL. Returns one item with id, name, status, property_types, subtypes, asking_price, cap_rate, pro_forma_noi, square_footage, units, year_built, zoning, lot_size_acres, ownership, marketing_description, investment_highlights, location (address, city, state_code, latitude, longitude), property_url and summary_details. Use the properties search endpoint to discover property ids.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — Crexi property id (numeric) or a property detail URL/path (examples: "1545312", "https://www.crexi.com/properties/1545312/new-york-st-josephs-church"; minLength: 1)

Response

• @type string (default: "CrexiProperty")
• id integer required
• name string nullable
• description string nullable
• status string nullable
• platform string nullable
• property_types array (default: [])
• subtypes array (default: [])
• asking_price number nullable
• price_per_sqft number nullable
• cap_rate number nullable
• pro_forma_cap_rate number nullable
• pro_forma_noi number nullable
• net_operating_income number nullable
• square_footage integer nullable
• net_rentable_sqft integer nullable
• units integer nullable
• year_built string nullable
• buildings integer nullable
• stories integer nullable
• zoning string nullable
• lot_size_acres number nullable
• ceiling_height string nullable
• loading_docks integer nullable
• parking_spots integer nullable
• occupancy_rate number nullable
• tenancy string nullable
• tenant_count integer nullable
• lease_type string nullable
• lease_term_years number nullable
• remaining_term_years number nullable
• is_ground_lease boolean nullable
• class_type string nullable
• investment_type string nullable
• apn string nullable
• ownership string nullable
• broker_co_op boolean nullable
• is_in_opportunity_zone boolean nullable
• is_note_loan boolean nullable
• is_sold boolean nullable
• is_paused boolean nullable
• is_outdated boolean nullable
• is_elite boolean nullable
• has_om boolean nullable
• has_flyer boolean nullable
• has_virtual_tour boolean nullable
• marketing_description string nullable
• investment_highlights string nullable
• image string nullable
• alias string nullable
• property_url string nullable
• created_at integer nullable
• activated_at integer nullable
• updated_at integer nullable
• location object nullable
  • @type string (default: "CrexiLocation")
  • address string nullable
  • city string nullable
  • county string nullable
  • state_code string nullable
  • state_name string nullable
  • zip string nullable
  • latitude number nullable
  • longitude number nullable
  • full_address string nullable
• summary_details array (default: [])
  • @type string (default: "CrexiSummaryDetail")
  • key string required
  • label string nullable
  • value_type string nullable
  • display 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 — Property not found (well-formed id but no active listing for it) 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.