EveryData platform API
Crexi API
The Crexi catalog exposes 2 action-specific paths (`search` and `property_detail`) for commercial property search results and property details, preserving each object boundary.
The opening Crexi path, `search`, works with matching public results using `keyword`; `property_detail` instead works with one property record using `url`, preventing cross-action assumptions.
- Endpoint
- POST /api/v1/social
- Capabilities
- 2
- Per 1,000
- $1.389
Available capabilities
Compare the Crexi actions by required input, returned data, and price. Use the action identifier exactly as shown in your request.
| Action | Required | Optional | Delivery | Limit | Per 1,000 | Response fields |
|---|---|---|---|---|---|---|
searchSearch Use Crexi | keyword | min_price, property_types, sort, state, states, transaction_type | Sync delivery | Catalog values: defaultLimit=20, maxLimit=100. A limit can control pages or per-parent expansion for some actions, so it is not always a final row count. | $1.39 per 1,000 requests | id · url · name · text · address · city · county · state · postal_code · latitude · longitude · price · area_sqft · property_types · status · brokerage_name · posted_at · updated_at · image_url · is_sold · is_unpriced · in_opportunity_zone · platform |
property_detailProperty details The Crexi route | url | — | Sync delivery | — | $1.39 per 1,000 requests | 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 |
What does each Crexi action accept?
Each answer below pairs one callable action with its real inputs. Parameter meanings and allowed values are action-specific; a familiar name does not carry the same meaning across every platform.
Official sources are linked only to clarify the platform term beside them. They do not imply platform authorization or endorsement, and they do not add official-site features to the EveryInfra API contract.
What do the Crexi search parameters mean?
Use Crexi search with keyword for Crexi public results. Keep id, url, name, text, address, city, county, state, postal_code, latitude, longitude, price, area_sqft, property_types, status, brokerage_name, posted_at, updated_at, image_url, is_sold, is_unpriced, in_opportunity_zone, platform attached to this Crexi object shape. Crexi search takes keyword, transaction_type, min_price, states, state, sort, and property_types and yields name, postal_code, county, status, is_unpriced, url, platform, is_sold, image_url, price, latitude, text, longitude, in_opportunity_zone, area_sqft, state, city, updated_at, posted_at, brokerage_name, id, property_types, and address.
keywordRequired- Serves as the required search parameter for Crexi commercial real estate, but functions as a state filter when supplied as a US state postal code (such as TX, CA, or FL) rather than a free-text property title search. Providing state or states overrides this selection, though keyword remains required.
min_priceOptional- Filters listings by minimum asking price in USD. Accepts numeric values, ideally integers. This parameter does not evaluate capitalization rate or price per square foot, and is ignored by direct property_detail requests.
property_typesOptional- Filters commercial real estate by asset category using a string or array of strings, such as Office, Retail, or Multifamily. Applies strictly to search filtering rather than residential layouts, and is ignored by direct property_detail lookup requests.
sortOptional- Sorts Crexi search results descending by relevance (directory match strength, default) or newest (listing date order). It does not sort by last_updated timestamp or capitalization rate, and is ignored when retrieving properties directly by ID.Allowed values:
newestrelevance stateOptional- Filters by a single US state postal code, such as TX. Read only when states is omitted, and takes precedence over keyword state filtering. To query multiple states simultaneously, use the states array instead.
statesOptional- Filters search results by US state postal codes using a string or an array of strings, such as TX or ["TX", "CA"], automatically converted to uppercase. Precedence follows states over state over keyword. Accepts state codes only, not city names or country codes.
transaction_typeOptional- Filters listings by transaction mode: sale (default) or lease. Only the string lease (case-insensitive) switches the search to lease properties; all other values fall back to sale. The alias rent is not supported.Allowed values:
leaseCrexi: Sale and Lease Property SearchesCrexi search documentation distinguishes between Sale and Lease listings. This reference covers transaction types only and does not indicate that this endpoint includes map layers, demographic data, or traffic flow features mentioned in the source.Checked
What do the Crexi property_detail parameters mean?
The Crexi route property_detail is limited to one property record, identified by url. Crexi property_detail keeps Crexi field meanings action-specific. For Crexi property_detail, supply url; results include lat, city, tenancy, highlights, updated_at, url, property_types, platform, name, stories, county, listed_at, id, text, price, status, state, property_subtypes, lng, occupancy, address, and postal_code.
urlRequired- 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 the gateway does not parse /lease/<ID> path patterns.
How to use the Crexi API
- 01Read the public catalog and choose a platform action.
- 02Send the platform, action, and required parameters to POST /api/v1/social.
- 03Handle a synchronous result or poll the returned job ID when the selected action is asynchronous.
- 04Store the structured response fields needed by your application.
curl -X POST https://api.everyinfra.com/api/v1/social \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"platform":"crexi","action":"search","params":{"keyword":"<keyword>"}}'
Crexi API questions
What can I retrieve with the Crexi API?
Set platform to crexi. The current catalog lists search and property details. These action names identify different Crexi objects or views; they are not interchangeable search modes.
Which input starts a Crexi `search` request?
Serves as the required search parameter for Crexi commercial real estate, but functions as a state filter when supplied as a US state postal code (such as TX, CA, or FL) rather than a free-text property title search. Providing state or states overrides this selection, though keyword remains required. Send it as keyword inside params.
Which fields can Crexi `search` return?
Its declared schema includes name, text, address, and city. A declared field can still be absent from an individual source record, and every other action has its own field list.
Does every Crexi action return immediately?
No assumption is needed: this page labels each action's delivery mode. The current catalog contains sync delivery; poll a returned job ID only for an action labeled asynchronous.