Rightmove BLM V3 feed setup

Overview

We ingest the Rightmove V3 BLM format — the file most UK letting CRMs already publish. If your agency is live on Rightmove or Zoopla, you almost certainly already have a compatible feed. This guide takes you from "I have an agent account" to "my properties sync automatically" in about fifteen minutes.

What we need from you

1. A publicly accessible feed URL — the HTTPS address of your BLM XML file. Your CRM's support team can tell you where it's published.
2. Optional basic auth credentials — if your feed is password-protected, provide the username and password on the feed config screen. We store them encrypted.
3. An IP whitelist entry — if your CRM restricts feed access by IP, add our static polling address (shown on the feed config screen).

File hosting options

You have three realistic options for hosting the BLM file:

• Your CRM provides a URL. By far the easiest. Reapit, Alto, Vebra, Jupix, Street, Reapit CloudFlow, and most other lettings CRMs will either expose a feed URL or export one. Ask your account manager for the "Rightmove V3 BLM feed URL."
• A self-hosted static file. Some smaller agents generate the XML nightly and upload it to their own website (e.g. https://youragency.co.uk/feeds/blm-v3.xml). That's fine — the file just needs to be reachable.
• A feed-as-a-service provider. Third-party tools like Homeflow or Iamproperty can normalise stock from multiple sources into a single feed. We accept these.

URL configuration

In your dashboard, go to Feeds → Add feed and set:

• Format: Rightmove V3 BLM
• Feed URL: the HTTPS endpoint serving your XML
• Auth: none, basic auth, or custom header — depending on how your feed is protected
• Branch filter (optional): if your feed contains stock from multiple offices, choose which branches apply to the Borders

When you save, we fetch the feed immediately, validate it, and show the number of properties detected. Any parse errors appear inline so you can fix the source before the next poll.

Polling cadence

• Hourly automatic polling.
• Manual re-sync available from the feed detail screen — useful when you've just listed something and don't want to wait.
• Exponential back-off if your feed returns errors, to avoid hammering a broken endpoint. After three consecutive failures we email you.

What gets synced

Per property, from the BLM:

• Property type, bedrooms, bathrooms, furnished status
• Summary description and full description
• Full address and postcode (we use the postcode to auto-match to a Borders neighbourhood)
• Asking rent and deposit amount
• Available-from date
• EPC rating (if present)
• Key features list
• Up to 20 images per property, resized and optimised
• Status (available / let agreed / let / withdrawn) — we update the listing state automatically

What gets filtered out

• Non-rental properties — if your BLM contains sales stock, we drop it.
• Non-Borders properties — anything outside Scottish Borders postcodes (TD, EH44, EH45, EH46) is filtered at ingest.
• Inactive entries — withdrawn properties are removed from the live search on the next sync after their status changes.

Troubleshooting

• Feed returns a 401: your feed requires authentication. Re-enter basic auth credentials in the feed config.
• Feed returns a 403: likely an IP restriction. Add our polling IP to your CRM's whitelist.
• Properties missing: check the feed-log screen — we report every property we saw and explain any that were rejected.
• Images not appearing: image URLs inside the BLM must be publicly accessible without auth.

Need a hand?

Email the address on the contact page with your feed URL and we'll walk through it with you. Most agents are live within an afternoon of getting in touch.

Register an agent account