Realtor Property details API
API health
- 24h health
- Normal
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Get one Realtor property from its detail URL, property ID or address. Get status, list and sold prices, sale date, beds, baths, interior square footage and year built. It does not replace an inspection, appraisal or title check.
Send POST https://api.everyinfra.com/api/v1/social with platform set to realtor and action set to property_detail. Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
#Please help me write a data collection script with the EveryInfra Realtor Property details endpoint (realtor/property_detail).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to realtor and action to property_detail, and put the parameters inside params.
- Required parameters:
- url: Specifies the Realtor detail URL for property_detail, which should contain a _M<digits>-<digits> suffix to extract the property_id. You may also pass a property ID or full address in this field.
- Returns one object. Main fields: id, url, title, status, price, sold_price, sold_at, updated_at, property_type, beds, baths, area_sqft; 17 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=realtor.
- Example request body:
{
"platform": "realtor",
"action": "property_detail",
"params": {
"url": "https://www.realtor.com/realestateandhomes-detail/3808-Warm-Meadows-St_Las-Vegas_NV_89129_M18627-62703"
}
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
#| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | realtor | Platform identifier, fixed value. |
action | body | string | Yes | property_detail | Capability identifier, fixed value. |
url | body.params | string | Yes | - | Specifies the Realtor detail URL for property_detail, which should contain a _M<digits>-<digits> suffix to extract the property_id. You may also pass a property ID or full address in this field. Other URLs lacking an extractable ID are not guaranteed to resolve. |
Code samples
#curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "realtor",
"action": "property_detail",
"params": {
"url": "https://www.realtor.com/realestateandhomes-detail/3808-Warm-Meadows-St_Las-Vegas_NV_89129_M18627-62703"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
#{ "id": "req_…", "platform": "realtor", "action": "property_detail", "results": { "id": "•••", "url": "https://www.realtor.com/realestateandhomes-detail/3808-Warm-Meadows-St_Las-Vegas_NV_89129_M18627-62703", "title": "3808 Warm Meadows St", "status": "sold", "price": 385000, "sold_price": 385000, "sold_at": "2018-07-27T00:00:00+00:00", "updated_at": "2022-02-12T00:00:00+00:00", "property_type": "single_family", "beds": 4, "baths": 3, "area_sqft": 2911, "year_built": 1996, "address": "3808 Warm Meadows St", "city": "Las Vegas", "state": "NV", "postal_code": "89129", "platform": "realtor" }, "billing": { "charged": …, "charged_usd": …, "balance_after_usd": …, … }, "quota": { … }}
Response fields
#Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
url | Link to the record on the platform. |
title | Title. null when the platform has no titles (for example text-only posts). |
status | Keeps the platform's own meaning |
price | Price as a number without a currency symbol; see currency. |
sold_price | Keeps the platform's own meaning |
sold_at | Keeps the platform's own meaning |
updated_at | Keeps the platform's own meaning |
property_type | Keeps the platform's own meaning |
beds | Keeps the platform's own meaning |
baths | Keeps the platform's own meaning |
area_sqft | Keeps the platform's own meaning |
year_built | Keeps the platform's own meaning |
address | Full address, passed through as is. |
city | City name in the platform's language, not normalized. |
state | Keeps the platform's own meaning |
postal_code | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
#- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.