registercheckby openlaw group

Changelog

What changed in /v1, newest first. Breaking changes link to the migration guide.

/v1 changes in place. A breaking change is marked breaking, and the migration guide has every one of them, old next to new. An old name that keeps working for a while says so on every response with Deprecation and Sunset headers.

19 November 2026

  • GET /events/{event_id} finds older events. An event a company's history lists (GET /events?subject_id=) is found by its id whatever its age; before, an event older than about six months answered 404. The price is unchanged.
  • A lookup that finds no company or several is refunded. A job started with subject_lookup that ends company_not_found or company_ambiguous now gives back its 25 credits: credits.refunded shows 25. The candidates are unchanged.
  • A lookup job carries its outcome in lookup. Breaking for lookups. Every job has lookup: null for a job started with a company id, else {outcome, candidates, candidates_has_more} where outcome is pending, matched, not_found or ambiguous. Several matching companies are no longer in result.candidates: they are lookup.candidates (at most 10, with candidates_has_more), and result is null unless the job succeeded. A candidate is a company: {object, id, name, register, city, status, subject_lookup}. id is our company id when we hold the company, else null; register has the court (code, name), type, number, formatted and country; subject_lookup is the criteria to send to POST /jobs for that company: the court, register type and number when the court is in our court directory (that names exactly one company), otherwise the name, register type and, when known, the city, which can match more than one company again. The failure codes stay company_ambiguous and company_not_found. Every job also carries subject_lookup (null for a company-id job). The migration guide has old next to new.
  • The value lists of a job can grow. status_details.running.stage, status_details.failed.code, status_details.canceled.reason, and a missing document's reason and code are strings with documented known values, not closed enums. Treat a value you do not know like the fallback each field names. Job status and the register types stay closed.
  • Prefer: wait=N on POST /jobs. Send Prefer: wait=N (1 to 55 seconds) and the call waits for the job. A job that reaches a final status in time answers 201 Created with Location and Preference-Applied: wait=N; otherwise 202 Accepted as before, with Location and Retry-After. Without Prefer nothing changes.
  • MCP: start_register_job takes an idempotency_key. An optional key (1 to 255 characters) sent as Idempotency-Key, so a retried call returns the same job instead of charging twice. get_register_job returns lookup with the candidates and their subject_lookup to pass to the next start_register_job.

18 November 2026

  • A job for a company we do not hold yet. POST /jobs takes subject_lookup instead of subject_id: the company's name (required) and, optionally, register_court, register_type, register_number (needs register_court) and city. The job searches the register by name. When it finds one company, the company is stored and its documents are fetched as for a subject_id job; the job's subject then carries the new cmp_ id. Otherwise it fails with company_not_found or company_ambiguous (result.candidates lists up to 10 matches, with a subject_id where we already hold the company). A lookup costs 25 credits; the charge stays when it ends company_not_found or company_ambiguous, and other failures are refunded. A lookup job cannot be canceled while queued.
  • MCP: register jobs. The MCP server has two new tools: start_register_job (a company id, or a lookup by name; the same price as POST /jobs) and get_register_job (free). They need the new scopes jobs:write and jobs:read; an existing connection asks you to reconnect once to grant them. See MCP.
  • Transparenzregister extracts, connections and files. You can order the Transparenzregister's own extract of a legal person with your own register account. POST /connections stores a live login (the register's e-mail and password, never returned) or a test connection; POST /transparency-register/extracts orders an extract by ekrn or company (Prefer: wait=55 waits up to 55 seconds, else 202 with Location and Retry-After); the statuses are queued, pending, succeeded, failed and canceled. Files are read by their file_ id at GET /files/{file_id}/content. An open extract is canceled (refunded) or a final one redacted with POST .../cancel and POST .../redact; the data and files are deleted 30 days after the extract ended. The webhook events transparency_register.extract.succeeded, .failed and .canceled carry no personal data. An extract costs 25 credits, charged only when it succeeds, a test extract too. The register bills its own 1,65 EUR per retrieved document to your own Transparenzregister account (live connections only). Five new problem codes start with transparency_register_. The guide has the steps.

