Kyero Integration

Because Kyero is built around imported data rather than manual entry, the feed effectively is the listing relationship: Kyero explicitly instructs agents to manage property details in their source system, not inside the Kyero control panel, because the daily import overwrites whatever is stored on Kyero.com. A properly structured feed means price changes, new instructions, availability updates and sold/withdrawn properties propagate automatically, and it prevents listings from falling into Kyero's "incomplete" state — a status applied (and hidden from public search) whenever the importer can't recognise a valid price, town, province or property type. For an agency advertising the same portfolio across Kyero and other overseas-property channels, feed automation is what keeps every destination in sync instead of drifting out of date.

Kyero property data is submitted using the Kyero XML feed, built on the current v3.x import specification — one of the most widely used property data formats among international estate agents, alongside the BLM standard. A handful of structural rules are strictly enforced:

1. The feed must be an absolute feed containing every property you want listed or updated, not an incremental diff — properties omitted from a submitted feed are treated as removed.
2. Each feed URL may only carry properties for a single Kyero account; agencies managing multiple Kyero accounts need a separate feed URL per account (the URL can embed basic-auth credentials, e.g. username:password@yourdomain.com).
3. The file must be valid UTF-8, with all tags written in lowercase (the format is case-sensitive) and no CDATA blocks.
4. Reserved XML characters inside text content must be entity-encoded: <, >, &, ', ", and 
 for line breaks within a description.
5. Each property only registers as changed when its <date> tag (format YYYY-MM-DD HH:MM:SS) advances — an invalid or stagnant date tag causes that property to fall back to weekly-only processing.

Kyero geographically scopes the import to properties in its supported markets and provides a dedicated validator at validator.kyero.com so agents can check structure and encoding before submitting a feed URL for approval.

The XML import specification defines both mandatory tags (needed for a property to be accepted and shown publicly) and optional tags that enrich the listing. The core set:

Feedance takes your existing property data — a PMS export, CRM database, spreadsheet, or an existing feed built for another channel — and restructures it to match Kyero's exact XML import rules, rather than requiring your team to hand-build and maintain a compliant file. In practice that means: mapping your source fields to the lowercase Kyero tag set (id, price, town, province, beds, baths, images, and the rest), entity-encoding special characters automatically so a stray ampersand or apostrophe in a description never breaks the parse, generating one absolute (full-catalogue) feed per Kyero account, and advancing each property's <date> tag only when its underlying data actually changes — so updates register with Kyero without artificially forcing every property into reprocessing. Feedance hosts the resulting file at a stable HTTPS URL (with basic-auth credentials if you keep the feed private), which you then submit through Kyero's support ticket process for the initial validator check and approval, exactly as Kyero's own onboarding instructions describe.

Kyero's processing cadence depends on the agency's package: accounts on a Prime package are processed nightly, five nights a week (Sunday/Monday through Thursday/Friday), with feeds typically picked up around 01:30 CET once a property is live. Accounts on a Free package are processed once per week. Feeds that fail validation or otherwise misbehave are demoted to weekly-only processing, or disabled entirely, until the issue is fixed — so a feed that's technically valid but rarely changes its <date> tags won't get more frequent treatment than the package allows, but a broken feed can get less frequent treatment than it's entitled to.

Kyero's documented failure modes center on a few recurring issues:

1. Incomplete properties — a property is marked incomplete and hidden from public search whenever the importer can't recognise a valid price, town, province or property type; agents can hand-edit the property directly on Kyero.com to fix it, but the fix will be overwritten by the next feed import unless the source data is corrected.
2. Unescaped special characters — ampersands, angle brackets, quotes and apostrophes left un-encoded in free-text fields (like descriptions) break XML parsing; Kyero requires entity encoding (&, <, >, ', ") rather than CDATA blocks.
3. Stale or invalid <date> values — since Kyero only treats a property as updated when its date tag advances, a feed generator that doesn't bump this field on real changes will see updates silently fail to register.
4. Placeholder image URLs — submitting "no image available" or stock placeholder photos instead of omitting the tag is explicitly disallowed.
5. Import failures — if a feed import fails outright, Kyero's monitoring system sends an automatic email notification to the agent, and agents can self-check status any time via validator.kyero.com or by reviewing live properties in their Kyero account.

A few practices, drawn from Kyero's own guidance, help a feed stay in good standing and process on the fastest schedule your package allows: run every feed through validator.kyero.com (structure) and a UTF-8/W3C check (encoding) before submitting a new or changed feed URL; keep the <id> and <ref> values for each property stable across every export so Kyero — and any other channel you distribute to — can reliably match updates to the same listing; populate desc with language sub-nodes rather than relying on features alone if you're targeting Kyero's international buyer audience; keep all 50 image slots filled with real, stable photo URLs rather than a placeholder; and manage every property edit in your source PMS, never inside the Kyero control panel directly, since manual edits are overwritten by the next automated import.

Is a Kyero feed the same as a Google Merchant Center or shopping feed?
No. Kyero imports real-estate listings (price, location, beds/baths, plot size, images), not product/e-commerce attributes like GTIN or SKU — the Kyero XML import specification is a real-estate-specific schema.

What format does Kyero require?
The Kyero XML feed, currently on its v3.x import specification, submitted as a single absolute (full-catalogue) file per Kyero account.

Can one feed cover multiple estate agent accounts?
No — each feed URL is tied to a single Kyero account; agencies with multiple accounts need a separate feed URL for each.

How often is my feed refreshed on Kyero.com?
Prime-package accounts are processed nightly (five nights a week); Free-package accounts are processed once a week; non-conforming feeds may be dropped to weekly or disabled until fixed.

What happens if a property is missing required data?
It's flagged "incomplete" and hidden from public search until price, town, province and property type are all present and recognised.

How do I know if my feed is working?
Check live properties in your Kyero account, run the feed through validator.kyero.com, or wait for Kyero's automated email alert, which is sent if an import fails.