What is Octopus Prime Real Estate LLC?

Octopus Prime Real Estate LLC manages 5 data types including compass leads. Helps you organize, track, and share your work in 1 place for teams and solo users.

← Octopus Circle

XML FEED · PARTNER GUIDE

Partner Access

Octopus XML Feed
Integration Guide

Everything a partner needs to ingest, sync, and maintain Octopus Prime real estate listings — field-by-field, with stable identity rules and update-handling protocols.

60 min

The feed regenerates automatically every hour with a full snapshot of all live listings.

XML (Kyero V3)

Standard Kyero V3 XML schema — ingest with any Kyero-compatible parser or CRM.

<id>

Stable record ID + bedroom suffix. Key your entire catalogue on this field.

EUR (from AED)

Prices converted from AED to EUR at the live exchange rate on every refresh.

01 · Overview

What is the Octopus XML Feed?

A normalized, Kyero-compatible XML property feed of Octopus Prime's curated UAE developments. One project expands into multiple property entries — one per bedroom configuration with a listed price.

The feed is regenerated automatically every 60 minutes. Each refresh is a full snapshot — it contains every currently-available listing. There is no delta format; partners are expected to reconcile against their own stored catalogue using the <id> field.

Endpoint: https://octopus.realty/functions/generateKyeroXml

All prices converted AED → EUR using the live exchange rate.

Bilingual descriptions (EN + ES) included.

Handover date and payment plan carried inside <features>.

Floor plans embedded as floorplan-tagged <image> entries.

02 · Structure

Feed Structure

A <root> element wraps Kyero-style metadata and sibling <property> elements.

The high-level shape:

<root>
  <kyero>
    <feed_version>3</feed_version>
  </kyero>

  <property>
    <id>rec0RFLLtuQjVvOnY-2</id>
    <date>2026-03-14 19:48:50</date>
    <ref>REP-MARL-2BR</ref>
    <price>459340</price>
    <price_freq>sale</price_freq>
    <part_ownership>0</part_ownership>
    <leasehold>0</leasehold>
    <new_build>1</new_build>
    <type>apartment</type>
    <town>AL REEM ISLAND</town>
    <province>ABU DHABI</province>
    <country>UAE</country>
    <beds>2</beds>
    <baths>2</baths>
    <pool>1</pool>
    <surface_area><built>81</built><plot>0</plot></surface_area>
    <features><feature>Swimming Pool</feature><feature>Gym</feature><feature>Covered Parking</feature><feature>Handover: 2028-12-31</feature><feature>Payment plan: 20% down payment, 30% during construction, 40% on handover, 10% post-handover over 12 months</feature><feature>Full upfront payment discount: 5%</feature></features>
    <desc><en> ... </en><es> ... </es></desc>
    <images>
      <image id="1"><url>...</url></image>
      <image id="2"><tags><tag>floorplan</tag></tags><url>...</url></image>
    </images>
    <video_url>...</video_url>
    <prime>0</prime>
    <virtual_tour_url>...</virtual_tour_url>
  </property>

  <property> ... </property>
  ...
</root>

The <kyero> block carries the feed version only (Kyero V3 standard). Each <property> is one sellable unit variant.

03 · Identity & Stability

How IDs are formed — and what stays stable

The single most important section for partners. Get this wrong and your catalogue will duplicate or drop listings.

<id> — your primary key

Formed as {recordId}-{beds}.

Example: rec0RFLLtuQjVvOnY-2 — record rec0RFLLtuQjVvOnY (the project), bedroom suffix 2.

Stable forever for the lifetime of the listing. Editing price, photos, or descriptions in our source does not change the id. Only deleting the source record removes it.

<ref> — human-readable, semi-stable

Formed as {DEV(3)}-{PROJECT(4)}-{BEDS}.

Example: REP-MARL-2BR — REP (Reportage), MARL (Marlin 2), 2BR.

Do NOT use as primary key. If the developer or project is renamed in our source, the ref changes while the id stays the same. Match on id; store ref for display only.

Rule of thumb

Key on <id>. Store it permanently on first sight. On every sync, look up by id: if it exists → update fields; if new → insert; if a stored id is absent from the feed → the listing was removed, mark unavailable.

A single project with 3 priced bedroom configs produces 3 properties with 3 distinct ids — they are independent listings from a sync perspective.

04 · Field Reference

Every field, explained

Stability tags: STABLE (never changes for a given id) · SEMI (changes only on rename) · CHANGES (overwrite on sync) · FIXED (constant across all listings).

