AsyncAPI channel · Zoopla · Zoopla Lead Push Service

/

The member's configured recipient endpoint. Zoopla sends one HTTP POST per lead. When one endpoint receives both types, the top-level key on the payload distinguishes them.

Open source AsyncAPI → All Zoopla channels Zoopla provider profile
Provider: Zoopla AsyncAPI: v3.0.0 Spec: Zoopla Lead Push Service Operations: 2 Messages: 2

Channel address

/

Operations

receive
receiveApplicantLead
Receive an applicant lead (a consumer looking to buy or rent).
receive
receiveAppraisalLead
Receive an appraisal lead (an owner asking for a valuation).

Messages

applicantLead
A consumer has enquired about buying or renting a property.
Content-Type: application/json
appraisalLead
A property owner has requested a valuation.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.