Dossier-API Integration

Overview

Release 3.3 connects the FTS Platform to dossier-api as the single source of truth for parcel intelligence, replacing multiple fragmented lookups with one unified pipeline.

What Changed

DossierBridgeService

New server-side HTTP client for dossier-api, configured via DOSSIER_API_URL env var
Centralises all communication between the platform and dossier-api

AddressInsightController

New endpoint at /api/address/insight coordinates dossier-api lookups server-side
Resolves address to SPI, then fires title-status verification and enrichment in parallel
Eliminates direct browser-to-dossier-api calls for address resolution

ProjectInsightEnrichmentService

Calls /api/insights (same endpoint the browser uses) ensuring data consistency between manual and automated updates
Single code path for both interactive and batch enrichment

Fields Populated

Parcel identifiers: SPI, Parcel PFI, Property PFI, EZI Address, Lot Number, Plan Number
Planning data: Zone, Overlay, LSIO, Land Size, Bushfire, LGA, Water Authority
Compliance flags: Part 5 Build Reg, SLHC
Title lifecycle: Title Status, Title Date, Predicted Title Date, SOC Date
SPEAR: SPEAR Ref, Estate Stage
Geolocation: Lat/Lng

Docker Compose

Added dossier, dossier-api, and v4-platform services to docker-compose.yml for local development

All parcel data now flows through a single, auditable pipeline. The platform no longer needs to coordinate multiple external API calls directly - dossier-api handles orchestration, caching, and data normalisation.