zillowgroup.com
Zillow Group exposes multiple HTTP APIs and feed integrations for real estate, mortgage, rentals, and transactions, authenticated variously by Bridge Interactive account/API tokens, mortgage `partnerId`, Mortech third-party name plus license key, dotloop 3-legged OAuth, or undocumented/unknown mechanics for some feed and lead integrations.
- Zillow Group Data & APIs catalogdiscovered
- Zillow Group Bridge data APIsdiscovered
- Zillow Mortgage Get Current Rates APIdiscovered
- Zillow Mortgage Lender Reviews APIdiscovered
- Zillow Rentals Lead deliverydiscovered
- Zillow Rentals Feed integrationsdiscovered
- dotloop Transaction Management APIdiscovered
- Mortech Prospect Sync APIdiscovered
Create an account on the Bridge Interactive Platform registration page, then request the relevant Zillow Group dataset/API in the Bridge dashboard (API Access → Request Data Access → Zillow Group Datasets → agree to terms → choose dataset/API → Apply). After approval, get your token from the Bridge dashboard under Data Access → API Access Tokens. Zillow Group's developer pages describe this as password and access-token or API-key authentication depending on the dataset.
Use the Zillow Group Transaction Management access-request flow to get access to dotloop Connect, then follow the dotloop public API documentation to register and use a 3-legged OAuth app. The Zillow Group page identifies the auth model as OAuth 2.0 / 3-legged OAuth.
Submit the Zillow Group mortgage API access request form on any Mortech API page, such as Prospect Sync API. After partner approval / MSA where required, Zillow Group issues the two-part credential noted in the docs: Third Party Name plus License Key. The pages do not document the exact wire format for sending these values.
Submit the Zillow Group mortgage API request form from pages such as Get Current Rates or Lender Reviews, agree to the Terms & Conditions, and wait for Zillow Group to provision your partnerId. The docs state these APIs are No auth, partnerId required, but do not specify whether partnerId is sent in the query string, body, or headers.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing