Zillow Agent Contact API - Published Phones and Websites

Supply a known public screen_name for the documented contact view. Available data can include phone numbers in E.164 and display form, email only when published, website, social links, brokerage office address and licenses. The actual response layout and contact completeness were not live-verified. An absent email or phone is unavailable, not permission to infer or reconstruct one. Public contact information does not authorize unsolicited outreach. Confirm applicable TCPA, Do-Not-Call and other legal requirements, respect consent and suppression preferences and verify professional credentials separately before using the information.

API Features

Published contact-field projection Research documented phone, website and optional published email fields without inferring private contact data.

Phone presentation variants The documented contact resource includes E.164 and display phone forms when available; inspect actual field names before parsing.

Brokerage office association Keep available office-address and license context attached to the known profile rather than substituting a property address.

Consent-aware contact use Separate public discoverability from permission to contact; respect TCPA/DNC obligations and suppression preferences.

Live API Demo

GET /api/project/zillow-real-estate/get-agent-contact

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/zillow-real-estate/get-agent-contact?key=<API_KEY>&screen_name=<screen_name>'

curl -X GET 'https://api.opendata-api.com/api/project/zillow-real-estate/get-agent-contact?key=<API_KEY>&screen_name=<screen_name>'

📢

Need Help?

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

Use Cases

User-opened agent contact panel: display available published office contact fields only after the user selects a known profile.
Authorized directory contact reconciliation: compare an existing record with available public website and office fields.
Contact completeness review: mark unavailable email and phone fields for manual review without generating substitutes.
Consent and suppression check preparation: pass published contact references to an independently managed compliance workflow before outreach.

Frequently asked questions

Will every agent have an email address?

No. Email is documented only when publicly published. Preserve absent values as unavailable rather than infer an address from the agent’s name or website.

Does a returned phone number authorize marketing calls?

No. Public availability is not consent. Apply relevant TCPA, DNC and other legal obligations and respect contact and suppression preferences before outreach.

Can I treat office contact data as verified licensing information?

No. Office, phone and license context are documented profile fields, not authoritative current credential verification. This endpoint’s response and completeness were not live-tested.

Related operations

Guides

View Subscription Plans →

Get Published Agent Contact and Office Information