POST

API health

24h health
Normal
  • 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.

Send POST https://api.everyinfra.com/api/v1/social with platform set to crexi and action set to property_detail. 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.

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.

AI prompt

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

How the endpoint works:
- 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

#
NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYescrexiPlatform identifier, fixed value.
actionbodystringYesproperty_detailCapability identifier, fixed value.
urlbody.paramsstringYes-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

#
Captured October 24, 2026 at 18:28 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed. id, billing and quota differ on every call, so only their shape is shown.
json
{  "id": "req_…",  "platform": "crexi",  "action": "property_detail",  "results": {    "id": 2592583,    "url": "https://www.crexi.com/properties/2592583",    "name": "2nd GEN Restaurant W/ Drive-thru",    "text": "<p><strong>For registration requirements and regulations, please review </strong><strong style=\"\"><a href=\"https://learn.crexi.com/how-to-register-for-an-auction-crexi-help-center\" target=\"_blank\" style=\"color: rgba(0, 0, 255, 1)\">here</a> </strong><strong>or contact </strong><sp…",    "highlights": [      "<",      "u",      "l"    ],    "status": "Active",    "price": 100000,    "address": "8926 Jensen Dr",    "city": "Houston",    "county": "Harris County",    "state": "TX",    "postal_code": "77093",    "lat": 29.8422425,    "lng": -95.3425305,    "property_types": [      "Retail"    ],    "property_subtypes": [      "QSR/Fast Food",      "Restaurant",      "Storefront"    ],    "listed_at": "2026-09-21T18:35:17.241000+00:00",    "updated_at": "2026-10-20T14:55:30.737000+00:00",    "platform": "crexi"  },  "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.

FieldMeaning
idThe record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
urlLink to the record on the platform.
nameName of the object itself, for account, product and business capabilities.
textBody 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).
highlightsKeeps the platform's own meaning
statusKeeps the platform's own meaning
pricePrice as a number without a currency symbol; see currency.
addressFull address, passed through as is.
cityCity name in the platform's language, not normalized.
countyKeeps the platform's own meaning
stateKeeps the platform's own meaning
postal_codeKeeps the platform's own meaning
latKeeps the platform's own meaning
lngKeeps the platform's own meaning
property_typesKeeps the platform's own meaning
property_subtypesKeeps the platform's own meaning
tenancyKeeps the platform's own meaning
occupancyKeeps the platform's own meaning
storiesKeeps the platform's own meaning
listed_atKeeps the platform's own meaning
updated_atKeeps the platform's own meaning
platformSource 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.
402
Insufficient balance. Top up first.
422
Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429
Per-minute request limit reached. Wait for Retry-After, then try again.
503
Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty
No data. No charge.

Errors

Google Analytics needs consent. Privacy