Get bulk-delivery job status for agents
In: header
Path Parameters
Job ID returned by POST /v1/agents/bulk-delivery
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/agents/bulk-delivery/string"{
"bytes": 0,
"chargedCount": 0,
"completedAt": "string",
"creditLedgerId": "string",
"creditsCharged": 0,
"downloadUrl": "string",
"entityType": "string",
"error": "string",
"estimatedTotal": 0,
"format": "parquet",
"jobId": "string",
"processed": 0,
"resultsUrl": "string",
"startedAt": "string",
"status": "queued"
}{
"error": "string"
}{
"error": "string"
}{
"error": "string"
}Get agent by ID GET
Previous Page
Search agents with filters POST
Search and list individual real-estate agents with filters — one row per agent. Filter by name, location (state, city, zip), brokerage/office, and production metrics (sales volume, transaction units, price range), with sorting and cursor pagination. LOCATION SEMANTICS: the state/city/zip filters match ANY of an agent's location signals — their listed city/state, their office address(es), AND the markets where they actually closed transactions (production) — combined with OR. So an agent matches a searched location if their office OR their production is there. A search for city "Long Beach" can therefore return agents whose office or displayed primary market is in a different city/state, because they transacted in Long Beach. The `state`/`city` returned on each row reflect the agent's primary market and may differ from the searched location. (Use the `office` filter to match by brokerage/office name, and the per-agent city/county/state breakdown endpoints to rank an agent's volume within a specific market.) RANKING BY DEAL SIDE: combine a location filter with `sort` on `buyerVolume`/`buyerUnits` (or `sellerVolume`/`sellerUnits`, `dualVolume`/`dualUnits`) to rank agents by how active they are representing buyers vs. sellers in that market — e.g. sort `buyerVolume` descending for the most active buyer-side agents in a state or city. This is the per-agent record search: use it to find specific real-estate agents or build a filtered agent list. (For a single agent by ID use the agent detail endpoint.) If you only need how many agents match and not the records themselves, send the same request body to `countAgents`.