If you run an estate or letting agency on Street, your CRM already holds the most up-to-date version of every property: the price, the status, the photographs, the floor plan and the description. The question is how that information reaches your website, and how enquiries from your website get back into Street.

In this guide we explain how a Street CRM website integration works, what it should handle, and what to check before you start. It is based on our work integrating Brighton & Beck Property’s website with Street, so their team manages property information in one place instead of updating it twice.

Why integrate your website with Street?

Without an integration, someone has to copy each new instruction onto the website by hand, then remember to update it when the price drops, an offer is accepted or the property is withdrawn. That takes time, and mistakes are easy to make. A buyer who calls about a home that sold last week is not a good start.

An integration means your team updates Street and the website follows. It also works the other way: a valuation request or viewing enquiry from the website can arrive in Street as a record your team can act on, rather than as an email someone has to re-type.

What Street’s API makes possible

Street has an Open API that is available to every Street customer at no extra cost. It follows standard REST conventions and exchanges data as JSON. It covers core records such as properties, applicants, viewings, valuations, offers, branches and contacts. It also supports webhooks, which tell another system straight away when something changes, and there is a sandbox for testing before anything goes live. Access is controlled with API tokens created by your company admin. You can read more on Street’s Open API page.

Portal listings are a separate matter. Street has its own integrations with the property portals, so an integration with your own website does not need to replace those.

What a good integration should handle

Listings that stay in step. New instructions, price changes and status changes such as “under offer” or “sold” should reach the website quickly, ideally triggered by webhooks rather than a nightly import. Withdrawn properties should disappear from the website, not linger in search results.

Photos and floor plans. Images should be resized and compressed for the web, so property pages load quickly on a phone, without anyone editing files by hand.

Enquiries back into the CRM. Valuation requests, viewing requests and general enquiries should create or update the right record in Street, with the property attached, so nothing is lost between the website and the office.

Search that matches how people buy. Buyers expect to filter by location, price, property type and number of bedrooms. If you run auctions or lettings too, each should have its own clear route through the site.

Consent and data protection. Forms should record what people have agreed to, and the integration should only pass the data your team needs. This matters under UK GDPR.

Graceful failure. If Street is briefly unavailable, the website should keep showing the last known listings and queue any enquiries until the connection is back.

Questions to ask before you start

  • Which records should flow to the website, and which should stay private in the CRM?
  • How quickly do changes need to appear on the website?
  • What should happen to a property page when a home sells: remove it, or keep it as a “sold” example?
  • Who in your team will own the Street API token and admin settings?
  • Do you need to connect other tools too, such as your accounts package or a lead-nurture service?

How we approach it

We start by mapping how your team uses Street day to day, then agree what the website needs and what can stay in the CRM. We build against Street’s sandbox, test with real examples of your listings, and only then switch the live website over. After launch, we can look after the integration as Street and your website change.

If you are weighing up AI tools as well, read why the AI tool stack often fails small estate agencies. The same principle applies: your CRM should stay the single source of truth.

Next steps

See how we build property and auction platforms and API and systems integrations, or send us a short brief and you’ll hear back from Khaled within two working days.

For help connecting Street to your website, see our API and systems integration service and property and auction platforms.