TPX is designed to connect existing property systems to the TPX MLS & Syndication Server without requiring every participating organization to replace the technology it already uses.
Property inventory can enter the TPX network through different integration methods, including the TPX Houzez Connector, direct REST API connections and structured property feeds.
The purpose of each integration is the same: reliably connect an external property source to the canonical TPX property model while preserving ownership, identity and network availability.
Connects WordPress websites running Houzez directly to the TPX platform while allowing agencies to continue managing properties within their existing Houzez workflow.
Provides authenticated integration for custom websites, applications, property systems and third-party software that need to synchronize property data with TPX.
Designed for organizations that already publish or receive structured property feeds and need those records mapped into the TPX canonical property model.
Planned event notifications will allow connected systems to respond to property updates, withdrawals and syndication events without relying only on scheduled synchronization.
TPX acts as the central property exchange layer between originating systems and participating network websites.
SOURCE PROPERTY SYSTEM
↓
INTEGRATION LAYER
↓
TPX API
↓
CANONICAL TPX PROPERTY
↓
SYNDICATION ENGINE
↓
PARTICIPATING WEBSITES
The integration layer may be the TPX Houzez Connector, a direct REST API integration, an XML feed processor or another approved connector.
The TPX Houzez Connector is designed to provide the most direct workflow for agencies already using WordPress and the Houzez real estate theme.
Agencies continue managing their own properties in Houzez. The connector provides the bridge between the local WordPress property and the central TPX platform.
HOUZEZ PROPERTY
↓
TPX HOUZEZ CONNECTOR
↓
TPX MLS & SYNDICATION SERVER
↓
PRIVATE PROPERTY NETWORK
An originating agency can choose which properties are made available to the TPX network.
Properties that are not selected for network syndication remain local to that agency's own website.
When a Houzez property originates from the local agency, the TPX Connector treats that WordPress property as an owner-originated source record.
The connector should maintain the TPX identity of the property after its first successful synchronization.
LOCAL HOUZEZ PROPERTY
↓
TPX PROPERTY ID #4831
↓
CANONICAL TPX PROPERTY
Future edits to the same Houzez property should synchronize with the existing TPX property rather than create a new canonical record.
A property imported from the TPX network into another participating Houzez website is different from an owner-originated property.
The receiving website holds a local Houzez copy for search, maps, SEO and normal website functionality, but that property remains associated with the original TPX property and its syndication record.
TPX PROPERTY #4831
↓
SYNDICATION RECORD
↓
RECEIVING HOUZEZ WEBSITE
↓
LOCAL MANAGED COPY
This distinction prevents synchronization loops and duplicate canonical records.
The TPX Houzez Connector maps property data between the TPX property model and the Houzez property structure.
Typical mappings include:
| TPX Data | Houzez Data |
|---|---|
| Property title | WordPress property title |
| Description | WordPress property content |
| Sale price | Houzez property price |
| Bedrooms | Houzez bedroom field |
| Bathrooms | Houzez bathroom field |
| Property type | Houzez property type taxonomy |
| Features | Houzez property feature taxonomy |
| Latitude | houzez_geolocation_lat |
| Longitude | houzez_geolocation_long |
| Property images | WordPress Media Library / Houzez gallery |
The final mapping layer may vary depending on the Houzez configuration and the fields enabled by the participating website.
Organizations that do not use Houzez can connect directly to TPX through the authenticated REST API.
A custom application can submit property information using the property synchronization endpoint.
POST /api/v1/properties/sync
The request must include valid TPX API credentials:
X-TPX-Client-ID: YOUR_CLIENT_ID X-TPX-Secret: YOUR_CLIENT_SECRET Accept: application/json Content-Type: application/json
Each API client is associated with an authorized organization within the TPX network.
The REST API allows TPX to integrate with systems beyond WordPress.
Examples may include:
The external system remains responsible for maintaining a stable property identifier and processing API responses correctly.
XML integration provides another route for introducing structured property inventory to TPX.
An XML feed integration typically requires a mapping layer that converts the source feed structure into the canonical TPX property model.
EXTERNAL XML FEED
↓
FIELD MAPPING
↓
TPX PROPERTY STRUCTURE
↓
CANONICAL TPX RECORD
The mapping process should preserve the original external property identifier so that future imports can update the same canonical property.
A source XML feed might contain property information in a structure similar to:
<property>
<id>HH-1001</id>
<title>Modern Sea View Villa</title>
<price>6250000</price>
<bedrooms>4</bedrooms>
<bathrooms>3</bathrooms>
</property>
The field names used by an external XML feed do not need to match the TPX property model exactly.
The integration layer is responsible for mapping those source fields into the appropriate TPX fields.
TPX tracks where an external property originated.
This allows the platform to associate a canonical property with the correct agency, integration type and external property identifier.
AGENCY + SOURCE TYPE + EXTERNAL PROPERTY ID ↓ TPX PROPERTY
Source types can represent different integration methods such as Houzez, API, XML or other property feeds.
Every external integration should preserve stable identifiers.
For example:
SOURCE TYPE houzez EXTERNAL ID 1001 TPX PROPERTY 4831
If the same external property is synchronized again, TPX should update Property #4831 rather than create another canonical property.
Integrations can also associate property media with TPX property records.
Media may include:
For website syndication, receiving systems should generally import the required property media into their own local media environment rather than permanently relying on remote hotlinked images.
Integration with TPX does not automatically make every property available for syndication.
The originating system controls whether the property is made available to the private network.
{
"exchange_available": true
}
When set to false, the property is withdrawn from network availability.
{
"exchange_available": false
}
Different integrations may use different synchronization strategies.
A connector can submit changes immediately after an originating property is updated, while scheduled synchronization can provide an additional reliability layer.
PROPERTY UPDATED
↓
SEND CHANGE TO TPX
↓
PROCESS RESPONSE
↓
MARK AS SYNCHRONIZED
↓
SCHEDULED CHECK AS SAFETY NET
Reliable integrations should also account for temporary network failures and retry unsuccessful synchronization attempts.
A connected website should be able to distinguish between successfully synchronized properties and properties that still require attention.
Typical connector states may include:
These states allow administrators to identify failures without losing track of the originating property.
TPX is designed to support event-driven synchronization in addition to direct API requests and scheduled synchronization.
Potential events may include:
property.created property.updated property.withdrawn property.sold syndication.revoked
A property network can create duplicate records if a receiving website sends a syndicated property back to TPX as though it were its own property.
Integrations must therefore distinguish between:
OWNER PROPERTY Originates from the local agency Can synchronize to TPX SYNDICATED PROPERTY Originates from another TPX member Must not create a new TPX property
This rule allows TPX to maintain one canonical record while still creating genuine local property records on receiving websites.
Every API integration should protect its TPX credentials.
TPX API access is associated with authorized organizations rather than unrestricted public access.
When building a new TPX integration, we recommend implementing the connection in stages.
OBTAIN API CREDENTIALS
↓
TEST AUTHENTICATION
↓
MAP PROPERTY FIELDS
↓
SYNC ONE TEST PROPERTY
↓
STORE TPX PROPERTY ID
↓
TEST PROPERTY UPDATE
↓
TEST NETWORK AVAILABILITY
↓
VERIFY SYNDICATED COPY
↓
ADD RETRY / ERROR HANDLING
↓
MOVE TO PRODUCTION
Testing the complete lifecycle with a small number of properties is preferable to introducing a large inventory before synchronization behavior has been verified.
| Integration | Best For |
|---|---|
| TPX Houzez Connector | Agencies already operating property websites with WordPress and Houzez. |
| REST API | Custom websites, applications and property management platforms. |
| XML Feed | Organizations already producing structured property feeds. |
| Custom Integration | Proprietary systems and specialized network workflows. |
Real estate technology for Houzez. We build private MLS and property syndication infrastructure, synchronization technology, AI tools and purpose-built plugins for agencies and property networks.
TPX product updates, new features and private MLS insights delivered to your inbox.
Hua Hin, Prachuap Khiri Khan, 77110, Thailand
Copyright © 2026 TPX – Real Estate Technology for Houzez. All rights reserved.