17 November 2026

  • A job that brought none of the documents it was asked for is refunded. A refresh_documents job whose register failed to hand out every requested document type still succeeds (the company record was refreshed), and its 25 credits are refunded in full: credits.refunded shows 25.
  • A document the register did not hand out because of a technical problem is register_not_answering. When the register reports a technical problem and did not hand out a document, result.missing_documents names that document register_not_answering; ask again later; the job's other documents are served.
  • A company carries its consolidated head count. GET /companies/{company_id} has consolidated_employee_estimate, the same shape as employee_estimate: how many people the company and its subsidiaries employ, estimated by Registercheck from the consolidated accounts. change.vacancies is null. It is null when there is no consolidated head count. The company in a KYB report, a verification, an answer or a job's result carries the key as null. The price is unchanged. If you validate responses against a saved copy of the contract, update it, because company allows no other properties. An estimate's change may now span one or two fiscal years (to_year - from_year is 1 or 2).
  • A company carries an employee estimate. GET /companies/{company_id} has employee_estimate: how many people the company employs, estimated by Registercheck, as a range (min, median, max), a confidence, when it was computed (as_of) and, where known, how the count changed between two years (change). It is not register data and not an official figure. It is null when there is no estimate; estimates cover active GmbH, UG, AG, SE and KGaA and their "& Co." partnerships. The company in a KYB report, a verification, an answer or a job's result carries the key as null. The price is unchanged. If you validate responses against a saved copy of the contract, update it, because company allows no other properties.
  • A holder filed under a foreign register carries that register's country. On a shareholder's or a holder's holder_as_filed.register, a register that is not one of the six German register types now has type: null and the register's own country (an Austrian Firmenbuch FN is AT). Before, the raw prefix was sent as the type, with country DE, which a strict client rejects. The register's German spellings map to their type: HR B is HRB, HR A is HRA, GenR is GnR. formatted keeps the register as filed.
  • The candidates of a 409 register_identity_ambiguous now carry each company's published id (cmp_…) (breaking for a client that validates candidates[].id as a UUID), as every other answer does; the raw UUID they carried before is the form deprecated since October 2026 and refused after 2026-12-31. The migration guide has the change.
  • The 409 register_identity_ambiguous detail now names subject_id.
  • A financial statement says whether its positions were withheld. positions was null both when a filing had not been read and when its reading failed the accounting check. GET /companies/{company_id}/financial-statements now carries positions_status: read (the lines are served), not_read (no reading is served), or withheld. positions_withheld_reason is failed_accounting_self_check when the status is withheld, and null otherwise. positions is unchanged: the lines when read, null for not_read and withheld. positions_status is null when it could not be checked on this request; ask again. The price is unchanged. If you validate responses against a saved copy of the contract, update it, because a statement allows no other properties.
  • A purpose the register does not state is null. Where the register states no business purpose (most e.K., and many KG, OHG and GmbH & Co. KG), purpose carried the register's placeholder, "---". It is now null on a company (GET /companies/{company_id}, the KYB report, POST /companies/verify and /answers), on a formation, and in the data of a company.purpose.changed event (its source.text keeps the register's wording as written). A purpose the register states is published verbatim, as before.
  • A job that keeps waiting on an unavailable register now ends after 15 minutes. A refresh job that is still retrying 15 minutes after it was created fails with register_unavailable and its credits are refunded, so it no longer holds an open-job slot for up to an hour while a register keeps refusing. Ask again later; the fetch itself keeps trying in the background.
  • The rate-limit headers are in the OpenAPI document. Every successful response declares X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, which were sent but not declared, so a generated client can read them. X-RateLimit-Reset is an ISO 8601 timestamp. Nothing about the limits changed.
  • A succeeded job names the documents it was asked for and does not hold. result.missing_documents lists each asked type that result.documents does not, in the order it was asked. not_in_register means the register's file holds none of that type (a GmbH without a filed Satzung, a closed sheet's current extract). not_retrieved means the register lists one, or we could not tell, and this job did not get it; ask again later. code is the failure recorded for that document, or null when nothing was recorded. A document the register still holds unchanged stays in documents, with the date it was first retrieved.
  • The KYB report and a company's history carry the courts' insolvency publications. The KYB report has an insolvency section: the publications of insolvenzbekanntmachungen.de (§ 9 InsO) matched to the company by register court, type and number and by name, each with its kind, stage, published_on, court, file_number and kept_until, shown until its last day under InsBekV § 3. A company's events include one company.insolvency.recorded per publication, with source insolvency_publication. They are not on the market-wide feed or on monitors. The KYB report's price is unchanged.
  • A financial statement lists the lines it prints. positions on a financial statement is every balance-sheet and income-statement line of the published filing, in the order and outline it was printed, with figures in full currency units. It is null until that filing has been read (financial statements).
  • A company's shareholders say when the register lists a newer list. When the register lists a shareholder list newer than the one served, extract.newer_filing on a company's shareholders and in the KYB report's shareholders section names that list's date and whether its refresh is queued or waiting. The key is absent when the list served is the register's newest. The refresh costs nothing extra.
  • A person shareholder carries the birth date the filing states. On a company's shareholders, the ownership tree and the KYB report, holder_as_filed.birth_date of a person is now the date of birth the shareholder list states; it was always null before. On a person's holdings it stays null.
  • The company filter refuses a negative capital. company.capital.gte and company.capital.lte on POST /search/companies/filter take 0 or more (share capital in euros). A negative bound answers 400 validation_failed naming the field, uncharged.

16 November 2026

  • A shareholder event names the two lists it compared. company.shareholder.added, company.shareholder.removed and company.shareholding.changed carry current_list_date and previous_list_date: the register date of the newly filed list, and the register date of the stored list it was compared with. Either is null when that date is unknown. Both are null for events stored before this field was released (2026-11-16). effective_date is still the day the list was read.

14 November 2026

  • registration_date for more companies whose sheet came from another court. When a carried-over sheet states no "Tag der ersten Eintragung" but names the register it came from, registration_date is now that register's first entry, followed up to three registers back. No existing value changes; about 15% of the companies that answered null now have a day.
  • founding_date no longer carries a Beginn written with the month, either. About 800 more companies had a "Beginn" written as "1. Juli 2001", or an earlier entry's Beginn, as their founding_date. It is now null, and the day is in commencement_date, which now also reads a Beginn written with the month name.
  • founding_date no longer carries a partnership's Beginn. About 45,000 companies, almost all OHG and KG, had the day the register states as their "Beginn" in founding_date. It is now null for them, and the same day is in commencement_date. A founding date that any register entry states as the articles (Gesellschaftsvertrag, Satzung) stays as it was, and so does every founding date that differs from the Beginn.
  • A company's first register entry, and the Beginn the register states. registration_date is now the "Tag der ersten Eintragung" the register states for a sheet carried over from an earlier register (the paper register, or another court after a move), for example 1977 rather than the 2005 day the sheet was rewritten. A carried-over sheet that does not state that day now answers null instead of the transfer day. The new commencement_date is the start of business the register states ("Beginn", mostly for OHG and KG), null where it states none. Neither is a founding date: founding_date stays the founding contract. Both are on GET /companies/{company_id}, the KYB report, POST /companies/verify and /answers, at no extra cost.

