Nothing retyped. Ever.
Connect the XML feed your brokerage already publishes to the portals. Reference, price, specifications, description and the permit number arrive with it — photographs do not, and every listing lands as a draft you approve.
The portals already hold every listing you have. Retyping them into another tool is the most expensive hour of your week, and it is still wrong by Friday.
The same listing typed into the office CRM, the portal and your own page.
Three prices, three photo sets, three permit dates.
Office tools show you the whole office. Your page is yours alone.
How it works
The whole workflowConnect the feed
Paste the XML URL your brokerage already publishes to the portals. It is encrypted before it is stored with a key the database does not hold, and nothing in this product decrypts it for display — not even for you.
Say what the feed IS
Your full inventory, or a partial one. A full feed may withdraw a listing it stops carrying; a partial feed only ever adds. You answer that once, and no document can change the answer — which is what stops a twenty-four-hour changes feed taking a whole brokerage offline.
Everything arrives as a draft
Reference, price, specifications, description and the permit number come across. Photographs do not, and the feed cannot carry the permit’s dates, the issuing licence or the Madmoun link — so every import ends on one completion screen before it can go live.
Changes follow the feed
A price that moves in the feed moves on your page, and the brochure is built at the moment it is asked for, so it cannot be stale. The scheduled run happens overnight; “Sync now” is there for the afternoon a price changes.
Authenticated encryption, because the plaintext is a URL this system then fetches. The key lives outside the database.
What you get
Your listings, once, without typing them twice.
Property Finder and Bayut settled on the same XML document; dubizzle has its own. Say which one the URL is and the mapping is done — there is nothing to configure per field.
Keep the portal link on the listing as its source of truth and as a duplicate check against your own reference numbers. Nothing requests it. Every address a feed URL does resolve to is checked against the private ranges before a socket opens, and again inside every redirect.
Type a property in, or upload a developer’s brochure for an off-plan project and review what it proposes field by field, with the quote it read each value from. The permit, project and escrow numbers are never proposed — confirming those against the register is the broker’s own duty, and a proposal would turn it into a click.
Only a feed you have declared to be your full inventory can withdraw anything, and only a listing it carries itself. A withdrawn listing goes inactive rather than being deleted, so the link stops working and the Activity it collected stays attached to the row.
Retyping, or connecting
Same listings · same reference numbers| Retyping listings | A connected feed |
|---|---|
| An hour a week, at least | One URL, pasted once |
| Wrong by Friday | Re-read on every run |
| Permit dates remembered by hand | Permit number imported, expiry read at the page |
| A copy that drifts from the portal | One reference, matched on your own numbers |
| Off-market stock in a notes app | A draft nobody but you can open |
What we never do
The rules this feature runs on, on every plan.
Fair questions
More on the home page, or ask a person.
Write to us
I do not have the feed URL.
Your brokerage does — it is the document they already publish to the portals. Ask your office for the XML endpoint, and if you are not sure what to ask for, write to us and a person will tell you exactly what to request.
Do the photographs come across?
No, and that is the honest answer rather than a temporary one. A feed carries image URLs; showing a photograph here means fetching it through the same address checks as the feed, writing it as an original that is never overwritten, and processing it — a pipeline rather than a column. Upload them once and every page, brochure and client link uses them.
What happens if the feed comes back empty?
Nothing is withdrawn and the run is marked failed. An expired token, a login page and an error envelope all parse to zero listings, and every one of those is likelier than a brokerage having sold its entire book overnight.
Can a feed take a page that is already live offline?
Only a feed you have declared to be your full inventory, and only for a listing that arrived through it. A partial feed never withdraws anything — the database raises an error rather than accepting one — and a listing you typed in is never touched by any feed.
What about listings that are not mine?
A feed belongs to one Organisation and every listing it brings in lands as a draft on your own Agent profile, which is the only thing your public page renders. Publishing also needs your broker number on your profile, so nothing can go live under a licence you have not entered.
Works with
Connect the feed tonight.
Fourteen days, no card. One URL, and nothing publishes until you have read it.