Open Company Data in United Kingdom: Official Sources, APIs and Reuse Rights
The United Kingdom is one of the best jurisdictions for official company data because Companies House provides public search, API documentation and bulk-download routes. That strength can also create false confidence. A serious UK company-data workflow still needs to separate the company-register core from procurement notices, Gazette events, charity records, VAT checks, trademark context, LEI records and regulated financial-services data. Those layers answer different questions and carry different reuse, privacy and update risks.
This material refresh replaces the older UK page, which is publicly crawlable but below the current CompaniesData depth and formatting standard. The new version is a reference article rather than a thin programmatic page. It includes editorial methodology, coverage and update-risk analysis, a reuse checklist, source-by-source deep dives, practical manual/API/bulk options, missing-data gaps, a recommended data model, CompaniesData normalization value, expanded FAQ and official sources.
The short answer for data teams is: use Companies House search, API and bulk downloads as the backbone; add Find a Tender and Contracts Finder for procurement, The Gazette for statutory notices, Charity Commission for charity entities, GOV.UK VAT checks for tax-identifier validation, UK IPO for trademarks and GLEIF for LEI records. Keep FCA-style regulated financial-services routes in a held track until later source-live access and lawful-use review are clean.
Key Takeaways
- Best official backbone: Companies House search, developer API and bulk downloads provide the core company-register evidence.
- Best enrichment layers: Find a Tender, Contracts Finder, The Gazette, Charity Commission, UK IPO, GOV.UK VAT checks and GLEIF add context but are not complete company registers.
- Main reuse boundary: company filings, officer fields, persons with significant control, dissolved-history details, paid documents and contact data need field-level caution.
- Marketing-contact caution: public company visibility is not permission to build email, phone or lead-list exports.
- Publication gate: this refresh passed the final source-live gate for linked sources; render, crawler, sitemap and supported indexing artifacts are recorded in the publication report.
Editorial Methodology
CompaniesData ranks UK company-data sources by authority first, then access model, source stability, reuse clarity and data-model value. Official sources are preferred: Companies House for the company core, official procurement portals for contract context, The Gazette for public notices, official charity and tax routes for specialist checks, UK IPO for trademark context and GLEIF for LEI-bearing entities. Non-official aggregators may be useful for market context, but they are not used as evidence for official reuse rights in this article.
The source screen behind this article reviewed 12 UK routes with browser-like, Googlebot-like and Bingbot-like profiles. It found 6 stable source candidates, 5 conditional candidates and 1 held route. The clean article set excludes held routes and uses 11 official or high-quality public routes for the article body.
Each source receives an allowed claim and a blocked claim. This matters because the UK is not source-poor: the risk is that teams overextend strong Companies House availability into unsupported claims about private contact data, full beneficial-owner reuse, paid document availability, dissolved-company history or regulated financial-services coverage.
Coverage, Access and Update-Risk Analysis
Company-register coverage: Companies House is the central authority for incorporated company records. Company number, registered name, status, filing history and registered-office context are the typical backbone fields. The article can safely describe Companies House as the core official UK company-register source, but should not imply that every downstream document or person-linked field is suitable for unrestricted commercial reuse.
API and bulk access: the developer API and bulk-download service make the UK commercially useful for data operations. API access is best for targeted lookups and workflow automation. Bulk downloads are best for population-scale reconciliation and periodic refresh. Both still need source terms, update dates, field dictionaries, authentication/rate notes and error-handling records.
Procurement and public notices: Find a Tender and Contracts Finder add supplier and buyer events. The Gazette adds statutory notice context, especially for insolvency and formal public notices. These are event layers. They are useful for risk, procurement intelligence and public-sector sales research, but they should be matched back to the Companies House core with confidence scores.
Charity, tax, IP and LEI context: Charity Commission records identify charity entities in England and Wales. GOV.UK VAT checks can support tax-identifier validation where the service terms and use case allow it. UK IPO trademark routes add brand/IP context. GLEIF adds standardized LEI records for entities that have LEIs. None of those layers is complete UK business coverage.
Update risk: UK company records, filings, procurement notices, Gazette notices, charity records, VAT checks, trademark records and LEI records update on different schedules. A reliable dataset needs per-source access dates, observed update dates, source owner, field scope and data-retention policy rather than one generic last-updated timestamp.
Reuse Checklist
- Authority check: identify whether the field came from Companies House, procurement portals, The Gazette, Charity Commission, GOV.UK, UK IPO or GLEIF.
- Access-model check: separate public search, official API, bulk download, public notice, regulator register, tax validation, IP guidance and LEI API routes.
- Licence and terms check: preserve Crown/open-government licensing notes, Companies House API or bulk terms, Gazette terms and service-specific limitations.
- Field-scope check: keep company core, filings, officer/person fields, PSC fields, procurement events, notices, charity, tax, trademark and LEI fields in separate layers until matched.
- Privacy check: treat officer, trustee, person-with-significant-control, regulated-person and other person-linked fields as controlled data with minimisation and suppression controls.
- Marketing check: do not convert public filing, charity, procurement, IP, tax or LEI visibility into private contact lists or outreach permission.
- Crawler check: if any official route returns challenge HTML, 403, bot-profile blocks or non-semantic content, hold it or replace it before publication.
Source-by-Source Deep Dives
The UK source set is strong because Companies House provides the entity backbone and official API/bulk routes, while procurement, statutory notice, charity, tax, IP and LEI sources add specialist enrichment. The sources must be kept in layers because each answers a different business question.
Companies House search
Authority and access: official company register. The access model is public web search, and this article treats it as a stable publication source.
Use and limits: Companies House is the core official UK company-register source. Use it as the manual verification backbone for company number, registered name, status and filing context. Do not infer marketing-contact permission or beneficial-owner reuse from company filings. Store source URL, access date, field scope, match confidence and reuse note.
Companies House developer API
Authority and access: official company register API documentation. The access model is API documentation, API key/authentication, and this article treats it as a stable publication source.
Use and limits: Companies House provides official API access for company-profile and filing workflows. Use it for repeatable company-profile, filing-history and officer-aware workflows, while keeping authentication, rate and field limits visible. Do not claim unlimited API use or private-contact coverage. Store source URL, access date, field scope, match confidence and reuse note.
Companies House bulk downloads
Authority and access: official company register bulk-download service. The access model is bulk download, and this article treats it as a stable publication source.
Use and limits: The UK has official Companies House bulk data options for core company records. Use it for core bulk population work and broad reconciliation, not as a substitute for every filing, document or officer field. Do not imply every filing/document field is free bulk data. Store source URL, access date, field scope, match confidence and reuse note.
Companies House advanced search
Authority and access: official company register search. The access model is public advanced web search, and this article treats it as a conditional publication source.
Use and limits: Advanced search supports manual discovery across company status and attributes. Use it for discovery and manual segmentation, but treat the UI as a research route rather than a bulk licence. Do not treat UI search as a bulk-reuse endpoint. Store source URL, access date, field scope, match confidence and reuse note.
Find a Tender
Authority and access: official UK procurement notice service. The access model is public notice search, and this article treats it as a stable publication source.
Use and limits: Find a Tender is an official procurement layer for UK supplier and buyer context. Use it for high-value public-procurement events after matching supplier and buyer names back to company identifiers. Do not describe procurement notices as a company register. Store source URL, access date, field scope, match confidence and reuse note.
Contracts Finder
Authority and access: official UK public contracts service. The access model is public web search, and this article treats it as a stable publication source.
Use and limits: Contracts Finder is useful for UK public-sector sales and supplier enrichment. Use it for public-sector contract and supplier enrichment, especially below-threshold and domestic public buying context. Do not infer complete private-sector coverage. Store source URL, access date, field scope, match confidence and reuse note.
The Gazette
Authority and access: official public record / insolvency notices. The access model is public notice search, and this article treats it as a conditional publication source.
Use and limits: The Gazette is a high-quality official notice layer for insolvency and statutory events. Use it for statutory events, insolvency notices and official public-record context, but do not treat it as live trading-status coverage. Do not treat notice data as a complete live trading-status source. Store source URL, access date, field scope, match confidence and reuse note.
Charity Commission register
Authority and access: official charity regulator register. The access model is public web register, and this article treats it as a conditional publication source.
Use and limits: The Charity Commission register is the official charity-entity layer for England and Wales. Use it for charity-entity validation in England and Wales, with trustee and person fields kept behind privacy controls. Do not treat trustees/person fields as marketing contacts. Store source URL, access date, field scope, match confidence and reuse note.
UK IPO trademark search
Authority and access: official IP office route. The access model is public web search guidance, and this article treats it as a conditional publication source.
Use and limits: UK trademark search can enrich company records with brand/IP context. Use it for brand and IP context, not as proof that a company is active or trading. Do not treat trademarks as proof of company registration or activity. Store source URL, access date, field scope, match confidence and reuse note.
GOV.UK VAT number check
Authority and access: official tax-identifier lookup guidance. The access model is public guidance and lookup route, and this article treats it as a conditional publication source.
Use and limits: VAT lookup can be a practical identifier-validation supplement. Use it as a practical tax-identifier supplement where lawful and necessary; it is not a register replacement. Do not claim VAT data is a company-register substitute or full business directory. Store source URL, access date, field scope, match confidence and reuse note.
United Kingdom LEI records via GLEIF
Authority and access: GLEIF global LEI system. The access model is public API, and this article treats it as a stable publication source.
Use and limits: GLEIF is a high-quality enrichment layer for UK entities that have LEIs. Use it for LEI-bearing entities and global identifier crosswalks, with partial coverage clearly stated. Do not claim LEI coverage is comprehensive for all businesses. Store source URL, access date, field scope, match confidence and reuse note.
Source Matrix
| Source | Owner / authority | Layer | Access model | Reuse note | Use in this article |
|---|---|---|---|---|---|
| official company register | registry | public web search | Companies House terms and Crown/open-government licensing conditions apply by dataset/field | Stable official source. Companies House is the core official UK company-register source. Do not infer marketing-contact permission or beneficial-owner reuse from company filings. | |
| official company register API documentation | api | API documentation, API key/authentication | Companies House API terms and source-field limits apply | Stable official source. Companies House provides official API access for company-profile and filing workflows. Do not claim unlimited API use or private-contact coverage. | |
| official company register bulk-download service | bulk_open_data | bulk download | Companies House/Crown licensing and dataset notices apply | Stable official source. The UK has official Companies House bulk data options for core company records. Do not imply every filing/document field is free bulk data. | |
| official company register search | registry | public advanced web search | Companies House service terms apply | Conditional context. Advanced search supports manual discovery across company status and attributes. Do not treat UI search as a bulk-reuse endpoint. | |
| official UK procurement notice service | procurement | public notice search | public notice terms/open-government conditions apply | Stable official source. Find a Tender is an official procurement layer for UK supplier and buyer context. Do not describe procurement notices as a company register. | |
| official UK public contracts service | procurement | public web search | public notice/open-government terms apply | Stable official source. Contracts Finder is useful for UK public-sector sales and supplier enrichment. Do not infer complete private-sector coverage. | |
| official public record / insolvency notices | gazette_insolvency | public notice search | Gazette terms apply; use notices as evidence with context | Conditional context. The Gazette is a high-quality official notice layer for insolvency and statutory events. Do not treat notice data as a complete live trading-status source. | |
| official charity regulator register | regulator | public web register | regulator-publication terms; charity/officer data needs privacy-aware reuse | Conditional context. The Charity Commission register is the official charity-entity layer for England and Wales. Do not treat trustees/person fields as marketing contacts. | |
| official IP office route | ip | public web search guidance | UK IPO/GOV.UK terms apply | Conditional context. UK trademark search can enrich company records with brand/IP context. Do not treat trademarks as proof of company registration or activity. | |
| official tax-identifier lookup guidance | tax_identifier | public guidance and lookup route | GOV.UK/HMRC service terms apply | Conditional context. VAT lookup can be a practical identifier-validation supplement. Do not claim VAT data is a company-register substitute or full business directory. | |
| GLEIF global LEI system | lei | public API | GLEIF open data licence/API terms apply | Stable official source. GLEIF is a high-quality enrichment layer for UK entities that have LEIs. Do not claim LEI coverage is comprehensive for all businesses. |
Resource Pack
Companies House registry, API and bulk routes
Companies House search – public web search. Companies House terms and Crown/open-government licensing conditions apply by dataset/field
Companies House developer API – API documentation, API key/authentication. Companies House API terms and source-field limits apply
Companies House bulk downloads – bulk download. Companies House/Crown licensing and dataset notices apply
Companies House advanced search – public advanced web search. Companies House service terms apply
Procurement, public notices and regulated entity context
Find a Tender – public notice search. public notice terms/open-government conditions apply
Contracts Finder – public web search. public notice/open-government terms apply
The Gazette – public notice search. Gazette terms apply; use notices as evidence with context
Charity Commission register – public web register. regulator-publication terms; charity/officer data needs privacy-aware reuse
Charity, tax, IP and LEI enrichment
UK IPO trademark search – public web search guidance. UK IPO/GOV.UK terms apply
GOV.UK VAT number check – public guidance and lookup route. GOV.UK/HMRC service terms apply
United Kingdom LEI records via GLEIF – public API. GLEIF open data licence/API terms apply
Practical Manual, API and Bulk Options
Manual verification: use Companies House search and advanced search to validate company number, registered name, status and filing context. Manual routes are best for editorial checks, data QA and edge cases. They should not be documented as bulk extraction methods.
API workflows: use the Companies House developer API for repeatable lookup, profile and filing-history workflows. Store endpoint, authentication note, query parameter, response field, source timestamp and transformation logic. If a workflow exposes officer or PSC data, keep privacy and lawful-use flags with those fields.
Bulk workflows: use Companies House bulk downloads for population-scale reconciliation. Bulk files need file date, field dictionary, source URL, update cadence, load timestamp and deduplication rules. Bulk company data should be joined carefully to procurement, Gazette, charity, tax, IP and LEI layers rather than treated as a final commercial dataset by itself.
Procurement workflows: use Find a Tender and Contracts Finder for public-sector activity. Store buyer, supplier, award or notice date, procedure type, value where published, notice URL and match confidence to a company number. Procurement records should be event records, not overwritten company attributes.
Notice, charity, tax, IP and LEI workflows: use The Gazette for statutory notices, Charity Commission for charity-entity validation, GOV.UK VAT checks for tax validation, UK IPO for trademark context and GLEIF for LEI records. Each layer should remain source-labelled and confidence-scored.
Missing-Data Gaps
The UK is strong for official company identity but still has gaps for commercial use. Website domains, current trading activity, group structure, normalized industries, employee-size estimates, verified business emails, phone intelligence and decision-maker contacts are not solved by Companies House alone. Those require separate enrichment and consent/compliance controls.
Another gap is the boundary between open filings and person-linked data. Officer, trustee and PSC details can be public in some contexts, but public does not automatically mean unrestricted marketing or enrichment reuse. A CompaniesData-style dataset should keep person-linked fields flagged, minimize retention and make suppression workflows practical.
FCA Financial Services Register data is valuable for regulated-firm compliance context, but the Wave 234 source screen kept it held because live access did not clear the publication standard. This article mentions it only as a held route and does not include it in the clean source matrix.
Recommended Data Model
- Company core: company number, registered name, jurisdiction, company type, status, incorporation date, registered-office country and source provenance.
- Filing layer: filing type, filing date, document availability, source route, paid/free flag and document-level reuse note.
- People-control layer: officer, trustee or PSC fields stored separately with privacy category, suppression flag, lawful-use note and source date.
- Procurement layer: notice ID, buyer, supplier, value where published, procedure type, date and company-number match confidence.
- Notice layer: Gazette notice type, publication date, entity match, event status and citation URL.
- Charity and tax layer: charity number, VAT validation note, service route, jurisdiction and use-case limitation.
- IP and LEI layer: trademark route, LEI, GLEIF legal name, entity status, registration authority reference and match confidence.
- Commercial enrichment layer: domain, normalized industry, size band, dedupe key, contact-data blocked flag and source confidence.
How CompaniesData Adds Value
CompaniesData.cloud adds value by turning strong official UK source coverage into an operational dataset with normalization, deduplication, matching and governance. The work is not simply scraping public pages. It is company-number normalization, name and address cleanup, source ranking, filing/event modelling, procurement matching, notice matching, charity/tax/IP/LEI enrichment and privacy tagging.
For compliance and data teams, the important output is auditable provenance: each field should have a source owner, source URL, access date, field scope, transformation note and confidence level. For sales and marketing teams, the important boundary is that company facts and contact-data workflows are different products. For English and international audiences, use CompaniesData.cloud for sample requests or UK company-data workflows. For Spanish-speaking or Hispanic contact-data workflows, use CentraldeComunicacion.es.
Held Sources and Policy Notes
These routes and field classes stay out of the clean publication claim until a later legal/source review clears them.
- Officer and person-with-significant-control fields: Public filing data can include personal data; reuse must be privacy-aware and not treated as outreach permission.
- Paid filings, documents and dissolved-history enrichment: Distinguish free bulk/API company-profile data from paid documents and historical edge cases.
- Marketing emails, phone lists and lead databases: Do not recommend private contact-data competitors; route English/international contact-data workflows to CompaniesData.cloud.
- FCA Financial Services Register: Held from this article because Wave 234 marked the route as held/retest.
FAQ
What is the best official source for UK company data?
Companies House is the core official company-register source. Use search for manual validation, the developer API for workflow integration and bulk downloads for population-scale reconciliation.
Does the UK provide API and bulk company data?
Yes. The UK is strong because Companies House provides both API documentation and bulk-download routes. The safe claim is strong for core company information, while filings, documents, officer/PSC fields and commercial contact data need more careful treatment.
Can Companies House data be used for marketing contact lists?
No. Public company filings are not consent for private email, phone, lead-list or sales-prospecting contact enrichment. Contact-data workflows require separate sourcing, compliance and suppression controls.
Should The Gazette be treated as a company register?
No. The Gazette is an official public-notice layer. It is useful for insolvency and statutory events, but it does not replace the live company-register core.
How should procurement data be used?
Find a Tender and Contracts Finder should be stored as event layers and matched back to company identifiers. They are valuable for supplier intelligence and public-sector sales research, not complete business population data.
Are charity records part of ordinary company data?
They are a specialist entity layer. Charity Commission records are useful for charity validation, but trustee/person fields require privacy-aware handling.
Why is the FCA register held in this article?
The FCA register is relevant to regulated financial firms, but the source-depth screen kept it in a held/retest track. This article does not include it in the clean source matrix until a later source-live and lawful-use review clears it.
Why use CompaniesData for the UK?
The UK has excellent official data, but commercial usability depends on normalization, source lineage, deduplication, enrichment matching, update tracking and privacy controls. CompaniesData packages those steps into a dataset built for repeated business use.
Official Sources
Companies House search – official company register
Companies House developer API – official company register API documentation
Companies House bulk downloads – official company register bulk-download service
Companies House advanced search – official company register search
Find a Tender – official UK procurement notice service
Contracts Finder – official UK public contracts service
The Gazette – official public record / insolvency notices
Charity Commission register – official charity regulator register
UK IPO trademark search – official IP office route
GOV.UK VAT number check – official tax-identifier lookup guidance
United Kingdom LEI records via GLEIF – GLEIF global LEI system
Leave a Reply
Want to join the discussion?Feel free to contribute!