Docs menu
StreetEasy API endpoint
StreetEasy Market Data Catalog API
Lists the 63 monthly metrics selectable in StreetEasy's Data Dashboard. Each has an `id`, display `label`, a sales or rentals `type`, a `bedrooms` segment and a `property_type`. Pass an `id` to `streeteasy-market-data-series` to get that metric's data. Takes no parameters.
GETapiKey1 credit/requestStreetEasystreeteasy.MarketDataCatalog
StreetEasy/streeteasy/market-data/catalogEndpoint facts
- Method
- GET
- API path
- /streeteasy/market-data/catalog
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- StreetEasy
- Response schema
- #/definitions/streeteasy.MarketDataCatalog
- MCP tool
- streeteasy_market_data_catalog
How this endpoint behaves
MCP tool: streeteasy_market_data_catalog
Lists the selectable monthly metrics in StreetEasy's public Data Dashboard. Each entry contains the source dataset ID, display label, sales/rentals type, bedroom segment, and property type. Use a returned id with streeteasy-market-data-series.
Parameters
None.
Response behavior
The catalog is pinned from StreetEasy's public dashboard metric selector. The automated service test asserts the exact set of 63 active dataset IDs so selector drift is visible.
Example
Sampled response
- Request, 14 Oct 2026
- GET /streeteasy/market-data/catalog
- Items in metrics
- 63
- Fields filled in every checked item
- 5
| Field | Filled in, of 63 checked | Values in the sample |
|---|---|---|
| id | 63 | |
| label | 63 | “Median Asking PPSF” and 15 other values |
| type | 63 | Sales (41), Rentals (22) |
| bedrooms | 63 | Any Bedrooms (39), One Bedroom (6), Studio (6) and 2 more |
| property_type | 63 | Any Property Type (40), Condo (8), Coop (8) and 1 more |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/streeteasy/market-data/catalog" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"source": "StreetEasy Data Dashboard",
"metrics": [
{
"id": "medianAskingPrice",
"label": "Median Asking Price",
"type": "Sales",
"bedrooms": "Any Bedrooms",
"property_type": "Any Property Type"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/streeteasy.MarketDataCatalog
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| metrics | array | No | ||||
| metrics[].bedrooms | string | No | ||||
| metrics[].id | string | No | ||||
| metrics[].label | string | No | ||||
| metrics[].property_type | string | No | ||||
| metrics[].type | string | No | ||||
| source | string | No |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Code examples
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/streeteasy/market-data/catalog" \
-H "x-api-key: $CRAWLORA_API_KEY"