US commercial property as JSON, with the lease rate read the way the source quotes it
Crexi API returns live Crexi data as clean JSON for crexi The primary endpoint, search, returns listing_id, title, url (the live crexi.com page), listing_type, price (amount in USD, currency, status = published | unpriced | auction,….
5 active endpoints. Every call is 1 credit.
- POST/crexi/v1/search
- POST/crexi/v1/lease_search
- POST/crexi/v1/property_detail
- POST/crexi/v1/lease_detail
- POST/crexi/v1/suggest
What Crexi endpoints does ReefAPI ship?
5 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Crexi API
5 of 5 endpoints, ready to run
Search the FOR-SALE commercial listings on crexi.com. Give a market — city plus state, a county, a ZIP code or a whole state — and narrow it with the filters Crexi itself publishes: property type, asking price range, building size, lot acreage, cap rate, year built and opportunity-zone status. Every row carries the asking price in USD with an explicit status, the property types, the building size, the brokerage, the full geocoded address and the live crexi.com URL. Listings whose price the broker did not publish are included by default and say so; set include_unpriced to false for priced listings only. Page with offset. A market with no matching listing answers an honest empty result, not an error.
{ "ok": true, "data": { "listings": [ { "listing_id": 2528122, "title": "Boxing Gym For Sale", "url": "https://www.crexi.com/properties/2528122/texas-boxing-gym-for-sale", "listing_type": "sale", "price": { "amount": 100000, "currency": "USD", "status": "published", "formatted": null }, "property_types": [ "Business for Sale" ], "property_subtypes": null, "investment_type": null, "building_size_sqft": 2459, "status": "On-Market", "description": "Business for Sale | 2,459 SqFt", "brokerage_name": "eXp Commercial", "location": { "address": "Business For Sale", "city": "Austin", "county": null, "state_code": "TX", "state": "Texas", "zip": "78748", "country": "United States", "latitude": 30.168207, "longitude": -97.8177601, "full_address": "Business For Sale, Austin, TX 78748" }, "other_locations": null, "in_opportunity_zone": false, "is_new": false, "activated_on": "2026-05-26T13:17:37.173Z", "updated_on": "2026-07-02T17:25:15.312Z", "media": { "thumbnail": "https://crexi.com/images/format=auto,width=716,height=444,fit=cover/assets/2528122/570a1333086f4a96af1f3c79be4426d6.PNG", "image_count": 1, "gallery_item_count": 1, "has_video": false, "has_virtual_tour": false, "has_offering_memorandum": true, "has_flyer": false } }, { "listing_id": 2689308, "title": "13701 Fitzhugh Road", "url": "https://www.crexi.com/properties/2689308/texas-13701-fitzhugh-road", "listing_type": "sale", "price": { "amount": 4700000, "currency": "USD", "status": "published", "formatted": null }, "property_types": [ "Office", "Mixed Use", "Land" ], "property_subtypes": null, "investment_type": "Core", "building_size_sqft": 8600, "status": "On-Market", "description": "9.99 Unrestricted Acres with Flex/Office-Warehouse in Hays County, 3 Miles from US-290", "brokerage_name": null, "location": { "address": "13701 Fitzhugh Road", "city": "Austin", "county": "Hays County", "state_code": "TX", "state": "Texas", "zip": "78736", "country": "United States", "latitude": 30.23576265770295, "longitude": -98.0083788917877, "full_address": "13701 Fitzhugh Road, Austin, Hays County, TX 78736" }, "other_locations": null, "in_opportunity_zone": false, "is_new": false, "activated_on": "2026-09-08T01:22:58.146Z", "updated_on": "2026-09-08T01:22:58.146Z", "media": { "thumbnail": "https://crexi.com/images/format=auto,width=716,height=444,fit=cover/assets/2689308/203eb5905b774606a9ff26931d644759.PNG", "image_count": 5, "gallery_item_count": 5, "has_video": false, "has_virtual_tour": false, "has_offering_memorandum": false, "has_flyer": true } } ], "total_results": 665, "returned_count": 2, "offset": 0, "limit": 2, "listing_type": "sale" }, "meta": {} }
How the Crexi API works
Crexi is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 321 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Sale and lease are two different searches against two different hosts
Crexi splits its market in two and so does this engine. The filters differ, the URLs differ and the records differ. Asking the sale surface for a lease rate is not a filter away; it is the wrong call.
{"city": "Austin", "state": "TX"}For-sale listings. Pair city with state: a bare city name matches that city in every state. A city Crexi does not know returns an honest empty rather than the national inventory.
{"city": "Austin", "state": "TX"}Lease spaces, from Crexi's separate lease host. The rate comes back both as a number and as the source's own formatted string, because the two disagree more often than you would expect.
{"listing_id": "<from a sale row>"}The full sale record. Sale and lease listings never share a URL shape, so a lease id on this call is the wrong call rather than a near miss.
{"listing_id": "<from a lease row>"}The full lease record, including the suite table that the lease search rows do not carry.
Two clean halves of the US commercial market, with the lease rate expressed the way the broker quoted it rather than flattened into a single number.
curl -X POST https://api.reefapi.com/crexi/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"city":"Austin","state":"TX","limit":25}'{
"ok": true,
"data": { … },
"meta": {
"api": "crexi",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}United States only, two hosts, and a lease rate that is often a range rather than a number
Measured 2026-09-30 against the live gateway across three sale markets and two lease markets, 250 rows read with every id checked against its own URL. Three of these lines go against us.
Crexi runs its for-sale and its lease inventories on two different hosts with different filters and different record shapes, and the engine keeps them apart rather than pretending they are one search with a flag. Geography is plain text: city, state, county or ZIP, with no id to resolve first.
Sale listings and lease listings never share a URL builder. That was checked against Crexi's own page code before a single measurement was taken, because the same mistake on a comparable source once produced forty-two clean-looking measurements against an address that did not exist. Across 250 live rows, no sale row carried a lease path and no lease row was missing one, and the id inside every URL matched the listing id on all 250.
Crexi quotes lease rates like fourteen to sixteen dollars, and stripping that to digits produces 1416. Every rate is published both as a number and as the source's own formatted string, and the two are checked against each other; across 100 live lease rows they disagreed zero times. The check exists because the failure it catches looks like a perfectly filled column.
Where a space is quoted per month rather than per year, Crexi leaves its numeric rate field empty and carries the real annualised figure only in the formatted twin. Reading the numeric field alone reported those spaces as undisclosed; deriving from the source's own published value took published lease rates from thirty-six percent of rows to fifty-two.
About twenty percent of sale rows carry no asking price, because contact-the-broker and auction listings are normal here. Those come back with the amount null and a status saying why, never as zero and never as an error. A price filter therefore silently excludes them, because they cannot match a number.
Building size is on roughly thirty percent of rows. That is not a parsing gap: land is Crexi's largest category and land has no building. Lot size, property type and the address are there instead, and the absence is reported as the source publishes it.
An unknown key on this API returns a normal 200 and changes nothing, so every filter was proved against a same-run unfiltered control. Sorting was removed after eleven different values returned the identical first ten listings as the unsorted control, and so was a rate band that left the count unchanged at 14,848 with out-of-band rows still present, and a year-built filter that did nothing on either host. What ships is what moved the count.
Crexi's type-ahead matches assets and brokers rather than places, and answers a ZIP code with nothing at all. It is published honestly as a suggester rather than dressed up as a geocoder, and search takes plain text instead.
A city Crexi does not recognise returns zero rows, not the national inventory. That was checked directly: Austin with Texas returns 665 listings and Denver with Colorado 632, against an unfiltered set of more than 254,000, with no overlap at all between the filtered and unfiltered first pages.
The suggester is the cheap call; search and the detail records carry the real cost. Count is capped at a hundred rows a call even though the source will serve more, so a large market is walked by page rather than pulled in one request.
What people build with Crexi
The jobs this data is most often used for.
endpoints
credit per call
Pricing and assortment teams use Crexi to search the FOR-SALE commercial listings on crexi.com.
Brand-protection teams use Crexi to search the SPACES FOR LEASE on crexi.com.
Retail analysts use Crexi to read one FOR-SALE listing in full.
Catalog enrichment teams use Crexi to read one LEASE listing in full.
What Crexi data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 321 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/crexi/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"city":"Austin","state":"TX","limit":25}'import requests
r = requests.post(
"https://api.reefapi.com/crexi/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"city": "Austin",
"state": "TX",
"limit": 25
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Crexi.
Get a free key →What is the Crexi API?▾
Crexi API is a ReefAPI endpoint group for crexi It returns live JSON through POST requests under /crexi/v1.
Is the Crexi API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Crexi calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Crexi login or account?▾
No login to Crexi is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Crexi data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Crexi API use?▾
Crexi actions currently cost 1 credit per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Crexi from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call crexi actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Crexi API a Crexi scraper?▾
It is the managed alternative to a DIY Crexi scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same crexi back as clean JSON.
Why does my Crexi scraper keep getting blocked?▾
Most Crexi scrapers break on anti-bot defenses, rate limits and IP bans that need rotating residential proxies and browser fingerprinting to clear. ReefAPI handles all of that for you — no proxies, no captchas, no maintenance — and returns live JSON. Blocked calls are free.
26 More APIs APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Crexi, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 320 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-09-30.