13 November 2026

  • A current representative without own words takes sole or joint from the register entry that states them. A holder whose own words are not on the current printout but in a later register entry publishes type from that entry with basis: entry, text: null and no § 181 release (the register history holds those words as read, not as printed).

  • Start dates now also come from the register history's numbered entry that opened a current mandate. A current role whose own numbered entries give no appointment takes that day as appointed_date. A former role does not, and a role whose own numbered entries say the appointment ended still publishes none.

  • A representative's start date comes only from a numbered register entry. A managing director's or board member's appointed_date is the day of the register's numbered entry that appointed them, as for a Prokura. A holder known only from the current printout, whose listing carries no entry number, now has appointed_date: null -- the printout's own day was the day of its last entry, not of the appointment. Roles are ordered by the published date, undated last.

  • The KYB report carries a sanctions screening. GET /v1/companies/{company_id}/kyb-report has a new sanctions section: an automated name match of the company and of the people in its current roles and shareholder list against the official EU, UN, OFAC and UK sanctions lists, with the list versions screened and each hit's list, entry, result (match or possible) and reasons. A match needs a second identifier, such as the same register number or the same full birth date. The report still costs 50 credits.

  • Registered associations (e.V.) now carry their signing authority. A board member's signing_authority is published on every surface that already carried it for other forms. Until now every role at an association published null. At a registered association sole is published only where the register's own words say so in a standard wording -- a rule that makes every board member sign alone, or the holder's own standard words; any other sole reading publishes type: null with its basis and text. At a registered association together_with is null: who signs with a joint holder is not read there yet.

12 November 2026

  • Joint signing authority names its co-signers. signing_authority.together_with lists who signs together with a joint holder: each entry is an office (type) and how many of its holders (count, or all), any one entry being enough -- for example a Gesamtprokura "gemeinsam mit einem Geschäftsführer oder einem anderen Prokuristen" reads [{"type": "managing_director", "count": 1}, {"type": "authorized_signatory", "count": 1}]. It is null when the holder is not joint or the register names no office.
  • More Prokura roles carry their signing authority. A Prokurist the register's sources store twice -- once from the current printout without its wording, once from the change history with it -- now reads signing_authority from the register's wording instead of publishing null. Where the stored rows disagree on the wording and the register's entries cannot tell which is newer, or the row with the wording has ended or records a later change, it stays null, and a grant the register ended no longer lends a current Prokura its dates.
  • A company's first register entry and its former names. A company's registration_date is now the day of its first register entry (it was always null), and the new previous_names lists the names it no longer bears, oldest first, each with until, the day that name ended: on GET /companies/{company_id}, the KYB report, POST /companies/verify, /answers and a refresh result (GET /jobs/{id}). [] means none; null means they could not be read on this read.
  • A shareholder as the filing names it. Each shareholding on a company's shareholders, the ownership tree and the KYB report carries holder_as_filed: a company with its seat, country and register (a foreign register too, such as Delaware's, with its number), or a person with the name and place the filing states. holder stays the bare link. On a person's or a company's own holdings, holder_as_filed names the holder only.
  • The KYB report's documents say when we retrieved them. Each document reference carries retrieved_at, as /documents says it, and the report lists the newest articles of association (articles_of_association).
  • A company's history lists what the register changed. GET /companies/{company_id}/events no longer lists an entry whose stored value is empty, a legal-relationship or note entry without text, or an undated shareholder-list change, and lists each appointment once per person and role. The legal form is the one the register states; a UG that becomes a GmbH by a new name is a name change, and the old name is in previous_names.
  • A residence with a slash stays whole. A place of residence such as "Wünschendorf/Elster" or "Frankfurt/Main" is no longer cut at the slash on roles and person records; only a foreign residence written as "town / country" is split into town and country. Stored residences were corrected.
  • A role's name needs at least 3 letters or digits. On a role condition, name, first_name and last_name with contains need at least 3 letters or digits. an, a b, --- and a value of only spaces answer 400 validation_failed naming the field, before anything is charged. A company name and a shareholder name still take 2. equals and starts_with on a role name stay refused.
  • Prokura roles carry their dates. An authorized_signatory role's appointed_date is the date of the register entry that granted the Prokura, and an ended Prokura's ended_date the entry that ended it -- null where no numbered register entry dates that grant. The order of a company's roles is unchanged: representatives first, then the Prokuristen.

