Skip to main content
This page records changes to the API contract and to behaviour worth knowing about: new fields, renames, breaking changes. Each entry names the release it shipped in. The release is info.version in the OpenAPI spec — see Versioning.
Entries start at release 1.0.0, the first numbered release. Changes made during the earlier beta were not tracked.

​
Conventions

Entries are tagged so you can scan for the kind of change that affects you:
  • Breaking — you must change your integration. Always listed first.
  • Added — new endpoint, field, or capability. Safe to ignore if you don’t use it.
  • Changed — non-breaking change to existing behaviour.
  • Deprecated — still works but scheduled for removal. Start migrating.
  • Removed — no longer available.
  • Fixed — bug fix bringing actual behaviour in line with documented behaviour.

​
History

​
2026-09-04 — release 1.0.1

  • Fixed — deployment fix only. No change to the API contract.

​
2026-09-04 — release 1.0.0

First numbered release. The URL prefix stays /api/v1.
  • Breaking — request field postcode renamed to input_postcode.
  • Breaking — response field matched_postcode renamed to matched_registered_postcode. It holds the registered office postcode of the matched company.
Requests that still send postcode are not rejected. The API returns 200 and ignores the unknown field, so the postcode stops contributing to matching and you get no error. Rename the field.
Last modified on September 4, 2026