Field	Type	Stability	Description & handling
id	string	STABLE	Internal record ID + bedroom suffix (e.g. rec0RFLLtuQjVvOnY-2). Deterministic. The primary key you must store. Action: STORE permanently. Use this as your internal unique key for deduplication and updates.
ref	string	SEMI	Human-readable code: DEV(3)-PROJECT(4)-BEDS (e.g. REP-MARL-2BR). Derived from developer + project names. Action: Store, but do NOT use as primary key. If developer/project is renamed, ref changes while id stays the same.
date	datetime (UTC)	CHANGES	Listing timestamp formatted as YYYY-MM-DD HH:MM:SS (UTC). Action: Use for sorting/display only. Do not treat as last-modified; price/photo changes do not update this field.
price	integer (EUR)	CHANGES	Price converted from AED to EUR using the current exchange rate. Rounded to whole euros. Action: OVERWRITE on every sync if value differs. Always store the latest. Never preserve stale price.
price_freq	string	FIXED	Always 'sale' — these are listings for sale, not rentals. Action: Store. Constant.
part_ownership	integer	FIXED	Always 0 — whole-ownership properties, no fractional ownership. Action: Store. Constant.
leasehold	integer	FIXED	Always 0 — freehold properties (not leasehold). Action: Store. Constant.
new_build	integer	FIXED	Always 1 (these are all new-build developments). Action: Store. Constant.
type	string	STABLE	Normalized singular lowercase type: apartment, studio, villa, townhouse, penthouse, or duplex. Action: Store. Unlikely to change for a given project.
town	string	STABLE	District / area name (e.g. AL REEM ISLAND). Action: Store. May be refined over time.
province	string	STABLE	City / emirate (e.g. ABU DHABI, DUBAI). Action: Store.
country	string	FIXED	Always 'UAE'. Action: Store. Constant.
beds	integer	STABLE	Bedroom count for this unit variant (0 = studio, 1–5). Action: Store. Tied to id suffix — stable.
baths	integer	STABLE	Bathroom count for this unit variant. Action: Store. Enriched from source data.
pool	integer	FIXED	Always 1 — all developments include pool access. Action: Store. Constant.
surface_area.built	integer (m²)	STABLE	Built area in square meters (converted from sq ft). Action: Store. Recalculated only if source size changes.
surface_area.plot	integer (m²)	STABLE	Plot area in m². Real value for villas/townhouses with private land; 0 for apartments. Action: Store. Treat 0 as 'not applicable' (apartments). Recalculated only if source size changes.
features.feature	array of strings	CHANGES	Amenity / feature list for the project (e.g. Pool, Gym, Covered Parking). Multiple <feature> siblings. Action: OVERWRITE the whole array on sync. Replace your stored list; do not merge with old values.
desc.en / desc.es	text (XML-escaped)	CHANGES	Project description in English and Spanish, prefixed with the project name (e.g. 'MARLIN 2. ...'). XML-escaped — no CDATA sections. Action: OVERWRITE on change. Store both if you serve multilingual markets.
images.image	array (id + url)	CHANGES	Gallery images with sequential id attributes (id="1", id="2"…). Each URL is a stable proxy link ending in .jpg that 302-redirects to the current source image. Placeholder/invalid URLs are filtered out. Floor plans carry a <tags><tag>floorplan</tag></tags> marker. Action: URLs are stable proxy links (end in .jpg) that always 302-redirect to the current image. Safe to hot-link, or overwrite the array on sync and self-host if you prefer.
tags.tag (floorplan)	string	STABLE	Tag marker inside an <image> element indicating a floor plan resource. Value: 'floorplan'. Action: Store. Use as a flag to display a 'Floor plan available' badge and link to floor_plans_url.
video_url	URL	CHANGES	Standard Kyero video URL — mapped from the project's YouTube link. Action: OVERWRITE on change. Same value as youtube_video_url.
prime	integer	FIXED	Always 0 — Kyero's own 'prime listing' premium flag; not used by Octopus. Action: Store. Constant.
features (Handover)	text	CHANGES	Emitted as a <feature>: 'Handover: YYYY-MM-DD'. The expected handover/completion date. Action: OVERWRITE on change. May shift as construction progresses.
features (Payment plan)	text	CHANGES	Emitted as a single <feature>: 'Payment plan: X% down payment, Y% during construction, Z% on handover, W% post-handover over N months'. Only present parts are listed. Action: OVERWRITE on change. Up to four parts: down payment, during construction, on handover, post-handover (+ months).
features (Full upfront payment discount)	text	CHANGES	Emitted as a <feature>: 'Full upfront payment discount: X%' — only when a full-payment discount applies. Action: OVERWRITE on change. If absent, no full-payment discount is offered.
virtual_tour_url	URL	CHANGES	Kyero V3 standard field. 360° virtual tour link — allowed providers: Matterport, Nodalview, EyeSpy360, iStaging. Action: OVERWRITE on change. If absent, no virtual tour is available.