11 November 2026

  • A refresh job also checks for a newer shareholder list. For a GmbH or UG, a refresh_documents job that asks the register now also checks it for a newer shareholder list (Gesellschafterliste) and reads one, at no extra cost: the job's documents then include it, and /companies/{id}/shareholders serves it.
  • A Prokura's § 181 release is true only in full. signing_authority.self_dealing_exempt on a Prokura role was also true when the register lifted only one of the two prohibitions of § 181 BGB, most often with "mit sich als Vertreter eines Dritten" (acting for a third party at the same time). Such a partial release now publishes null with the register's words in text, as it already did for every other role (companies).
  • Signing authority on every representative role. Each current role at GET /companies/{company_id}/roles, in ?expand=roles, the KYB report and an on-demand refresh result (GET /jobs/{id}) carries a signing_authority that says how its holder may sign — null for every role at a registered association. A registered association is its stored legal form (an e.V. or a wirtschaftlicher Verein); only where no legal form is stored, a VR register or "e.V." or "eingetragener Verein" in its name counts. The reading is not certified for associations yet (a later release may certify them). On the company surfaces (a company's roles list and ?expand=roles, the KYB report, /answers, a refresh result) every representative role of a company whose status is terminated publishes signing_authority: null. A person's own roles (/persons/{person_id}/roles) read the holder's own entry words alone, as before. Company surfaces publish no signing authority when the source withheld every checked text or predates the field. A person's roles publish no entry words that the source withheld and none that hold a date. On a company surface, own words that hold a date answer nothing for that role — signing_authority is {type: null, basis: "entry", self_dealing_exempt: null, text: null, real_estate_power: null, limited_to_branch: null} (every field null except basis "entry"; neither the rule nor the statute answers). A Prokura's dated wording publishes signing_authority: null. A refresh result (GET /v1/jobs/{job_id}) whose render withheld someone publishes signing_authority: null for that role. The stored words are dropped before the role is read. Where the company's privacy rules withheld anyone on its lists — a representative or a Prokura holder — only the holder's own entry words answer. A rule whose answer depends on an amount or a kind of deal (land, loans) answers nothing for a role it moves between alone and joint; a role that signs jointly either way stays joint. Words that negate a power, or deny a § 181 BGB release, state nothing and grant none. Beyond that: type (sole / joint) with a new basis naming which of three sources answered — the holder's own entry words (entry), the company's printed general representation rule (general_rule) or the statute of the legal form (law). A rule answers a role only where it names that role's organ or names no organ, and is read against the holders of the organ it names; a rule that states representation plainly blocks the statute for every role, also one it does not name. self_dealing_exempt is true only for a full release from § 181 BGB; a partial one stays null, and a release read from the rule publishes with the rule's words in text. Words that exclude the holder from representation, or that negate a power, keep type: null with the words in text and basis: entry; words that deny a § 181 release grant none. A rule whose answer depends on an amount answers nothing for a role it moves between alone and joint (a role that signs jointly either way stays joint). Where the company's privacy rules withheld anyone on its lists (a representative or a Prokura holder), only the holder's own entry words answer. A former role, and every role on a person's own list (GET /persons/{person_id}/roles), answers from the holder's entry words alone — a row the company's Sperrung check did not keep publishes nothing of the entry. A Prokura's authority is read from its own wording as before and now also names its basis. POST /answers' may_act_alone is read from the same role the roles list builds for the same payload, so the two cannot disagree; an answer that rests on the statute carries medium confidence and names the statute in its details. The company record's representation_rule is the rule the roles applied: the newest printout's rule, from its meta row; only where no meta rule exists does the record fall back to the latest entry's (the roles list carries no events, so there the meta row's rule is the only source).

10 November 2026

  • Document downloads cost 10 credits. GET /v1/documents/{document_id}/content and POST /v1/documents/{document_id}/links each cost 10 credits; the new link endpoint is free while a paid link this key made for the same document is still live. A link from POST /v1/documents/{document_id}/links serves the file through https://files.registercheck.de/d/… for up to 60 minutes and 20 downloads; GET /v1/documents/{document_id}/content still answers 302 with a link that expires after 5 minutes.

  • The MCP server's get_document uses the new link. It calls POST /v1/documents/{document_id}/links (10 credits; free while the link lives), reads the file from files.registercheck.de, and returns the same link for the user's browser. Continuing a long document with offset within those 60 minutes is free.

  • A plan refusal names the plan that allows it. 403 destination_requires_plan, job_requires_plan and monitor_limit_reached carry feature and required_plan; monitor_limit_reached also carries used (errors).

  • GET /account lists its features: each feature a key can be refused, whether this workspace has it, and the plan that turns it on when it does not.

  • A destination says when the plan stops it (requires_plan): "business" for a Slack channel or webhook while the workspace is on a smaller plan, null otherwise. It turns back to null by itself after an upgrade.

  • A monitor says how and when it reports: check_schedule, next_check_at, paused_at and counts_toward_limit. A monitor created with an API key reports as soon as a change is detected (check_schedule null).

  • One free feed of all your company monitors' events: GET /events?monitored=true, ordered and paged like monitor_id.

  • Event types carry a severity, critical or normal.

  • Test a webhook destination: POST /destinations/{destination_id}/test sends one signed sample delivery whose test is true. It is free, at most 10 an hour, sent once and never counted towards switching the destination off.

  • Slack and webhook destinations come with Business and Scale. POST /destinations with "channel": "slack" or "webhook" answers 403 destination_requires_plan on a smaller plan, as the plans describe. A Slack channel or webhook you set up earlier stays set up: an event of a monitor whose workspace has a smaller plan is not sent to it (its delivery is skipped), and it receives again after an upgrade. E-mail destinations are not affected (details).

  • Claude and ChatGPT can connect to the MCP server with a workspace API key. On the Registercheck sign-in page an assistant's connection now offers Mit API-Schlüssel verbinden: the connection then acts with that key, its limits and its workspace's credits, and ends when the key is revoked (details). The key never signs anyone in to the web app.

  • The MCP server reads a register document in the chat. get_document returns a PDF's text layer or structured register data as XML, and gives a download link on files.registercheck.de for scans without a text layer.

9 November 2026

  • The MCP server accepts a workspace API key. AI platforms that cannot sign in with OAuth, such as Langdock, can connect to the Registercheck MCP server with an API key sent as Authorization: Bearer, once the workspace allows it: API-Schlüssel für KI-Plattformen (MCP) in the workspace settings, off by default. A tool costs what the same /v1 call costs, charged to the key's workspace. Nothing changes for /v1 or for OAuth connections.
  • A company's register history, entry by entry. GET /companies/{company_id}/register-entries lists the register court's own record of a company, newest entry first: one register_entry per entry, with its running number on the register sheet, the day it was entered and every change it made. GET /companies/{company_id}/events still flattens the same history into one event per change.

