Scope: write:enquiries

The replacement for V1's residential/sales/{id}/viewing, call-back and
information, kept as close to them as the data allows. The fields are named as this
endpoint's GET returns them.

salesLifecycleListingId is the listing the visitor was looking at, as in V1. Any
listing the API key can reach is accepted, on any channel and in any state. The enquiry
belongs to the listing's team, so a client key can send leads for all its teams.

type and up to three preferredTimes are written into the enquiry's comment
after the visitor's own comment, as V1 writes them, with the times in UK time.
Either firstName or lastName, and either emailAddress or
phoneDaytime, are required.

The enquiry is created unprocessed, with source vendorWebsite. The team's beacon,
auto-responder and a push to agents' phones follow, as for a portal lead; none of them can
fail the request.

POST /v2/sales/enquiries
{
"salesLifecycleListingId": 99120,
"type": "viewing",
"firstName": "Sam",
"lastName": "Example",
"emailAddress": "[email protected]",
"phoneDaytime": "07700 900123",
"comment": "Could I see it on a Saturday?",
"preferredTimes": ["2026-11-07T10:00:00Z", "2026-11-07T14:30:00Z"]
}