Daichodo

Changelog

Changes to the API, the published contract, the SDKs and the terms — the ones that affect you if you have integrated.

Site copy and internal changes are not here. Only what is observable from outside.

  1. Terms

    Terms clause 4 gains an attribution obligation (effective 2026-10-21)

    If you display register data to third parties — in your product, a document or a report — the National Tax Agency attribution must appear near it. Internal checking and reconciliation carries no new obligation. Posted as the 30 days’ notice clause 12 requires.

  2. SDK

    daichodo 0.1.3 (npm and PyPI)

    The clients now carry types for the errors the API actually returns. ErrorResponse on 401, 403, 404 and 429, and HTTPValidationError — which this API never returns — is gone.

  3. API

    The contract now declares the errors each endpoint returns

    Every path with a parameter declared FastAPI’s HTTPValidationError, a shape this API never returns, while 401, 403, 404 and 429 were declared on none — so a generated client had a type that could not fire and none for the four you actually meet. Each route now declares exactly the statuses it can return, as ErrorResponse. No behaviour changed.

  4. SDK Breaking

    daichodo-validate 0.2.0 (PyPI)

    A registration number whose check digit fails now returns valid=False. The API and the TypeScript package have behaved this way since 2026-09-05; the Python package had not caught up. Breaking if you relied on the permissive behaviour.

  5. API Breaking

    The check digit applies to every registration number

    POST /v1/validate returns valid: false for a registration number whose check digit fails. It previously excused these as sole traders. Measured across the whole register — 5,421,496 numbers — corporations, sole traders and unincorporated associations all satisfy the check digit, with zero exceptions, so the exemption admitted every typo and every fabrication instead. @daichodo/validate 0.2.0 shipped to npm the same day.