Changelog

Track externally visible changes here.

2026-06-19

Added

• Trademark similarity matches (POST /v1/trademarks/search and the trademarks block of POST /v1/name/screening) now expose the trademark lifecycle dates applicationDate, registrationDate, and expiryDate as ISO timestamps when known.
• Trademark similarity matches now expose markCategory (legal mark type, e.g. Individual mark, Collective mark, Certification mark) and markFeatureCategory (type of sign, e.g. Word, Combined, Figurative, Three dimensional) when known. Both source directly from the IGE register.

Changed

• Trademark search no longer drops relevant acronym/dominant-term candidates, so matches such as IFJ Institut → IFJ Startup Support are now surfaced.
• The semantic deceptive-purpose check is now grounded in the actual company name, reducing false-positive purpose warnings for abstract names (e.g. FuJu GmbH).

Notes

• All new response fields are additive and nullable; existing fields and their types are unchanged.

2026-05-08

Added

• Partner assessment-code documentation now includes ERR_SOLE_PROP_SURNAME_MISSING and WARN_SOLE_PROP_OWNER_SURNAME_AMBIGUOUS.

Changed

• Partner assessment guidance now clarifies ownerSurname handling for sole proprietorships, including official spelling, multi-part names, hyphenated names, and ambiguous additional family names.

2026-05-07

Added

• GET /v1/name/screening/catalog exposes the stable screening issue codes, driver codes, status enums, risk values, error codes, and English fallback descriptions for partner UI mapping.

Changed

• Partner documentation now clarifies that code fields and enum values are the stable integration contract.
• Partner documentation now treats message fields as English fallback/debug copy only; localized customer-facing text should be rendered by partner applications from their own code-to-copy mappings.

2026-04-28

Changed

• Partner guidance now represents POST /v1/name/screening as the bundled assessment, conflict, trademark, and optional domain orchestration endpoint.
• Jurata technical documentation refreshed to match the current top-level assessment response and screening request/response contract.

2026-03-06

Added

• Initial partner documentation portal scaffold with Material for MkDocs.
• Getting started, API reference, integration guides, operations pages, and generated OpenAPI page.

Changed

• Partner docs now position POST /v1/name/assessment as the primary integration endpoint.

Deprecated

• POST /v1/name/eligibility for new partner integrations.

Removed

• None.

2026-02-28

Added

• Dedicated OpenAPI/docs endpoint surface for partner-facing schema views (2e692f0).
• Additional restricted-term categories for gambling and health-related naming signals (82cb65f, fd4692e).

Changed

• Assessment logic and checks were expanded with more category coverage and policy mapping refinements (82cb65f, fd4692e, 0e4acd1).

2026-02-27

Added

• Split Swagger/OpenAPI surfaces for admin and non-admin consumers (965d8d4).

Changed

• Endpoint routing/layout updates in the API app to support partner/admin separation (f4132f4).

2026-02-26

Added

• First release of the v4 assessment API model and profile-based risk output (7ceb35e).
• New assessment-focused schemas and docs aligned with v4 behavior (7ceb35e).

2026-02-22

Added

• V3 semantic extraction pipeline for eligibility checks with richer category outputs (e03b623).

2026-02-21

Added

• V2 eligibility endpoint and schema (POST /v2/name/eligibility) for structured semantic evaluation (00adfbf).

2026-01-14

Changed

• Conflict-search output and normalization behavior improved, including name-core handling for better matching quality (5bc1606).

2026-01-09

Added

• End-to-end API test support and scenario coverage in CI, improving release confidence for partner-facing behavior (93566a3).