Zillow Batch Agent Contact API

Send body as a JSON object containing a screen_names array of known public agent profile names. Use names already held in an authorized directory or chosen for a legitimate research task. The source documentation does not provide a numeric batch maximum; keep client batches bounded and handle validation errors rather than inventing a fixed limit. The documented per-item status is ok, not_found or error, so one failed agent need not invalidate the other outcomes. This route was not live-verified; exact response layout, returned contact fields and item ordering are not established. Preserve each input’s outcome and absent fields, and honor consent, Do-Not-Call and suppression requirements. Batch access to public information is not permission for unsolicited outreach.

API Features

Screen-name array contact intake Place the selected public agent names in a JSON screen_names array rather than a comma-separated path field.

Three documented item statuses Handle ok, not_found and error separately for each submitted agent instead of collapsing all outcomes into HTTP success.

No invented contact batch maximum The documentation provides no fixed numeric limit; keep requests conservative and handle explicit validation feedback.

Suppression-aware directory refresh Update available public contact evidence without overriding contact preferences or inferring unpublished addresses.

Live API Demo

POST /api/project/zillow-real-estate/batch-agent-contacts

API Response (JSON)

{}

curl -X POST 'https://api.opendata-api.com/api/project/zillow-real-estate/batch-agent-contacts?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-agent-contacts?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

Authorized contact-directory refresh: update public contact fields for an existing reviewed set of agent screen names.
Per-agent contact outcome ledger: retain successful, missing and errored resolutions as separate directory states.
Directory contact-quality audit: identify which known profiles lack usable published contact information without creating substitutes.
Selective contact-resolution retry: isolate errored profile outcomes for a bounded follow-up while retaining successful and not-found results.

Frequently asked questions

What is the maximum contact batch size?

No fixed numeric maximum is supplied in the documentation available here. Keep batches bounded and handle validation feedback; do not assume the property or search batch limits apply.

How should I handle an individual agent failure?

The documented status values are ok, not_found and error. Preserve each outcome and retry only appropriate failures after inspection. Exact response keys and ordering were not live-verified.

Can I use the batch results for unsolicited outreach?

Public contact availability does not provide consent. Respect DNC, TCPA and other applicable obligations and preserve suppression preferences; do not infer missing email or phone fields.

Related operations

Guides

View Subscription Plans →

Resolve Public Contact Fields for Multiple Agents