Conflict Search Integration Guide¶
Use POST /v1/conflicts/search to identify already registered Swiss company names that are identical or similar to a proposed name.
This guide explains how to consume those results in partner applications and internal review workflows.
Suggested UX flow¶
- User enters proposed company name.
- Backend calls
POST /v1/conflicts/search. - UI displays
identityMatchseparately andsimilarMatchesin API order, with risk labels. - User chooses another name or continues with legal review.
Decision mapping example¶
CRITICAL: block and require a new name.HIGH: warn strongly and require user acknowledgment.MEDIUM/LOW: allow progress with advisory messaging.
Implementation tips¶
- Always display normalized input used by the API.
- Keep top N matches to reduce noise.
- Preserve API order when selecting the first N matches. Mixed names prioritize identifying words over descriptive-only matches, so the list can contain a lower-risk result before a higher-risk result. The risk label and
minRiskfilter remain separate from relevance ordering. - Make it clear in your UI that results are already registered company names, not generic similarity hints.
- Persist result snapshots for auditability in regulated workflows.