Property Feed Integrations

Overview

The API ingests property data from multiple UK letting agent feed providers. Each provider has its own subdirectory under api/propertyFeed/ with provider-specific parsing logic.

Base directory: api/propertyFeed/

Feed Providers

Jupix

Directory: api/propertyFeed/jupix/

getProperties.php - Fetches and processes properties from the Jupix XML feed

Jupix is a UK lettings property management platform. Uses XML API with token-based authentication (Vebra Alto compatible).

BLM (Rightmove BLM Format)

Directory: api/propertyFeed/blm/

updateProperties.php - Processes BLM format property files

BLM (Blind Listing Method) is the standard Rightmove data interchange format for property listings.

Aspasia

Directory: api/propertyFeed/aspasia/

getProperties.php - Fetches properties from Aspasia feed

RTDF (Real Time Data Feed)

Directory: api/propertyFeed/rtdf/

getPropertyList.php - Lists available properties
sendProperty.php - Sends/syncs a property
removeProperty.php - Removes a property

RTDF supports real-time property updates with individual property create/update/delete operations.

Veco

Directory: api/propertyFeed/veco/

getProperties.php - Fetches properties from Veco feed

StuRents

Directory: api/propertyFeed/stuRents/

Student-specific rental feed provider. Directory exists but appears to be empty or minimal.

Shared Utilities

Directory: api/propertyFeed/utils/

propertyFeedUtils.php - Shared property feed processing utilities
entrata/ - Entrata-specific utilities (see Entrata integration)

Feed Entry Points

File	Purpose
`api/propertyFeed/propertyFeed.php`	Main feed processing script (Vebra/Jupix authentication flow)
`api/propertyFeed/getProperties.php`	Generic property fetch
`api/propertyFeed/updateProperties.php`	Property update processing
`api/propertyFeed/reconcileProperties.php`	Reconciles feed data with local database

Authentication

The main propertyFeed.php file implements Vebra XML API authentication:

Sends HTTP Basic Auth credentials to the feed URL
Receives a token in the response headers
Stores the token (with expiry tracking) in a text file
Uses the token for subsequent data requests

FTP Feeds

File: api/propertyFeed/ftp/ (directory) File: api/ftpAuth.php

Some property feeds are delivered via FTP. The ftpAuth.php endpoint handles FTP authentication.

External Property Endpoints

File	Purpose
`api/external/createOrUpdateProperty.php`	External API for creating/updating properties
`api/external/deleteProperty.php`	External API for deleting properties
`api/propertyOperatorHouses.php`	Property operator house listings

Property Feed Data Flow


Feed Provider (Jupix/BLM/Veco/etc.)
    |
    v
Feed Script (getProperties.php)
    |-- Authenticates with provider
    |-- Fetches/parses property data
    |-- Maps to internal schema
    |
    v
MySQL `houses` table
    |-- Inserts new properties
    |-- Updates existing properties
    |-- Marks removed properties
    |
    v
API endpoints serve data to app

Properties from feeds are stored in the houses table with appropriate agent_id linking and city assignment.