Website integration overview
Source-reviewed draft; deployment and release verification pending.
Draft — source-reviewed on 22 October 2026. Deployment readiness and live API behavior remain unverified.
Feature 110 exposes a public website projection of eligible properties. Use it to design listing cards, detail pages, filters, map results, galleries and a public contact card. It is not a copy of the internal CRM property object.
Operations
| Method and default path | Consumer purpose |
|---|---|
POST /api/v1/public/properties/search | Search an area with filters and return paginated summaries. |
GET /api/v1/public/property-reference | Load controlled values, destination coverage, active catalogs and optional city-scoped LocalAreas. |
GET /api/v1/public/properties/{public_id} | Read an eligible property detail, optionally selecting operation=SALES or operation=RENTAL. |
GET /api/v1/public/properties/{public_id}/images/{asset_id} | Read the currently approved property image derivative. |
GET /api/v1/public/agent-images/{asset_id} | Read an eligible public agent photo. |
The prefix shown is the source default. There is no verified deployment URL in this draft.
Recommended data flow
- Load reference metadata. Read destination coverage rather than drawing a search outside the configured extent.
- Build an initial bounds request with
destination: "TENERIFE"and a required operation filter. - Render returned summaries as cards and public points as markers. Unknown fields are not a reason to load internal CRM data.
- On selection, request detail using the same public identifier and operation context.
- Load only the returned image URLs and explicitly supplied public agent information.
- Re-check availability on future requests and handle withdrawal with an unavailable state.
Public model boundaries
Summary and detail have different requirements. Search summaries always contain a valid public location; eligible detail may omit location, including when the property's location is hidden. A property can therefore have a valid detail page and be absent from map search.
Detail adds descriptions, characteristics, a gallery, the supported operations/prices and optional agent/address information. It does not return a booking availability calendar, private investment profile, owner contacts, private notes or CRM documents.
Design while deployment is pending
Develop React components against synthetic fixtures and a transport interface. Keep your display model separate from the literal DTO. For example, heading, formatted price text and a translated subtype label can be view-model properties derived from the public data, but are not wire fields.
Use the field-level guidance in Public Property model, Marketing and characteristics and Media and agents. Show independent loading/empty/error states for property data, reference choices and images.
Related operations
All operations above form the initial Website Property API definition. No CRM management, publication mutation, enquiry submission or reservation endpoint is included.
Updated 1 day ago