AsyncAPI channel · Alto (Vebra / Zoopla) · Zoopla Lead Push Service

/

Zoopla sends one HTTP POST per lead. The top-level key is the discriminator: "applicant" for consumers looking to buy or rent, "appraisal" for consumers looking to sell or let. Delivery can be filtered per endpoint on four independent flags — applicant leads, appraisal leads, sales leads and lettings leads.

Open source AsyncAPI → All Alto (Vebra / Zoopla) channels Alto (Vebra / Zoopla) provider profile
Provider: Alto (Vebra / Zoopla) AsyncAPI: v3.0.0 Spec: Zoopla Lead Push Service Operations: 1 Messages: 2

Channel address

/

Operations

receive
receiveZooplaLead
Zoopla POSTs a single applicant or appraisal lead to the partner endpoint.

Messages

ApplicantLead
A consumer enquiry from the Zoopla portal about buying or renting a property.
Content-Type: application/json
AppraisalLead
A consumer request from the Zoopla portal for a valuation — selling or letting.
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.