Companies House Officers Scraper — Directors & Secretaries

UK Companies House Officers Scraper — Directors & Secretaries (United Kingdom) ✅ No API Key

Get the officers of any UK (United Kingdom) company from Companies House by company number — current and former directors and secretaries, with role, status, appointment/resignation dates, date of birth, nationality, country of residence and correspondence address. One clean row per officer. Powered by the Neuralverge API. No API key or account required.

Ideal for KYC/KYB, due diligence, compliance and mapping company leadership.

✨ Why this Actor

• 👥 One row per officer — current and former, with role, dates, nationality and address, ready for a spreadsheet, CRM or AI pipeline.
• 💸 One flat price per row — $0.005 per officer, no run fee and no start fee. A company with no officers comes back as one no result row, billed like any other row.
• 🔑 No API key or account — extraction runs on the Neuralverge backend.
• ⚡ Real-time & structured — fresh data each run.

🔧 How it works

1. Provide a UK company number (e.g. 08804411) — or an advanced full Companies House officers-page URL.
2. Run the Actor. Fetching and AI-structuring the officers happens on the Neuralverge backend.
3. Get one dataset row per officer. Export to CSV, JSON or Excel, or pull it over the Apify API.

A company with no officers still returns one explicit no result row.

Input

One company per run.

Field	Type	Notes
companyNumber	string	The UK Companies House company number, e.g. 08804411.
companyUrl	string	Advanced: a full Companies House officers-page URL to use instead of the number.

{
  "companyNumber": "08804411"
}

What you'll receive

One dataset row per officer. Each row is an officer object with company_number (the company it belongs to) plus: name, role, status (Active / Resigned), appointed_on, resigned_on (when applicable), date_of_birth, nationality, country_of_residence, occupation and correspondence_address (a nested object).

Nulls are normal. Fields not published for an officer (e.g. date_of_birth for a corporate secretary, or resigned_on for an active officer) come back absent or null.

When nothing is found

A lookup that runs but returns no officers still writes a row, so a batch never silently loses an input:

Column	Value
company_number	echoed back exactly as submitted
found	false
message	why nothing was returned

A company with no officers produces exactly one such row for the whole run. Filter these out with found != false (or drop rows where message is set). This row is billed as one officer — see Pricing.

Example output (real run)

One officer row from the officers page of company 08804411, exactly as it appears in the dataset. A single run of this kind returned 14 officers (current and former) — this is one of them.

{
  "company_number": "08804411",
  "name": "BRITTON, Caroline Louise",
  "role": "Director",
  "status": "Active",
  "appointed_on": "8 March 2019",
  "date_of_birth": "February 1965",
  "nationality": "British",
  "country_of_residence": "United Kingdom",
  "correspondence_address": {
    "street_address": "30 South Colonnade",
    "locality": "London",
    "country": "United Kingdom",
    "postal_code": "E14 5HX"
  }
}

Genuine output from a live run — one director with role, dates, nationality and correspondence address.

Pricing

Pay per event — $0.005 per officer ($5 per 1,000) written to the dataset. There is no run fee and no start fee.

Event	Price	Charged
Actor start	free	never
Failed run — invalid input, API error, timeout	free	never
Row written to the dataset	$0.005 ($5 / 1,000)	every row, including the "no result" row

A completed lookup is billed as one officer, matched or not. When the source returns nothing, the Actor writes one explicit no-result row — the query you submitted plus found: false and a message explaining it — and that row is charged at the normal per-officer price. A company with no officers at all produces exactly one such row for the whole run. A run that fails (missing input, bad key, upstream error) writes no row and costs $0.00.

Pricing is on top of your Apify platform usage.

Rate limit

There is a ceiling on how fast one Apify account can pull from the Neuralverge backend: 10 requests per second for this Actor, counted separately from the other Neuralverge Actors. One run is normally one request, so this is about how many runs you start at once, not about the size of a single run — at typical run times that is dozens of runs in flight at once, which is well above ordinary use.

Updated August 2026: this ceiling was doubled from 5 to 10 requests per second. Bulk jobs that used to hit 429s now go through.

Above the ceiling the backend answers HTTP 429. The Actor waits out the Retry-After it asks for and retries a few times before giving up; a run that does give up writes no row and is not charged.

If you need a higher rate for a bulk job, get in touch.

Free plan limits

Users on any paid Apify plan are not affected by anything in this section.

On the Apify Free plan this Actor may be started 5 time(s) per calendar month per user. A run that finds nothing still counts, because the lookup is performed either way. Every Neuralverge Actor carries its own allowance — running one never uses up another's. When a limit is reached the Actor stops gracefully with a status message naming it; everything resets on the 1st of every month, and any paid Apify plan removes all of it.

Integrations & API

Results are stored in a standard Apify dataset — export as CSV, JSON, XML or Excel, or fetch on demand through the Apify API. The Actor also plugs into Apify's integrations (Make, Zapier, n8n, webhooks) and can be called from any MCP client.

FAQ

Do I need an account or API key? No. Extraction runs on the Neuralverge backend.

Does it include former officers? Yes — current and resigned officers are both returned, distinguished by the status field.

Am I charged if there are no officers? Yes — a lookup that ran is billed as one officer even when it matched nothing, and you get a single no result row that says so. A run that fails (missing input, bad key, upstream error) is not charged.

---

Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Companies House or the UK Government. Data originates from the public Companies House register.