/crexi/properties/brokers

POST /api/crexi/properties/brokers

Price: 1 credit

Get the listing brokers for a Crexi property: broker name, public profile id, license numbers and full license details (number, type, state, brokerage), badges, number of active assets, brokerage (name, website, logo, address) and the public profile URL.

How to use it

Fetch the listing broker(s) for a Crexi property by property id or detail URL. Each item has id, name, alias (public profile id, use it with the broker details endpoint), license_details (number, state_code, brokerage_name), asset_count, brokerage (name, website, address) and profile_url. Broker phone and email are not exposed.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — Crexi property id (numeric) or a property detail URL/path (examples: "1545312", "https://www.crexi.com/properties/1545312/new-york-st-josephs-church"; minLength: 1)

Response

• @type string (default: "CrexiListingBroker")
• id integer required
• global_id string nullable
• name string nullable
• first_name string nullable
• last_name string nullable
• alias string nullable
• image string nullable
• asset_count integer nullable
• is_platinum boolean nullable
• is_internal boolean nullable
• is_auctioneer boolean nullable
• verification_method string nullable
• badges array (default: [])
• licenses array (default: [])
• license_details array (default: [])
  • @type string (default: "CrexiLicense")
  • number string nullable
  • license_type string nullable
  • state_code string nullable
  • broker_title string nullable
  • brokerage_name string nullable
  • brokerage_city string nullable
  • brokerage_state_code string nullable
  • is_auctioneer boolean nullable
• brokerage object nullable
  • @type string (default: "CrexiBrokerage")
  • name string nullable
  • website string nullable
  • image string nullable
  • location object nullable
    • @type string (default: "CrexiLocation")
    • address string nullable
    • city string nullable
    • county string nullable
    • state_code string nullable
    • state_name string nullable
    • zip string nullable
    • latitude number nullable
    • longitude number nullable
    • full_address string nullable
• profile_url string nullable
• created_at integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Property not found (well-formed id but no active listing for it) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.