Building publications as a data stream in your systems

A portal is fine for research. For operations, the data belongs where your processes run: in the CRM, in lead handling, in the data warehouse. The Enterprise plan delivers it there.

Three integration routes, one data base

All three routes deliver the same data model — the choice is an architecture decision, not a data question:

REST API (pull) — query building applications at any time, filtered as in the interface. The pattern for batch synchronisation, reporting and the initial backfill.
Kafka stream (push) — every new application and every status change as a real-time event. The pattern for latency-critical lead routing and event-driven pipelines.
Cloud Connect (managed push) — we write the object data straight into your CRM: Salesforce, Microsoft Dynamics 365, HubSpot; SAP as an accompanied project. Field mapping per customer, upsert on stable keys (project ID, the owner's UID) instead of duplicates, no development on your side — on request.

The usual route: start with the pull API and add the stream once latency matters — or choose Cloud Connect if the data should land in your CRM without any development on your side. The data model stays the same — nothing gets rebuilt.

A data model built for joining

Every publication arrives structured and classified: project type, segment, number of apartments, owner, phases as a timeline. For joining with your own records, stable keys come along:

EGID — the federal building identifier, where it exists: the bridge to the RBD and your portfolio system
UID — the Swiss enterprise identification number of the owner (CHE-…), resolved via Zefix: the key for deduplication and company profiles in your CRM
FSO municipality number — unambiguous across mergers and spellings
Coordinates and address — for GIS, territory cuts and market areas

Operations and access

SSO via your identity provider — accounts and permissions stay in your organisation
Full coverage: every construction project in Switzerland, all segments
Excel export stays available for the business teams — API and stream complement the interface, they do not replace it

Automation, accompanied

We help you automate your internal projects and processes around building publications — from lead routing in the CRM to portfolio reconciliation. Where needed, our specialists support you with the data model, the connection and operations, accompany the whole integration process professionally, service-minded and personally — and remain available for your concerns after go-live, too.

How to get there

API and stream access are part of the Enterprise plan (price on request). The usual path: a short architecture call, a test account, then production. Write to contact@neubau-radar.ch or compare the plans: Plans & pricing.