Connect Your CRM to Domovita - Free Property Feed Import

Automated Property Feed Import

Import properties automatically from your CRM or property management software. Set everything up yourself from your Branch Management dashboard - no need to contact support.

What is a Property Feed?

A property feed is an automated way to sync your properties from your existing system to Domovita. We have live feeds today from Alto, Jupix, Loop, Street, Rex and Apex27. If you use another system, tell us which one and we'll check it with you first - each system's files need testing with us before we can say it works. Instead of manually entering each property, your CRM sends data to Domovita and we import it automatically.

Supported Feed Formats

• BLM (Rightmove V3): Industry-standard format used by Rightmove, Zoopla, OnTheMarket. Full 42-field coverage.
• XML: Auto-detects Vebra/Alto, Kyero, Jupix, and generic Rightmove-style XML.
• CSV/TSV: Spreadsheet-style files with flexible column matching. Great for bulk uploads from Excel or Google Sheets.
• JSON: Modern JSON format for developer-built integrations.
• RTDF (Real-Time Data Feed): Send individual property updates in real time as they change in your CRM.
• EAF (Estate Agent Feeds): Third-party middleware that connects to a range of CRMs and forwards listings to portals. We can receive its feed; EAF sets its own price, so check with them.

Feed Import Methods

1. Direct CRM connection - Alto / Vebra (self-service, minutes to set up)

