§ Industries / Rex Real Estate CRM

Rex Real Estate CRM

Rex API Integration

Rex holds your listings, your agents and your enquiries. The website has to show all three, stay current when an agent changes a price from their phone, and not fall over on a Saturday morning. This is how we connect the two.

How the Rex API works

Rex publishes its developer documentation openly, including a guide written for agency website builds. The points below come from that documentation.

  • Access is a user, not a key. An integration signs in as a Rex user and receives a session token. The agency invites that user to its Rex account and chooses its privileges, so access stays in the agency's hands.
  • Tokens expire. By default a token lasts for an hour of activity, and a longer lifetime of up to a week can be requested at login. The sync has to sign in again and retry instead of assuming a permanent key.
  • It is not REST. Every call is a POST to a service and a method, written in Rex's documentation as PublishedListings::search or Contacts::read, with criteria and paging in the body. It makes no difference to what the agency sees, but it shapes the build.
  • There is an endpoint made for websites. Rex directs website builds to its published listings service, which only returns listings an agent has marked ready for marketing. We filter it to listings flagged for the agency website and ask for the website version of each record, so a hidden address or a price override set in Rex is respected on the site.
  • Rate limits. Rex documents a limit of 3,600 requests an hour per agency account, and says plainly that the API should never be called live when a visitor loads a page.

What the integration lets your website do

  • Listings for sale and for lease. Price, description, photos, floorplans, features and links, kept in step with Rex.
  • Sold and leased results. The same service returns sold and leased listings, so results pages and suburb pages with your recent sales are built from Rex data and nobody retypes them.
  • Open homes and auctions. Upcoming inspection and auction times arrive with each listing and can be shown on the listing page and on a combined open homes page.
  • Agent profiles. Each listing carries its listing agents. Staff come from the account's users, so a profile page can show an agent's current listings and recent sales.
  • Enquiries back into Rex. Rex's API includes leads and contacts services. A website enquiry is written into Rex against the right listing and agent, so it is not left sitting in an inbox.
  • Appraisal requests. An appraisal form on a suburb or agent page posts into Rex the same way, with the page it came from recorded.
  • Changes that show up quickly. Rex supports webhooks for create and update events on its common records. We use them to pick up a price or status change soon after it happens, alongside a scheduled full check, which is the pairing Rex itself recommends.

How we build it

  • Sync, do not proxy. We mirror listings into the site's own data layer and render pages from that copy, so the site stays fast and stays up when the CRM is slow. Rex's documentation recommends the same approach.
  • Status rules that match how agents work. Withdrawn, under offer, sold and off-market each need a rule for what shows publicly and how long a sold listing keeps its page. Getting this wrong is the most common reason an agent rings you on a weekend.
  • Search that never touches the CRM. Suburb, price band, bedrooms, land size and map bounds run against your own index, so filtering is instant and unmetered.
  • Images served from your site. Listing images come back as links. We copy them at sync time and serve resized, modern formats, so a slow origin cannot drag down your page speed.
  • Tokens kept on the server. Rex warns that an integration exposing its token in the browser will be disabled. Ours never leaves the back end.

What to arrange with Rex

Ask whoever administers your Rex account to invite an integration user and grant it only the privileges the website needs. Setting up webhooks needs its own privilege. Rex's documentation notes that an integration user can count towards the agency's user slots unless the integrator has been verified by Rex, so raise that with Rex before go-live. Test and live accounts share the same API address, which means the two have to be kept apart deliberately: a test account connected to a live site will happily publish dummy listings.

Two things that catch most teams

Deletions are easy to miss. If you only sync changed records, a listing withdrawn in Rex lingers on the website, so compare the full set of listing IDs on a regular pass. And listings an agent has published in Rex are not automatically meant for the website. The website flag has to be part of the query, or portal-only stock appears on the site.

For a typical agency site, the feed, search, agent profiles and enquiry sync take two to three weeks, assuming Rex access is ready on day one.

Start with the scoping form

Planning a new agency site on Rex, or fixing the sync on the one you have? The real estate scoping form asks which CRM you are on and what the site needs to do, and takes about two minutes. Work starts from $500.

Related reading

Other CRM integrations

Rex is one of the systems where we build against the API. Agentbox and VaultRE work the same way in outline, with different rules for who grants access. We also integrate Box+Dice, ListOnce and PropertyMe.

The projects below are agency websites we have built. They are examples of the work, not a list of Rex clients.

Tell us more about your project.

Tell us which CRM you're on and what the website needs to do with it. Work starts from $500. Planning a whole agency site? Use the real estate scoping form instead.

No obligation. No sales call. Reply from a senior developer within 1 business day.

Rather talk? Book a 30-minute call →

Rex website integration questions

Ready to start your project?

Talk to us directly. No commitment required.