How listing feeds work in Spain, what a Kyero-format XML file contains, and how stock moves into a CRM and back out to the portals.
Almost nothing in Spanish real estate is typed in twice, and the reason is the feed. An MLS feed is a machine-readable file, nearly always XML, published at a URL by one system and read on a schedule by another. It is how a listing gets from the agency holding the mandate to the twenty portals a buyer might search on, without anyone re-keying the bedroom count.
Formats vary in their tag names but not much in their content. A usable listing record carries:
That last one is where most feeds get interesting and most importers get it wrong. A new-build development is one marketing entity containing many units at different sizes and prices. Handled badly it arrives as forty near-identical listings that swamp a search results page. Handled properly it is one entry with the unit breakdown underneath, which is how buyers expect to see it.
Kyero’s XML schema became the common interchange format for Spanish and cross-border property data in the way a de facto standard usually happens: enough providers adopted it that adopting anything else costs you integrations. Most MLS providers selling into Spain will hand you a Kyero-format feed URL if you ask.
Lumio reads that format, and the importer is deliberately provider-agnostic rather than wired to any one supplier. You paste the feed URL your provider gave you, preview what the file actually contains before committing to anything, filter by town, feature, reference or price, and import the listings you want. Nothing about it is specific to which company generated the file.
There is a difference worth understanding. Importing copies listings into your own catalogue: they become your rows, you control publication, and they appear on your website and in your portal feeds. Subscribing means reading someone else’s catalogue live without owning a copy.
Both have a place. Imported stock is yours to market. Subscribed stock stays fresh without you doing anything. New-build catalogues generally work best as a live connection, because developer inventory changes faster than anyone re-imports.
New-build data comes from the developers, aggregated by a new-build MLS. 5 Min Agency ships with the HabiHub catalogue of Spanish new builds already connected and refreshed daily. It is there on day one, which matters when the alternative is an empty database.
It is worth being clear about what that is and is not. It is a bonus, not the product. Most agencies bring their own resale stock, second-hand listings they have won mandates on, and the new-build catalogue sits alongside those rather than replacing them. An agency with fifty resale mandates plus the new-build catalogue has a genuinely broad offer. An agency with only the catalogue has the same offer as everyone else who has it.
The other direction matters just as much. Once stock is in the catalogue it has to reach buyers, and buyers are spread across domestic Spanish portals and the international ones their own countries use. Lumio publishes to these today:
Publishing is per listing rather than all-or-nothing, so a property can go to Fotocasa only, or to the cross-border portals only, or to both. Each portal gets its own generated feed URL, regenerated whenever you publish or unpublish, and the portal polls it on its own schedule.
People use MLS feed and portal feed interchangeably and then get confused about what a system does. The distinction is direction. An MLS feed is normally inbound, bringing stock in so you have something to sell. A portal feed is outbound, publishing your stock where buyers search. The same XML format frequently serves both, which is exactly why one catalogue can sit in the middle and feed both directions.
That middle position is the CRM. Your website reads the same catalogue, which is what stops the three-way drift between what is on your site, what is on the portals, and what you actually still have available.
Feeds fail quietly, which is their worst property. A provider changes a tag name, an import silently drops a field, and nobody notices until a buyer asks why every listing says zero bathrooms. Things worth checking on any feed integration:
If you are choosing an MLS provider, ask for a sample feed URL before you sign anything and look at the file. It will tell you more about the quality of their data than the sales call will.
An MLS feed is a machine-readable file, almost always XML, that one system publishes and another reads on a schedule. It carries the listings themselves: reference, type, location, price, bedrooms, bathrooms, built and plot area, description, features and photo URLs. It is how an agency shares stock with portals and with other agencies without anyone retyping a listing.
Yes. Lumio reads Kyero-format XML, which is the common interchange format among Spanish and cross-border MLS providers, and the importer is provider-agnostic rather than wired to one supplier. You paste the feed URL your provider gives you, preview what it contains, and import the listings you want.
From the developers, usually aggregated by a new-build MLS. Lumio ships with the HabiHub catalogue of Spanish new builds already connected and refreshed daily, so there is stock to sell before you have won your first mandate. It sits alongside your own resale listings rather than replacing them.
7 are live today: Fotocasa, Kyero, ThinkSpain, SpainHouses, JamesEdition, Green-Acres and Properstar.
Direction. An MLS feed is usually inbound, bringing other stock into your system so you have something to sell. A portal feed is outbound, publishing your stock where buyers search. The same XML format often serves both, which is why one catalogue can feed both directions.