7 November 2026

  • Smaller fixes found while checking the documentation against the API.
    • GET /companies/{company_id}/documents and GET /companies/{company_id}/financial-statements answer a merged company id with 301 company_merged, like the record and its other sub-resources; they answered 404. A survivor that is no longer public still answers 404.
    • HEAD /health and HEAD /openapi.json answer like GET, without a body; they answered 405.
    • A search monitor's recent_matches.sample[].event_type uses the names GET /events publishes (company.role.added, not company.officer.appointed).
    • Responses no longer carry an undocumented header that named a supplier. The documented X-RateLimit-* headers are unchanged.
    • A 400 from the company filter describes the filter only, and a 400 from GET /events names each parameter in this API's spelling (effective_date[gte], not effective_date_gte). A 402 for one credit says "1 credit". Branch on code, never on detail.

6 November 2026

  • WZ 2008 on the company record. industries_wz2008 lists the company's WZ 2008 classification (Klassifikation der Wirtschaftszweige, Ausgabe 2008) from section to subclass, beside the WZ 2025 industries. It is derived from the WZ 2025 subclass by the official Destatis correspondence; where one WZ 2025 subclass corresponds to several WZ 2008 subclasses, Registercheck picks one from the registered business purpose.
  • A merged company id redirects only to a public company. GET /companies/{company_id}, its sub-resources and GET /events?subject_id= answer 301 company_merged for a merged id as before, unless the surviving company is no longer public: then the merged id answers 404 not_found, like an id that was never there, and names no company.
  • The KYB report, verify, answers, ownership, beneficial owners, refresh results and find follow who the register says is in office. Like the role lists, a person registered under a changed name is listed once, under the name the register uses now: the KYB report, POST /companies/verify, POST /answers, the general partners on GET /companies/{company_id}/shareholders and GET /companies/{company_id}/ownership-tree, the computed beneficial owners, a refresh job's company result, and the officer a POST /companies/find hit names. Verify still matches a signatory by a name she was registered under before.
  • Role lists follow who the register says is in office. A person registered under a changed name is listed once, under the name the register uses now. GET /companies/{company_id}/roles, the company's counts.current_roles, ?expand=roles, GET /persons/{person_id}/roles and GET /persons/{person_id}/holdings follow that decision for who is current and when the office ended.
  • Jobs: fewer refusals and duplicate fetches, honest failure codes. An open job of the same company now comes back free even when the workspace is at its 10-open or 120-per-hour limit; at a limit, a company whose data is fresh enough still gets its stored answer, and only a job that needs the register is answered 429 rate_limited. Under the limits, a job asked right after a company read joins the refresh that read started instead of asking the register twice. result.register_entries_added now counts the register entries a refresh added, and is null when they could not be counted. A failed job names its cause: register_unavailable when the register did not hand over a document, and the new duplicate_company_record (asking again cannot help) when the company's register entry is held under another company id. status_transitions.running_at is set for a job that ran, also when it ended quickly. Job webhooks no longer carry sentry-trace or baggage headers.

The documentation was checked against the live API and corrected throughout. Features the API already served are now documented:

  • Documented: verify a customer's details. POST /companies/verify compares a company's name, register identity and address — one line in text, or fields in company — and optionally a signatory with the register, and runs the risk checks you name (status, insolvency, sanctions, ubo). 4 credits, plus 8 with ubo; a company that is not found (404) or ambiguous (409) is not charged. Check a customer walks through it.
  • Documented: ask one question about a company. POST /answers answers one of six kinds of question (representation, beneficial_owner, officers, shareholders, seat, status) from register data. 8 credits; a question outside the six kinds answers 422 question_not_supported and is not charged.
  • Documented: download a register document. GET /documents/{document_id}/content answers 302 with a link to the file that expires after 5 minutes, for 1 credit; each document's links.download names it. Documents.
  • Documented: search monitors. POST /monitors with a prompt or a filter instead of a company watches new companies, or changes at companies, that match a search. Creating one is free; its matches are sent by e-mail to the API key's owner, at 1 credit per match delivered. A search monitor carries no metadata. Search monitors.
  • Documented: search by street address. The company filter's company.address matches the registered address: street, with postal_code and city to narrow it. Filtering.
  • Documented: a radius around an address or a town. POST /companies/find reads a radius in words ("im Umkreis von 5 km um Marienplatz 1, München") into near, and near_place names the place it measured from.

These changes were already in effect before this date; the reference now describes them:

  • A search monitor's prompt names its events. Without event_types, the events a prompt names are the ones it watches: "Insolvenzen in Berlin" watches insolvencies, "Kapitalerhöhungen bei GmbHs in München" capital changes. A prompt that names no criterion a search can hold (an industry, a federal state, a city, a legal form or capital), such as "Kapitalerhöhung" alone, answers 422 prompt_not_understood, which always carries unrecognized.
  • A court change names the former court as previous. In company.register_court.changed events, a court the register's wording calls the former one ("bisher Amtsgericht X …, nunmehr Amtsgericht Y") is now data.previous, never data.current: such an entry used to publish X as the current court, and now publishes previous X and current Y. A court change noted when a register sheet was rewritten names only the former court; its current is null.
  • Monitored companies count per workspace. The limit on monitored companies — what a resume with PATCH /monitors/{monitor_id} is checked against — counts the monitors of the workspace, created in the app by any of its members, not the person's across every workspace they belong to. The limit is the workspace's plan's; on the free plan (Gratis) it is the free plan's in a personal workspace and 0 in a team workspace, where resuming a dashboard monitor answers 403 monitor_limit_reached with limit 0 until the workspace takes a paid plan. Otherwise pausing or deleting one of the counted monitors GET /monitors lists makes room. GET /account's monitors are the workspace's. Monitors created with an API key or through the MCP server still never count.
  • A key whose person may only read in its workspace cannot write. Creating, changing and deleting lists, list items, monitors and destinations, and changing a formation's metadata, answer 403 forbidden when the role the API key's person holds in the key's workspace may only read, or when the workspace is closed. Nothing is changed and nothing is charged. Each of these operations now declares that 403, and POST /destinations also declares the 403 destination_requires_plan it already answered.
  • A key whose person may only read spends no credits. Every operation with a price — reads included, and through the MCP server — answers 403 forbidden instead of charging when the API key's person may only read in the key's workspace, or when the workspace is closed, whatever the balance (not 402). Nothing is charged. Every priced operation now declares that 403.
  • Where the roles of a company come from. GET /companies/{company_id}/roles and the KYB report's roles part carry an extract (status, fetched_at, document_id) naming the register extract the roles are read from. status is parsed (read), processing (on file, being read), not_fetched (never fetched), failed, or unknown — the API's own word for a moment when it could not ask where the data stands. document_id and fetched_at are null when the company's roles were written from more than one filing; the extract describes the company's whole roles record, whatever status and role_type the page filters by. The roles of a person (GET /persons/{person_id}/roles) say extract: null: no one filing is behind them.
  • A shareholders page says when its list was fetched. fetched_at on GET /companies/{company_id}/shareholders is the moment the filed shareholder list was fetched, whenever the page's holders all come from that one list; otherwise it is null, as document_id already was.
  • Both changes add properties; nothing is removed or renamed. A client that validates responses strictly against an older copy of this spec will see extract as a property that copy does not know (our schemas admit no unknown names); keep your copy of the spec current, or allow additional properties when you validate.

