Bulk-fetch Zillow properties by zpid
zillow_bulk_getFetch up to 200 Zillow property records in one call. Returns a row per input ID, with error handling for each. Concurrent requests are throttled to avoid bot detection, and a hard deadline prevents hanging.
Instructions
Fetch up to 200 Zillow property records in a single call — the "give me everything for these N saved homes" endpoint. Returns one structured row per input id (no pivoted side-by-side summary table — for 2-25 listings with a comparison summary use zillow_compare_properties). Each row is either { zpid, property } on success or { zpid, error, error_kind } on failure — one bad zpid never fails the whole call. Calls fan out concurrently against /homedetails/<zpid>_zpid/ (capped at 6 in flight, per issue #78, with retry-once-on-timeout per sub-request to absorb transient SW evictions). Big lists fan out bounded to 6 in flight and paced by a per-host requests-per-minute throttle (burst 20) so the batch doesn't trip Zillow's PerimeterX bot-wall (issue #90). If the bot-wall is hit, the blocked sub-requests are retried with exponential backoff; anything still blocked is reported with error_kind: "bot_challenge" (distinct from a missing listing) and the response carries a { blocked, retry_after_s } envelope so you can finish the rest in a second pass. The whole call is bounded by an overall hard deadline (issue #98): a single slow/hung row never wedges the server — when the deadline is reached any row that has not yet settled is returned with error_kind: "pending" and the response carries a { pending } count so you can re-run just those ids.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| urls | No | Zillow homedetails URLs/paths to fetch. 1..200. | |
| zpids | No | Zpids to fetch. 1..200. Provide either zpids or urls. |