# Crexi Property details API (crexi.property_detail)

- Canonical page: [https://everyinfra.com/en/crexi-api/property_detail](https://everyinfra.com/en/crexi-api/property_detail?utm_medium=ai_doc&utm_campaign=page_md)
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "crexi", "action": "property_detail", "params": {...}}
- Price: $0.001389 per call ($1.39 per 1,000 requests); failed calls and empty results are not charged
- Returns: single object
- Mode: sync; add "mode": "async" for slow tasks

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.

## Health

- Live health (24h percent, hourly and daily trends): https://api.everyinfra.com/api/v1/social/availability?platform=crexi&action=property_detail

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| url | not declared | yes | not declared | 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. |

## Response fields (items in `results`)

| 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 | platform-native meaning |
| status | platform-native 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 | platform-native meaning |
| state | platform-native meaning |
| postal_code | platform-native meaning |
| lat | platform-native meaning |
| lng | platform-native meaning |
| property_types | platform-native meaning |
| property_subtypes | platform-native meaning |
| tenancy | platform-native meaning |
| occupancy | platform-native meaning |
| stories | platform-native meaning |
| listed_at | platform-native meaning |
| updated_at | platform-native meaning |
| platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |

## Example

```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"
  }
}'
```

```python
import os
import requests

response = requests.post(
    "https://api.everyinfra.com/api/v1/social",
    headers={"Authorization": f"Bearer {os.environ['EVERYINFRA_API_KEY']}"},
    json={
        "platform": "crexi",
        "action": "property_detail",
        "params": {
            "url": "https://www.crexi.com/properties/2592583",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

Real response to the example request above, captured 2026-10-24T18:28:34Z. `results` and `count` are real 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.

```text
{
  "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": { … }
}
```

## 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.

## Also

- Capability catalog (no key): https://api.everyinfra.com/api/v1/social/catalog?platform=crexi
- OpenAPI: https://everyinfra.com/openapi.json · Agents guide: https://everyinfra.com/agents.md