05 · Sync Protocol

How to ingest & maintain your catalogue

Treat every refresh as a full snapshot. Reconcile by id. Overwrite mutable fields.

STEP 1

Fetch & parse

Download the full XML every ≤60 min. Parse all <property> elements into a list keyed by id.

STEP 2

Reconcile by id

For each id: if new → INSERT into your catalogue. If exists → UPDATE mutable fields. For stored ids absent from feed → mark unavailable / delete.

STEP 3

Overwrite mutable

price, images, desc, handover (in features), payment plan (in features), video, virtual tour — always replace with latest. Never preserve stale values.

06 · Asset Hosting

Asset URLs — all hot-link safe

Every URL in the feed resolves to a stable external resource. No downloads or self-hosting required.

Safe to hot-link

<images> — stable proxy URLs (end in .jpg, 302-redirect to the current image).
<video_url> — YouTube link, stable.
<virtual_tour_url> — virtual tour on a 3rd-party platform (Matterport, Nodalview, etc.).

All URLs in the feed resolve to stable external resources — no download or mirroring required.

How image URLs work — the Octopus proxy

Every <image> URL in the feed is a stable proxy link ending in .jpg (e.g. .../functions/feedImage?p=recXXXX-2&i=1.jpg). On each request the proxy reads the current source URL from our cache and returns a 302 redirect to it. The cache refreshes every 60 minutes, so the proxy always resolves to a valid, fresh image — you can hot-link these URLs directly to your visitors.

In short: every URL in the feed is hot-link-safe — no download required.

07 · Update Scenarios

What to do when…

Real-world situations and the correct handling for each.

💰

Price changed

The price field updates on the next feed refresh. Overwrite the stored price with the new value. The id and ref remain identical — do not create a duplicate listing.

🖼️

Photos changed / rotated

Image URLs are stable proxy links — the same URL always resolves to the current photo via 302. You can keep the URL as-is on every sync, or overwrite your array if you self-host.

🕳️

A field is missing in an update

A missing optional field (video, virtual tour, floor plan image, post-handover plan) means the data is not available — clear it on your side. Do NOT preserve the previous value. A missing price or size means the unit variant was removed: delete that property from your catalogue.

➕

New bedroom variant added

A new id appears (e.g. recXXXX-5 for a newly priced 5BR). Treat it as a new listing. Existing ids are untouched.

➖

A property disappeared from the feed

If an id you stored is no longer present in a full feed refresh, the project/variant was removed or sold out. Mark it unavailable or delete it from your catalogue — do not keep selling it.

🔁

Developer or project renamed

ref will change (it is derived from names). id stays the same. Match on id, update the ref + display name. Never duplicate.

💱

Exchange rate moved

price (EUR) is recomputed from the source AED price × current rate on every generation. Expect small price drift between refreshes even if the AED price is unchanged. Always overwrite price.

🏗️

Handover date shifted

handover updates on change. Overwrite and reflect on your listing. No id change.

08 · Rules of Engagement

Do's & Don'ts

The short version of everything above. Print it. Pin it.

Do

Key everything on the id field — it is stable for the lifetime of the listing.
Overwrite mutable fields (price, images, descriptions, handover, payment plans) on every sync.
Treat each feed refresh as a full snapshot: compare ids, add new, update existing, remove missing.
Hot-link image, video and virtual-tour URLs directly — they are stable. No download or self-hosting is required.
Poll the feed at most once per 60 minutes — that is our regeneration cadence.

Don't

Do not use ref as your primary key — it can change if names are edited.
Do not expect brochure, fact-sheet or furnishing fields — they are not part of the Kyero V3 schema and are not in the feed. Request them via your Octopus contact if needed.
Do not preserve stale values for fields that go missing — clear them.
Do not keep selling listings whose id has disappeared from the feed.
Do not poll more frequently than 60 min — you will get identical payloads.
Do not modify or 'improve' descriptions — they are curated by Octopus.

09 · Worked Example

Anatomy of one property

A real entry from the feed, annotated.

rec0RFLLtuQjVvOnY-2

ref

REP-MARL-2BR

project_name

MARLIN 2

price (EUR)

459.340 €

payment plan

20% / 30% / 40% / 10%

handover

2028-12-31

This single project (Marlin 2) likely produces multiple property entries in the feed — one per bedroom configuration with a listed price+size. Each has a distinct <id> suffix and is an independent listing for sync purposes.

Need integration support?

If anything in this guide is unclear, or you hit an edge case not covered here, reach out to your Octopus Circle contact. We will help you wire up the feed correctly the first time.

Octopus Prime Real Estate LLC · RERA ORN 55603 · Licensed in Dubai, UAE