OpenHouse
Gets a single open house by OpenHouseKey
Both methods are valid and return the same result: a single OpenHouse entity identified by its unique OpenHouseKey. The path-style is more intuitive and commonly used in RESTful APIs. The function-style follows OData conventions and may be required in certain query contexts (e.g., when the key contains special characters or is not a simple numeric ID).
<b>Path-style access: </b>/odata/v1/OpenHouse/{OpenHouseKey}
<b>Example: </b>/odata/v1/OpenHouse/1000
<b>Function-style access: </b>/odata/v1/OpenHouse('{OpenHouseKey}')
<b>Example: </b>/odata/v1/OpenHouse('1000')
get/odata/v1/OpenHouse/{OpenHouseKey}
Path parameters
OpenHouseKeystring required
A unique identifier for this record from the immediate source
Query parameters
$selectstring
Selects which properties to include in the response.
Response
OK (DDF.Core.Entities.OpenHouse object)
Example response
{
"@odata.context": "https://localhost:7051/odata/v1/$metadata#DDF.Core.Entities.OpenHouse",
"OpenHouseKey": "12345",
"ListingKey": "12345",
"ListingId": "1",
"OpenHouseDate": "2021-01-01",
"OpenHouseStartTime": "12:00:00.00",
"OpenHouseEndTime": "12:00:00.00",
"OpenHouseRemarks": "OpenHouseRemarks",
"OpenHouseType": "Public",
"OpenHouseStatus": "Active",
"LivestreamOpenHouseURL": "\"https://www.youtube.com/watch?v=i-09UtAH10A\""
}