Migration guide

/v1 changes in place: the base URL stays https://api.registercheck.de/v1, and there is no /v2. When a name changes, the old one keeps working for a while, and every response to a request that used it says so in three headers:

Log every response that carries Deprecation, and you have your to-do list.

Deprecated now

These work unchanged until 31 December 2026. After that, the old form is refused.

The answers are the same: only the name you send changes.

q on /company-events, /events and /formations is not deprecated today: there it is a full-text term over several fields. That changes in the October 2026 release, below.

Coming in the October 2026 release

The next release moves /v1 to one model: one word for each thing the register holds, used the same way in every path, field and id. It is breaking. When it ships, this page lists every change field by field. The headlines:

• Ids say what they name. A company id becomes cmp_…, a person id per_…, and so on for every kind. The part after the prefix encodes the same UUID you have today, so stored ids can be converted without a call. A raw UUID is still accepted until 31 December 2026, with Deprecation and Sunset on the response.
• One page envelope. Every list and search answers {object: "page", data, next_cursor} and pages forward with cursor. starting_after, ending_before, page, has_more and next_page go.
• One reference shape. Every reference to a company or person is {object, id, name}.
• name on every search. GET /events and GET /formations take the search term as name. On /formations, q keeps working as a deprecated alias until 31 December 2026; /company-events keeps its q until it goes, on the same date.
• Renamed paths answer 410 endpoint_retired, and detail names the replacement:

After the release, only these old forms are still answered, and all of them stop on 31 December 2026: q on the three searches and on /formations, /company-events (with its q), and raw UUIDs.