Brixit publication

Use the Brixit portal to choose which properties appear on your own website. Your website loads the published inventory through a JSON feed from your Brixit installation. This connection publishes listing data; it does not import website inquiries into the CRM. Set up your website’s inquiry flow separately.

Enable publication

Open Integrations → Portals and turn on the Brixit portal.
Select Website feed. Copy the Listings JSON URL and Feed key (UUID).
Open the listing you want to share and enable its Brixit portal publication.
Open the copied feed URL and confirm the property is present.
Give the URL to your website developer to display the inventory and individual property pages.

Only listings published to the Brixit portal are included. A listing’s workflow status, such as draft or active, does not by itself determine feed inclusion. Review the listing’s publication switch when deciding what is visible.

The feed is designed for public websites. Anyone with its URL can read the exported data, including published property information, agent details and exported custom fields. Review that data before publishing. The feed key is separate from the connection key used by the automation API.

Feed endpoints

All endpoints use GET on your Brixit backend, with feed_key in the query string. They return JSON and do not require a Bearer authorization header.

Endpoint	Response
`/api/v1/app/brixit-portal/public/listings`	Paginated summaries of published properties
`/api/v1/app/brixit-portal/public/listings/{id}`	One published property, including its description, amenities and floor plans
`/api/v1/app/brixit-portal/public/developers`	Paginated developer IDs and names from the workspace, for building filters

Replace {id} with the property ID returned by the listings feed. The list response omits descriptions, amenities and floor plans; request the detail endpoint when a visitor opens a property.

Listing filters

Query key	Format and behavior
`feed_key`	Required UUID copied from Website feed
`page`	Page number, starting at 1
`per_page`	Listings per page; default 10, maximum 50
`listing_purpose`	`sell`, `rent`, or a comma-separated list; omit for both
`bedrooms`	One non-negative integer; omit for any number
`bathrooms`	One non-negative integer; omit for any number
`property_type`	One or more comma-separated property type names
`developer`	One or more comma-separated developer names, from the developers endpoint
`search`	Text matching the title or reference number; maximum 200 characters

For developers, page, per_page and search are supported. Its page size defaults to 50 and is capped at 100; search matches the developer’s name.

Test the feed

Use the copied URL in your browser, or replace the placeholders in this request:

curl --get 'https://YOUR-BACKEND/api/v1/app/brixit-portal/public/listings' \
  --data-urlencode 'feed_key=YOUR-FEED-UUID' \
  --data-urlencode 'listing_purpose=sell' \
  --data-urlencode 'per_page=10' \
  --data-urlencode 'page=1'

Confirm an HTTP 200 JSON response and find your published listing in data. Follow the response’s pagination when loading more properties.
Request /listings/{id} with the same feed_key and confirm the full property details.
Change an identifiable field in Brixit and fetch the property again. Confirm your website refreshes its cached copy too.
Unpublish the property from the Brixit portal. Confirm it disappears from the list and its detail request returns 404. Remove any cached copy on your website.

An empty published inventory returns a successful response with an empty data list. Missing or invalid feed access is rejected; invalid filters return 422. A detail request returns 404 when the property is missing or is not published to this portal. If a property is absent, check the integration switch, the listing’s Brixit publication switch and your filters before changing the website.