Alto (Vebra / Zoopla) · Schema
ViewingRequest
Real EstateUnited KingdomPropTechProperty ListingsCRMProperty ManagementRentalsConveyancingEstate AgencyTenancyWebhookEventLettingsSales ProgressionProperty DataReal Estate Software
Properties
| Name | Type | Description |
|---|---|---|
| negotiatorId | integer | Required: The unique identifer of the negotiator |
| branchId | integernull | Optional: The branch in which to record the viewing diary event. When omitted, defaults to the negotiator's default branch. |
| applicantIds | array | Required: The unique identifer of the applicant(s) |
| propertyId | integer | Required: The unique identifer of the property |
| startDate | string | Required: The start date and time in ISO 8601 format of the viewing appointment to be created. Interpreted as UK local diary time: a value with a UTC marker (a trailing `Z`) or an explicit offset is c |
| endDate | string | Required: The end date and time in ISO 8601 format of the viewing appointment to be created. Interpreted as UK local diary time: a value with a UTC marker (a trailing `Z`) or an explicit offset is con |
| notes | stringnull | Optional: Additional notes to accompany the viewing appointment being created. |
| isConfirmed | boolean | Optional: Marks viewing as confirmed; this will NOT send out confirmation emails and texts Default if not set: false |
| meetingPlaceType | string | Optional: Sets where the negotiator will meet for the viewing; Default if not set: AtTheProperty |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/alto-vebra/json-schema/alto-vebra-viewing-request-schema.json",
"title": "ViewingRequest",
"x-generated": "2026-11-04",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/alto-vebra-appointments-api-openapi.yml#/components/schemas/ViewingRequest",
"required": [
"applicantIds",
"endDate",
"negotiatorId",
"propertyId",
"startDate"
],
"type": "object",
"properties": {
"negotiatorId": {
"maximum": 2147483647,
"minimum": 0,
"type": "integer",
"description": "Required: The unique identifer of the negotiator",
"format": "int32"
},
"branchId": {
"type": [
"integer",
"null"
],
"description": "Optional: The branch in which to record the viewing diary event.\nWhen omitted, defaults to the negotiator's default branch.",
"format": "int32"
},
"applicantIds": {
"type": "array",
"items": {
"type": "integer",
"format": "int32"
},
"description": "Required: The unique identifer of the applicant(s)"
},
"propertyId": {
"maximum": 2147483647,
"minimum": 0,
"type": "integer",
"description": "Required: The unique identifer of the property",
"format": "int32"
},
"startDate": {
"type": "string",
"description": "Required: The start date and time in ISO 8601 format of the viewing appointment to be created.\nInterpreted as UK local diary time: a value with a UTC marker (a trailing `Z`) or an explicit offset\nis converted to UK local time (Europe/London); a plain local value with no offset is taken as-is.",
"format": "date-time"
},
"endDate": {
"type": "string",
"description": "Required: The end date and time in ISO 8601 format of the viewing appointment to be created.\nInterpreted as UK local diary time: a value with a UTC marker (a trailing `Z`) or an explicit offset\nis converted to UK local time (Europe/London); a plain local value with no offset is taken as-is.",
"format": "date-time"
},
"notes": {
"type": [
"string",
"null"
],
"description": "Optional: Additional notes to accompany the viewing appointment being created."
},
"isConfirmed": {
"type": "boolean",
"description": "Optional: Marks viewing as confirmed; this will NOT send out confirmation emails and texts\nDefault if not set: false"
},
"meetingPlaceType": {
"enum": [
"Unspecified",
"AtTheOffice",
"AtTheProperty"
],
"type": "string",
"description": "Optional: Sets where the negotiator will meet for the viewing;\nDefault if not set: AtTheProperty"
}
},
"additionalProperties": false
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/alto-vebra-viewing-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
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.
A second provider on the same verified email joins the account you already have.