5 November 2026

  • Jobs: ask the register for a company's current documents. POST /jobs with type: "refresh_documents" and a subject_id answers 202 with a job; GET /jobs/{job_id} says when to look again (Retry-After) until the job is succeeded, failed or canceled, and GET /jobs lists your jobs. A succeeded job's result holds its documents, and the refreshed company for 24 hours. 25 credits when the register is asked; 10 when the data we hold is newer than max_age_seconds (retrieval: stored); nothing when this workspace already has that job open; refunded in full when it ends failed, or canceled before the register is asked (POST /jobs/{job_id}/cancel); the balance must hold 25 when a job is asked for. Scale and Enterprise; any other plan gets 403 job_requires_plan and is never charged. A webhook destination whose enabled_events lists job.succeeded, job.failed or job.canceled is told when a job ends, signed as every webhook is.
  • A person's roles list an office once. GET /persons/{person_id}/roles, ?expand=roles and GET /persons/{person_id}/holdings also listed an older copy of some offices, from the register's first import in early 2025: listed as current, with no dates and holder_as_registered: null, next to the same office as the company lists it. Where the company's list holds the office for the person, the copy is gone; a Prokura now carries the role id the company's list uses.
  • Every role carries its holder's date of birth and place of residence, as the register entry states them. holder_as_registered on every role (GET /companies/{company_id}/roles, ?expand=roles, the KYB report, GET /persons/{person_id}/roles): name, birth_date, city (Wohnort). It is null when a company holds the role, or, on a person's list (/persons/{person_id}/roles, ?expand=roles), when the entry cannot be shown: the company withholds that row, or its check could not be made. A birth date withheld at the person's request stays null. No extra charge. Before, this took one GET /persons/{person_id} per holder and was out of reach for a holder with no person id. If you validate responses against a saved copy of the contract, update it, because role allows no other properties.

3 November 2026

  • A gGmbH and a gUG are legal forms of their own (breaking for every filter that names gmbh or ug): a non-profit GmbH carries legal_form: "ggmbh" and a non-profit UG legal_form: "gug" (new), instead of gmbh and ug. GET /legal-forms lists gug next to ug. A company filter on legal_form: ["gmbh"] no longer returns gGmbHs, and ["ug"] no longer returns gUGs; to keep the set you had, ask for gmbh and ggmbh (or ug and gug). Companies already registered carry their own code too. The migration guide has the pairs.
  • A company's tax IDs have their own endpoint, and come with the company on request. GET /companies/{company_id}/tax_ids lists the USt-IdNr. and the Steuernummer the company prints on its own Impressum, each typed as one of Stripe's tax ID types (eu_vat, de_stn), with the page and the date it was read. It costs 10 credits, and nothing when no tax ID can be shown. GET /companies/{company_id}?expand=tax_ids adds the same list to the company at no extra charge; expand=roles&expand=tax_ids asks for both. The values are not checked with any tax authority, and the Steuernummer of a sole trader or another form that identifies a natural person is never shown.

30 October 2026

  • Find and the company filter cost 1 credit per 10 companies they return, nothing when they find none. POST /companies/find and POST /search/companies/filter were charged for the results a call asked for, ⌈limit/10⌉, also when fewer or none came back. They now cost ⌈returned/10⌉: a page of 3 is 1 credit, an empty one is free. Your balance must still hold ⌈limit/10⌉ before the call. x-credit-cost-per says so with counted: returned.

