Crexi Property details API

Q: Why is price empty for some properties?

Not every Crexi listing publishes an asking price, so price can be empty. Treat an empty price as undisclosed rather than zero, keep those listings out of price averages, and compare them on occupancy, tenancy, stories and property_types instead.

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Look up one Crexi commercial listing by numeric ID or /properties/ link for highlights, asking price, full address, subtype, tenancy, occupancy, stories and listing dates. Text-only slugs and /lease/ paths do not resolve, and missing values should not be inferred.

Crexi Property details reads one commercial real estate listing on Crexi and returns its record: name, description, highlights, listing status, asking price, the full address down to county and postal code, coordinates, property type and subtype, tenancy, occupancy, number of stories, and when the listing was posted and last updated. Investors, brokers and lenders use it to screen deals, enrich a pipeline of listings found through search and watch how listings change over time.

Pass a /properties/<ID> link or the bare numeric ID as url. Read occupancy first: it is the central variable in valuing commercial property. tenancy says whether a single tenant or several share the building, which shapes both income and risk, and property_types uses broad classes such as office, retail, industrial and multifamily, refined by property_subtypes. listed_at shows how long a listing has been on the market and updated_at how recently it changed.

Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Crexi Property details endpoint (crexi/property_detail).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to crexi and action to property_detail, and put the parameters inside params.
- Required parameters:
- url: Identifies the target property using either a full Crexi URL containing a numeric listing ID (such as /properties/<ID>) or the raw numeric ID string extracted from a search result id field.
- Returns one object. Main fields: id, url, name, text, highlights, status, price, address, city, county, state, postal_code; 21 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=crexi.
- Example request body:
{
"platform": "crexi",
"action": "property_detail",
"params": {
"url": "https://www.crexi.com/properties/2592583"
}
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`crexi`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`property_detail`	Capability identifier, fixed value.
`url`	body.params	Not declared	Yes	-	Identifies the target property using either a full Crexi URL containing a numeric listing ID (such as /properties/<ID>) or the raw numeric ID string extracted from a search result id field. URLs with text-only slugs cannot be resolved, and /lease/<ID> links cannot be used for details.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "crexi",
  "action": "property_detail",
  "params": {
    "url": "https://www.crexi.com/properties/2592583"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json

{
  "id": "req_…",
  "platform": "crexi",
  "action": "property_detail",
  "results": {
    "id": …,
    "url": …,
    "name": …,
    "text": …,
    "highlights": …,
    "status": …,
    "price": …,
    "address": …,
    "city": …,
    "county": …,
    "state": …,
    "postal_code": …,
    "lat": …,
    "lng": …,
    "property_types": …,
    "property_subtypes": …,
    "tenancy": …,
    "occupancy": …,
    "stories": …,
    "listed_at": …,
    "updated_at": …,
    "platform": …
  },
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`id`	The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
`url`	Link to the record on the platform.
`name`	Name of the object itself, for account, product and business capabilities.
`text`	Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
`highlights`	Keeps the platform's own meaning
`status`	Keeps the platform's own meaning
`price`	Price as a number without a currency symbol; see currency.
`address`	Full address, passed through as is.
`city`	City name in the platform's language, not normalized.
`county`	Keeps the platform's own meaning
`state`	Keeps the platform's own meaning
`postal_code`	Keeps the platform's own meaning
`lat`	Keeps the platform's own meaning
`lng`	Keeps the platform's own meaning
`property_types`	Keeps the platform's own meaning
`property_subtypes`	Keeps the platform's own meaning
`tenancy`	Keeps the platform's own meaning
`occupancy`	Keeps the platform's own meaning
`stories`	Keeps the platform's own meaning
`listed_at`	Keeps the platform's own meaning
`updated_at`	Keeps the platform's own meaning
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

What can I pass as `url` for a Crexi property?

A Crexi link that contains the numeric property ID, shaped like https://www.crexi.com/properties/2592583, or the numeric ID by itself. Links that carry only a text slug cannot be resolved, and paths under /lease/ are not read as property IDs. A link built from the id of a Crexi Search result works.

How do I find properties to look up?

Start with the Crexi Search capability, which lists commercial listings by US state code and can narrow them by property type, asking price and whether the property is for sale or lease. Each result carries an id; pass it here, or a /properties/ link built from it, to get the full record with occupancy, tenancy, stories and highlights.

Why is `price` empty for some properties?

Not every Crexi listing publishes an asking price, so price can be empty. Treat an empty price as undisclosed rather than zero, keep those listings out of price averages, and compare them on occupancy, tenancy, stories and property_types instead.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).