Zillow agent reviews

GET https://api.api.sh/zillow/v1/agent/reviews
1 credit / call real estate try it in the playground →

Every review of a Zillow agent or team, 10 a page: rating, date, reviewer, text, the transaction it was about, sub-ratings (local knowledge, process expertise, responsiveness, negotiation skills), which team member it was for, and the agent's reply. Filter by the service the client got and sort by date or rating; total counts the reviews for the chosen filter.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
url string The agent's Zillow profile link (https://www.zillow.com/profile/<screen name>). Example: https://www.zillow.com/profile/everydoorrealestate
screen_name string The agent's screen name, instead of url.
zuid string The agent's encoded_zuid (from /zillow/v1/agent), instead of url or screen_name: skips the profile lookup; total is then null.
page integer Page number (10 reviews a page).
sort newest | rating_desc | rating_asc Order (default newest).
service all | buy | sell | buy_and_sell | no_deal | rental Only reviews for this service (default all).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/zillow/v1/agent/reviews?url=https%3A%2F%2Fwww.zillow.com%2Fprofile%2Feverydoorrealestate" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.