Zillow Batch Search API - Up to Ten Location

Send body as a JSON object containing a searches array with one to ten search-query objects. Each query carries its own location and supported filters; for example, a query can contain location, status, page and page_size. Keep an application-side association between every submitted query and its outcome. The documented contract allows HTTP 200 with partial failures: each search item has its own success or error outcome. This batch route was not live-verified, and its exact response field names and item ordering were not observed. Do not assume an HTTP-successful request means all searches worked, or merge failed and empty outcomes into one property collection. Retry selected failures only after inspecting their causes, within a client-defined request budget.

API Features

Ten-query request limit Place one to ten documented search-query objects in searches rather than issuing an unbounded multi-market request.

Structured search-array body Use one raw JSON object so nested query objects remain objects and the searches collection remains an array.

Per-query failure isolation The documented batch can report individual search failures without failing the entire HTTP request.

Query-provenance retention Store each location and filter combination with its outcome instead of losing the identity of a failed market segment.

Live API Demo

POST /api/project/zillow-real-estate/batch-search

API Response (JSON)

{}

curl -X POST 'https://api.opendata-api.com/api/project/zillow-real-estate/batch-search?key=<API_KEY>' \ -H 'Content-Type: application/json' \ -d '{"body":"<body>"}'

curl -X POST 'https://api.opendata-api.com/api/project/zillow-real-estate/batch-search?key=<API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{"body":"<body>"}'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Multi-city inventory comparison: send a bounded set of market queries and retain each city as a separate study segment.
Sale-versus-rental segmentation: submit independent searches for different statuses without conflating their result collections.
Search-workbook execution: turn a reviewed set of location/filter rows into small JSON request groups.
Selective search retry queue: isolate failed query outcomes from successful empty results before scheduling another attempt.

Frequently asked questions

What belongs in the batch-search body?

Use a JSON object with a searches array of one to ten query objects. Each object supplies its location and documented search filters. The public body parameter must carry the serialized JSON object, not a comma-separated location string.

Does HTTP 200 certify all ten searches?

No. The documented batch returns item-level success or error outcomes even when the HTTP request succeeds. Inspect every outcome; exact response keys and ordering were not live-verified.

Should I combine all returned properties immediately?

First preserve which submitted query produced each outcome. Keep failed searches distinct from valid empty segments, then deduplicate usable property IDs in your application if you need a combined view.

Related operations

Guides

View Subscription Plans →

Submit Up to Ten Property Searches