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.
Provider:ZooplaAsyncAPI: v3.0.0Spec: Zoopla Lead Push ServiceOperations: 2Messages: 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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.