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

1. User enters proposed company name.
2. Backend calls POST /v1/conflicts/search.
3. UI displays already registered matching names grouped by risk level.
4. 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.
• 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.