Companies House (UK): 8 reads, one client

The authoritative UK company register — profiles, officers, filings, charges, insolvency and persons with significant control. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.

What Companies House (UK) can do here

The integration exposes 8 reads, each with a declared input and output schema rather than a page of documentation you would have to translate. The authoritative UK company register — profiles, officers, filings, charges, insolvency and persons with significant control.

How it authenticates

Companies House (UK) authenticates with a apiKey and a apiPassword, supplied per request or stored once against your account and sealed at rest. On our side the same value is read from apiKey when we broker the call for you.

Capabilities it fulfils

Companies House (UK) answers business.registry.get and business.registry.search in the vendor-neutral form, which means code asking for any of those can be pointed at Companies House (UK) without naming it. If it goes down, or you would rather use somebody else, that is a preference change and not a rewrite.

• searchCompanies — read: Search the UK register by name or number. The connection test.
• getCompany — read: The full profile for one UK company.
• getOfficers — read: Directors and secretaries, current and resigned.
• getFilingHistory — read: Everything the company has filed, newest first.
• getCharges — read: Registered charges — who has security over the company's assets.
• getInsolvency — read: Insolvency cases against the company.
• getPersonsWithSignificantControl — read: Beneficial owners — who really controls the company.
• getRegisteredOfficeAddress — read: The registered office address on its own — the cheapest possible profile read.

Questions

Do I have to bring my own API keys?

You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.

What happens to a key I store here?

It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.

What happens when a provider changes its API?

The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.