29 October 2026

  • Finding companies reads cities, trades and English better, and the same way each time. POST /companies/find searches a city by the name the register writes ("Frankfurt" as Frankfurt am Main, "Koeln" and "Munich" as Köln and München), can search a trade by the WZ 2025 code the official keyword index gives it ("Bäckereien in Berlin" searches 10.71.0), and otherwise by a word stem of the business purpose ("Elektriker in Köln" searches the purpose for "Elektriker"); interpreted_filter shows which. An English activity is read as a German purpose stem. An activity the prompt names that the reading could not take comes back in unrecognized, instead of being left out without a word. The same prompt reads the same way for as long as its reading is kept.
  • The company filter refuses what its schema refuses, uncharged. near takes latitudes from -90 to 90, longitudes from -180 to 180 and a radius of 1 m to 200 km; a list criterion (legal_form, status, register_court, register_type, industry) holds at least one item and an industry code at most 10 characters; contains takes 2 characters or more and starts_with 1; a date is a calendar day as YYYY-MM-DD. Each answers 400 validation_failed naming the field. Such input was answered and charged before (an empty list matched every company, a date that is no day answered 503).
  • The company filter costs 1 credit per 10 requested results, and a page holds up to 1,000 companies. POST /search/companies/filter cost 25 credits a page of at most 100; it is now priced as POST /companies/find is, ⌈limit/10⌉ a call (a page of 100 is 10 credits, of 1,000 is 100). Its limit now takes 1–1,000 (default 20, unchanged); the filter still serves its first 10,000 companies.
  • Finding companies searches the activity a prompt names. POST /companies/find searches an activity by the WZ 2025 code whose official title describes it ("ambulanter Pflegedienst" is 86.94.1 Ambulante Pflegedienste), else by a word stem of the register's business purpose (company.purpose), instead of guessing a whole industry, which answered entire sectors. interpreted_filter shows what was searched, and ignore takes purpose to leave the purpose out.

26 October 2026

  • A person search hit carries the full date of birth. Each person in GET /search/persons and GET /search/suggestions now has birth_date and birth_month next to birth_year, as the person's record (GET /persons/{person_id}) states them. A person whose date of birth is withheld has all three null, as on the record, and a person GET /persons/{person_id} answers 404 for is not listed. When the dates cannot be read, the search answers 503 service_unavailable with Retry-After and nothing is charged.
  • The MCP server finds people. The Registercheck MCP server has a new tool, search_persons (1 credit, like GET /search/persons): people by name, optionally by year of birth and city, each with their date of birth and city. A person in list_company_roles, list_company_shareholders and get_company now carries person_id, the id that search answers with. Register text such as an event's wording is passed on as the register states it; its dates of birth are no longer cut to the year.

17 October 2026

  • The MCP server charges what the API charges. A tool call through the Registercheck MCP server now costs the credits of the /v1 call it makes, like the same call made with an API key: search_companies and list_company_documents 1 credit, get_company, list_company_roles, list_company_shareholders, list_company_events and create_monitor 10. Until now only list_events cost credits there. POST /monitors through a connection of the MCP server costs 10 credits, which free credits do not pay. Nothing changes for API keys.
  • A monitor created through the MCP server is one created with an API key. It costs 10 credits and no longer counts against the companies your plan monitors; resuming it is never refused for that limit. GET /account's monitors counts the monitors created in the dashboard only.
  • Ten times the credits in every plan. Starter includes 1,000 credits a month, Business 10,000 and Scale 100,000, at the same plan prices. The free plan's 50 credits stay as they are.

16 October 2026

  • Resuming a monitor can be refused. PATCH /monitors/{monitor_id} with {"status": "active"} answers 403 monitor_limit_reached when resuming would monitor more companies than the plan allows. Only active monitors count; monitors created with an API key never do.

15 October 2026

  • The reference-data lists answer the page envelope (breaking): /legal-forms, /courts, /role-types, /industries, /event-types and /event-groups now answer { "object": "page", "data": [...], "next_cursor": ... } like every other list, instead of { "object": "list", "data": [...], "has_more": false }. They take limit (1–100) and cursor like every other list, and limit is optional: omit it to receive the whole list in one page, next_cursor null — every vocabulary, /industries' 2,030 codes included. The data and its order are unchanged, and they stay free. The switch is hard: there is no transition period and no Deprecation header. See Pagination.
  • Which match_confidence to rely on. People recommends using person links at 0.80 or above. On 2026-10-15 links stored at 0.75, 0.70 or 0.60 whose register entry did not match the linked person were corrected: they now point to the matching person at 0.95 or 0.90, or to a new person at 0.95.
  • A monitor's event is dated when the monitor reports it. On GET /events?monitor_id=, in a delivery and in a webhook body, created_at is the moment the monitor reported the event — the same instant in all three. For a monitor created with an API key that is within seconds of the moment the change reached Registercheck, as before. A monitor created in the dashboard reports at its check time; polling on created_at[gte] still finds every event.
  • Destinations carry a role: own, account_inbox or route, saying which events a destination receives. A route's cadence cannot be changed (409 route_endpoint). Creating a destination with a route's address makes it own.
  • Webhook deliveries of dashboard monitors. A dashboard monitor that delivers to a webhook sends each event as a delivery with cadence instant, listed by GET /deliveries. Its e-mail and Slack summaries are not API deliveries and are not listed.
  • The account inbox's cadence sets how often dashboard monitors check when none was chosen for them: instant the plan's fastest, daily daily, weekly and monthly weekly.

10 November 2026

  • New API keys. A key created from this date starts with rc_prod_ and is 107 characters long. Keys created before 2026-11-10 start with registercheck_ and keep working. A revoked key stops working with the next request.

