JamesEdition
Brixit provides an XML feed of listings you publish to JamesEdition. JamesEdition reads that feed to import your inventory. Inbound leads use a separate connection: Brixit periodically pulls them using your JamesEdition Leads API token.
Connect the listing feed
- Open Integrations → Portals and turn on JamesEdition.
- Select Manage JamesEdition and copy the Feed URL under Listings XML feed.
- Give that URL to JamesEdition for your agency’s feed setup. Confirm the account and office receiving the listings before publishing.
- Open a listing in Brixit, use its portal publication controls and select JamesEdition.
- Complete the listing and portal fields below, then publish. Check the feed and the listing in your JamesEdition account after the provider has processed it.
The feed URL has this format; copy the actual URL from your workspace:
https://YOUR-BACKEND/api/v1/app/jamesedition-portal/public/feed.xml?feed_key=YOUR-FEED-KEY
Brixit generates the offices, agents and listings in the XML. Your website developer can refer to JamesEdition’s Multi Office feed specification when checking the exported structure.
Prepare a listing
Brixit checks the following before including a listing:
| Detail | Requirement |
|---|---|
| Photos | At least two image URLs |
| Country | A country code available from the company profile |
| City | A city that can be resolved from the listing’s address |
| Property type | A populated listing type |
| Agent | An assigned agent |
| Sale price | A positive price unless Price on request is selected; residential sales also need to meet the installation’s configured minimum and currency conversion rules |
| Rental price per day | A positive daily price unless Price on request is selected |
The JamesEdition publication form also offers Price on request, Hide address, Pre-owned and amenities. Rental price per day appears for rentals; Trakheesi permit number appears for UAE companies. Review the validation message on the listing when publication is rejected.
Receive leads
- Open Manage JamesEdition from the portal card.
- Enter the Leads API token supplied for your JamesEdition account.
- Select a Fallback assignee for inquiries that need fallback routing, then save.
- Check Last leads sync on the card after the next polling run.
- Arrange a test inquiry through JamesEdition. Find the resulting contact and inquiry in Brixit and check the linked listing and assigned user.
Publishing and receiving leads are separate checks. A working XML feed does not verify the Leads API token. This connection pulls leads; there is no inbound JamesEdition webhook URL to register in this flow.
Update, remove and verify
Edit the property in Brixit and review its publication status. A change that fails validation can prevent the property from appearing in the refreshed feed. Allow for feed processing before expecting the change on JamesEdition.
To remove an individual property, unpublish it from JamesEdition using the listing’s portal controls. Verify that it leaves the feed and then the provider’s inventory. Turning off the whole JamesEdition integration returns an empty valid feed; it does not synchronously remove pages from the provider’s website.
| Problem | Check |
|---|---|
| Feed returns 401 | Copy the complete Feed URL from Manage JamesEdition. |
| Feed is empty | Confirm the integration is on and at least one valid listing is published to JamesEdition. |
| One listing is missing | Check photos, address, agent, type, pricing and the publication validation message. |
| Changes are delayed | Confirm that the feed refreshed and ask JamesEdition when it last fetched the URL. |
| No inbound leads | Check the saved Leads API token, integration status and Last leads sync. Ask your administrator to check scheduled lead processing if sync never runs. |