OMNIA Immobilier · Real Estate

Omnia.ch, multi-agency real estate platform connected to APIMO

Omnia.ch is a multi-agency real-estate platform connected to APIMO, engineered by PULSE.digital. The client supplied polished Figma mockups; our job was the production-ready platform behind them: exposing a catalog of thousands of properties, synchronizing data nightly from the business software, and turning visits into qualified requests through multi-agency routing and email automation. THE CONTEXT — The catalog lives in APIMO (Publimmo base): the truth about properties, statuses and media sits in the business software, not in a CMS. For a multi-agency group the website is not a brochure: it is the channel that turns a business catalog into inbound requests — a web catalog always aligned with Publimmo reality, zero lost leads, and fluid search across thousands of objects. THE TECHNICAL CHALLENGE — APIMO is not a CMS: object structures, statuses, media and heterogeneous fields that must be normalized and stabilized web-side. Every night the site rebuilds its state from APIMO — deltas, deletions, status changes, images, inconsistencies — while avoiding the "broken site" effect at the slightest API issue. THE ARCHITECTURE — APIMO → web-model mapping (properties, promotions, lots, media, statuses); nightly sync scripts with consistency checks; a resilience strategy (retries, logs, fallback). A search engine and filters built for a large catalog without degrading fluidity, action-oriented listing pages (file request, visit, contact), and multi-agency routing with per-agency email rules, anti-spam, submission validation and monitoring (sync OK/KO, volumes, errors). TECHNOLOGIES — Next.js (SSR front-end, SEO), Node.js (sync services), PostgreSQL (normalized web model), APIMO API, transactional SMTP email, cron jobs. WHAT THIS PROJECT TEACHES — A successful real-estate portal is first an integration and operations problem, not a mockup problem: the value lies in nightly synchronization, lead routing and resilience — exactly what a prototype never shows. FREQUENTLY ASKED QUESTIONS Why nightly synchronization instead of real time? The business rhythm of real estate allows it and robustness wins: controlled rebuilds, consistency checks, no daytime dependency on API availability. What happens if the APIMO API fails? The resilience strategy (retries, logs, fallback) prevents the "broken site" effect; monitoring reports OK/KO syncs and processed volumes. How do requests reach the right agency? Multi-agency routing with per-agency rules and email templates, anti-spam, submission validation and traceability. Was design part of the project? No: Omnia supplied polished Figma mockups; PULSE built the production engineering behind them.