9 October 2026

  • Computed beneficial owners. GET /companies/{company_id}/beneficial-owners returns a beneficial_owner_analysis: each natural person the filings compute as qualifying, with the path and the multiplied percentage. status is complete, partial or none_found. gwg_above_25 (more than 25%) and amlr_at_least_25 (25% or more) are separate flags. fictitious_rule_applies follows the GwG test only, and stays false when a holder was withheld, an unidentified person could still reach 25%, or that person shares a name with an identified holder and together they could reach 25%. A person is identified by one linked person record, or else by the same full name and birth date (matched_by). Managing directors stay on /roles. 25 credits. Computed from register filings; may be incomplete. Not a Transparenzregister extract.
  • KYB report. GET /companies/{company_id}/kyb-report assembles the company record, the first page of current roles, the first page of shareholders, the ownership tree to depth 3, and references to the shareholder list and the register extracts. 50 credits, charged once. A part that cannot be completed is a 503 and is not charged, including a shareholder list that is still being extracted. A privacy check that cannot be completed is a 500, as on the other company routes. The report does not include computed beneficial owners; GET /companies/{company_id}/beneficial-owners computes them. The report is computed from register filings. It is not an extract from the Transparenzregister, and it is no substitute for your own due diligence.
  • Ownership tree, levels 2 and 3. GET /companies/{company_id}/ownership-tree follows linked companies for the depth you ask (1, 2 or 3). effective_percentage is the product of the percentages along the path, equal to the holding's own percentage at depth 1 and rounded half up to four decimal places further down. A cycle, and a company that holds itself, is flagged and not followed. unresolved says where the chain ends (foreign_entity, entity_not_linked, stock_corporation, no_shareholder_list, extraction_pending, depth_limit, cycle, self_holding, percentage_withheld). complete and truncated say whether that list is finished. Still 10 credits. Asking still starts at most one extraction, for the company you asked about. Companies further up are read from ownership already stored.

8 October 2026

  • A person's age. GET /persons/{person_id} includes age: whole years as of today in Europe/Berlin, computed from birth_date on each request and never stored. It is null when the date is missing, in the future, or the age would be over 120.
  • Filter companies by age. roles.conditions[].age selects representatives, and Prokuristen when the condition also sets role_type to ["authorized_signatory"]. Kommanditisten take shareholders.conditions[].age with type: ["limited_partner"]. Bounds are whole years from 0 to 120. An age on a role by itself, and a Kommanditist's age or birth_date by itself, answers 400: combine it with a narrowing criterion, for example a name, a register, a location or another company filter. A shareholder criterion counts; status and holder_type alone do not. Plain shareholders have no date of birth, so age there answers 400.

October 2026: one model

Breaking. /v1 uses one word for each thing the register holds, the same in every path, field, id and page of these docs. The glossary lists the words; the migration guide lists every change.

  • Ids say what they name: cmp_… for a company, per_… for a person, and so on for every kind. A raw UUID is still accepted until 31 December 2026. An id of the wrong kind answers 400 validation_failed instead of 404.
  • The workspace id on GET /account is a wsp_… id derived one way from the app's id (org_personal_…), which it was before: it no longer matches anything the app shows. No request takes a workspace id.
  • One page envelope for every list and search: {object: "page", data, next_cursor}, paged with cursor. starting_after, ending_before, page, has_more and next_page are gone.
  • One reference shape for a company or person: party, {object, id, name}.
  • Roles: /companies/{company_id}/roles and /persons/{person_id}/roles replace /companies/{id}/officers and /persons/{id}/positions, with one role object. Every list that narrows by role takes role_type; the role's own field is type.
  • Holdings of a person: /persons/{person_id}/holdings, the person's shareholdings.
  • Ownership tree: /companies/{company_id}/ownership-tree replaces depth on /shareholders. A shareholding names its holder (was owner), and a page of shareholders carries extract (was availability).
  • Events: /events with object: "event", a subject, data shaped by the event type, and as source, the register entry it was read from (the document for a shareholder list or annual accounts; null when the entry's number is not known). Its previous path, /company-events, keeps answering until 31 December 2026.
  • Monitoring: /destinations (was /notification-endpoints, with address for the address), /deliveries, /event-types and /event-groups (was /monitor-event-types). /alerts is gone: read what a monitor matched at /events?monitor_id= (free), and what was sent at /deliveries. A monitor's webhook body is a delivery holding its events. A destination has a cadence: instant, or for e-mail and Slack a daily, weekly or monthly digest at 07:00 in the workspace's time zone, and can be a Slack channel.
  • Role events: company.officer.appointed, .changed and .removed are company.role.added, company.role.changed and company.role.removed.
  • Lists: /lists with list and list_item (was /collections).
  • Search answers summary objects with a type (company or person); city moved to address.city, so apart from object and type a summary is a subset of its full record.
  • The filter's role criteria are named roles (were officers), and a condition's role type is role_type (was role). name matches a person's first, last or full name as well as a company holder's name, and first_name and last_name match one of a person's names.
  • Errors: a field that fails validation is 400 validation_failed with errors[] on most operations; /monitors and expand still answer a field error as 400 invalid_request, its detail naming the field. Renamed paths answer 410 endpoint_retired naming the replacement.
  • Credits: Registercheck-Credits-Charged is on every response to a call made with a key. Prices did not change.
  • name is the search term on GET /formations and GET /events too; q keeps working on /formations until 31 December 2026.
  • The reference is grouped by the first segment of the path (the reference lists under Reference data, /health under Platform), and lists only what is served.

October 2026: before the one-model release

  • Search takes name. GET /search/companies, /search/persons and /search/suggestions read the search term from name. q keeps working until 31 December 2026.
  • GET /events lists register events across all companies, and GET /events/{event_id} reads one. The previous path, /company-events, keeps working until 31 December 2026.
  • One status rule. The company record, search results, suggestions and the filter derive status the same way, always lowercase: active, liquidation, terminated or unknown.
  • Event types renamed (breaking for monitors that name them): company.shareholder.changed is company.shareholding.changed, and company.shareholders.changed is company.shareholder_list.changed. The old names answer 400 naming the new one.
  • Insolvency and other register entries are monitorable, in the groups insolvency, conversion and other_entries.

2 October 2026

  • legal_form replaces legal_form_code on GET /formations.

1 October 2026

  • The /v1 naming revision: the formations feed (/formations) replaces /search/new-registrations.

17 September 2026

  • The /v1 reference replaces the reference of the earlier API.

On this page