If you use Alto or Vebra, you no longer need FTP at all. In Branch Management → API & Feed Integrations, open the Alto / Vebra direct feed form and enter your datafeed ID, API username and API password - these are issued by Vebra/Alto (ask your Alto account manager, or find them in Vebra's feed settings), not by Domovita. Pick the API version (v13 is current), click Test Connection to check the credentials, then Save. We poll your feed automatically - with the default 30-minute setting, every 30 to 45 minutes; you can set anything from 15 minutes to 24 hours - and the card shows the feed status, last import time and property count.

Using Jupix? Jupix does not use this form - send us your Jupix XML feed link and we connect it for you (see the table below).

2. Direct REST API Feed - Loop and other REST-API CRMs

Email This email address is being protected from spambots. You need JavaScript enabled to view it. and ask for an API key for Domovita - Loop issues it to you as their customer. Issuing one is Loop's decision, so we cannot promise a timescale, but the first agency to do this had theirs within a few hours. Once you have a key, paste it into the Direct REST API Feed section in Branch Management, click Test Connection, then Save. With the default setting we check Loop about every 30 minutes, sometimes up to an hour.

One thing to check: we read the properties you have ticked for one Loop marketing channel, api unless you choose another. Pick your channel in the Direct REST API Feed section (for example Your website or Rightmove), then click Test Connection to see how many listings it finds before you save.

3. Inbound SFTP - we host the server, your CRM pushes (self-service)

If your CRM pushes files to an SFTP destination, click Set up SFTP feed in Branch Management. Credentials are generated automatically and appear on the card within a couple of minutes (the page refreshes itself): host feeds.domovita.co.uk, port 22, a username like dvfeed-123, and a password you can reveal and copy (branch admins only) or regenerate at any time - the old password stops working immediately. Point your CRM's export at those details and drop XML, BLM or CSV files in the root folder; we import on the next scan, every few minutes. Remove the feed whenever you like - access is revoked within a couple of minutes, and its listings come off Domovita until you set SFTP up again, when we pick up where you left off.

4. FTP / SFTP Auto-Pull (we pull from your CRM's server)

If your software can export your listings to an FTP server, Domovita can connect to that server on a schedule and pull your files - hands-free once configured. Whether your provider offers an FTP export for a new portal, and whether they charge for it, is up to them.

How to set it up: - Go to Branch Management (click your avatar, then "Branch Management") - Scroll to the FTP / SFTP Import section - Enter your CRM's FTP credentials (host, username, password, path) - Click "Test Connection" to verify it works - Click "Save Connection" - Domovita polls automatically during business hours (7am-6pm)

Where do I get FTP credentials? From your software provider - ask for an FTP export to a new portal. If you use Alto, use the direct connection in method 1 instead; if you use Jupix, send us your Jupix XML feed link and we connect it for you.

5. File Upload (Push via API)

Upload BLM, XML, CSV, or JSON files through our API endpoints. Your CRM pushes the files to Domovita.

• Best for: Automated scheduled uploads, CRMs that push rather than host FTP
• Requires an API key (generated from your Branch Management page)

6. Real-Time API (RTDF)

Send individual property updates via our RTDF endpoint as they change in your CRM. No batch file needed.

• Best for: Live CRM integrations, bespoke software, instant updates

7. Street.co.uk

If you use Street, Domovita reads the Street Property Feed API directly. Street describes its API as free and open, so there is nothing to buy and no middleware in between. A Company admin in Street goes to Settings → Applications and creates a Property Feed API token. A branch admin then pastes it into the Street Direct Feed section in Branch Management, clicks Test Connection, ticks the box to confirm they are authorised to connect the account, and saves. There is no need to email the token to anyone, and we store it encrypted. The first import runs on our next check, usually within half an hour during the day. After that, on the standard setting, we check Street about every hour through the day (not overnight), sometimes up to 90 minutes, so price changes, sales agreed and withdrawals reach your listings without anyone re-keying them. Properties you mark as low profile in Street are never imported, and embargoed ones wait until the embargo ends. To disconnect, click Remove in the same section and delete the token in Street.

Getting Your API Key

You can do this yourself - no need to contact support.

1. Go to Branch Management (avatar menu or /branchmanage)
2. Scroll to the API & Feed Integrations section
3. Click "Generate API Key"
4. Your 64-character API key appears immediately
5. Click "Copy Key" to copy it to your clipboard

Your API key authenticates all feed requests for your branch. Include it in every request as an HTTP header:

X-Feed-Api-Key: your_64_character_api_key_here

Key management (admin only): - Regenerate: Creates a new key (old key stops working immediately - update your integrations) - Revoke: Disables API access entirely until you generate a new key

API Key Security

• Keep it secret: Treat your API key like a password. Never share it publicly or commit it to code repositories.
• One key per branch: All team members share the same branch API key.
• Regenerate if compromised: Use the "Regenerate Key" button in Branch Management if you suspect exposure.
• Role access: Only branch admins can generate, regenerate, or revoke keys. The key is shared by the whole branch for feed requests.

Feed Source Settings

When you set up an FTP connection or use the API, Domovita creates a feed source for your branch with these settings:

• Name: Auto-generated from your branch name and connection type
• Feed Type: The format (BLM, XML, CSV, JSON, FTP, SFTP, etc.)
• API Key: Your unique authentication token
• Auto-Publish: Properties go live immediately (default for approved agents)
• Branch ID: Ensures imported properties are tagged to your branch

Import Process Overview

1. Your CRM exports data - either to FTP (we pull) or via API (you push)
2. Domovita parses the file - auto-detects format, extracts property data
3. Validation - required fields checked (price, postcode, property type)
4. Images downloaded - from URLs in the feed data, stored on our CDN
5. Properties created or updated - matched by your unique reference (agent_ref)
6. Results logged - import counts (created, updated, skipped, errors) saved in your feed log

Update vs Create Logic

• Each property has an agent_ref (your internal reference number)
• If that agent_ref already exists for your feed source: UPDATE the existing listing
• If it's new: CREATE a new listing
• This prevents duplicates and keeps your listings in step with your CRM

Removing and reconnecting a feed

You can remove a feed at any time from Branch Management. Removing it stops the imports, deletes the login details or key you gave us, and takes that feed's listings off Domovita - they are hidden, not deleted.

To reconnect, set up the same type of connection again for the same branch (for example, enter new Alto details in the Alto / Vebra form). We match each property to your existing listing by your CRM's own reference and update it, so you do not get duplicates, and the photos and enquiries already on each listing stay with it. Each listing comes back as your CRM sends it again.

After you reconnect, your first import tidies up: with a full feed (SFTP, FTP, a feed link, Loop or Street), anything no longer in your CRM stays off the site. Alto / Vebra still does not tell us about withdrawn properties, so contact us for those.

If you move to a different type of connection (for example from Alto direct to SFTP), contact us first so we can carry your listings across rather than import them a second time.

Full Replacement Mode

When you send a batch feed (BLM, XML, CSV, JSON) - by upload, FTP, SFTP or a feed link we fetch - Domovita treats it as your complete, current portfolio by default. Any property in Domovita that's missing from the new feed gets automatically unpublished. Our Loop and Street connections work the same way. When you mark a property sold, sold STC or let agreed in your CRM, its status updates on the next import and it drops out of our default search results; when your CRM stops sending it, it is unpublished.

Alto / Vebra is different: that connection only receives the listings that changed, so a property you withdraw in Alto is not taken down automatically. Contact us and we will remove it.

You can disable this with ?full_replacement=0 on the upload endpoint if you prefer additive-only imports.

Handling Images

• BLM files: Include an image ZIP bundle in the same upload request
• XML/JSON/RTDF: Provide image URLs in the data - we download and store them automatically
• Supported formats: JPG, JPEG, PNG, GIF, WEBP
• Storage: All images stored on Cloudflare R2 CDN for fast delivery

Supported CRM Systems

We have live feeds from the systems below today. This is how each one connects:

Quick Start Checklist

1. Register and get approved as an estate agent on Domovita
2. Go to Branch Management
3. Generate your API key
4. If your CRM exports to FTP: Enter FTP details, test connection, save
5. If your CRM pushes files: Give your IT team the API key and endpoint URLs shown on the page
6. If you want to test first: Upload a small sample file (5-10 properties) via the API
7. Check your feed log and live listings to verify everything imported correctly

Need Help?

• Self-service guides: Click "Getting Started" and "Full Reference" links on your Branch Management page
• Email: This email address is being protected from spambots. You need JavaScript enabled to view it. - include your branch name and any error messages
• Sample files: Send us a sample export from your CRM and we can advise on the best method