COMPANY DATA API

Company data API.
Records you can trace.

A company data API gives your software structured business records through search and lookup requests. CompanyProof connects legal identity, officers, reported ownership and financials in one profile, with source context where returned. Validate the fields available for your markets before integration.

REST + JSON / MCP for AI agents

Translucent company records brought together into one connected profile.
FROM SCATTERED RECORDS

People. Ownership.
Financials. Connected.

N
ONE COMPANY PROFILENorthstar Holdings LtdExplore the connections ↗
01 / THE FULLER PICTURE

THE DATA FOUNDATION

Official-source company intelligence

600M+
company records
400+
official registries
200+
countries & territories

Company data network.
Availability varies by field and market.
Explore coverage ↗

CHOOSE THE RIGHT DATA LAYER

Start with the decision.
Then choose the fields.

Company search finds candidates. A company profile API retrieves records for the selected entity. Neither step, on its own, approves a supplier or verifies every claim about it.

Legal-entity research

Use registration number and country to confirm identity, then inspect status, officers and reported relationships. Keep source details with the fields you store.

Check market and field coverage →

CRM company enrichment

Resolve the account to a legal entity, store its returned ID, then map only the fields your CRM needs. Preserve missing-data states and review ambiguous matches before writing to your CRM. Your application owns the mapping and update workflow.

Inspect the profile contract →

AI company answers

Give your agent the returned records and their source context. For a verdict on a supported company identity claim, use the separate Claim Verification API. Ownership and financial claims need their own assessment.

See supported verification fields →

What your enterprise pilot should prove

Choose representative companies across your required countries and entity types, including similar names, missing financials and restricted modules. Define acceptance thresholds before evaluating providers.

Compare results by country and required field; a global record count is not a field-completion rate.
MeasureKeep the evidenceDecision
Entity resolutionConfirmed registration number and jurisdiction; unresolved and ambiguous cases.Can your workflow select the correct legal entity without a silent name match?
Required-field coverageUsable required fields / requested sample records, split by country and entity type.Does the returned data support your actual decision?
Source and recencyReturned source category, link, retrieval time and filing period, where available.Can a reviewer distinguish registry facts, enrichment and modelled relationships?
Operational behaviourYour measured response times, request credits and module errors on the pilot sample.Do latency, fallback handling and accepted-call usage fit your application?
Permitted useYour order and agreement for storage, retention and onward distribution.Are the rights needed for your product explicitly agreed?

This is an evaluation method, not a measured CompanyProof benchmark. An unavailable ownership module is not evidence that there are no owners. Reported shareholders are not automatically a calculated ultimate beneficial owner.

FROM REQUIREMENT TO RESPONSE

Find the company information
fields you need.

Evaluate a company information API against the fields your application will use—not a promise that every company has every attribute. Start with the response locations below, then inspect the complete contract.

Field map for the CompanyProof profile envelope. Nested facts are optional unless the schema marks them required; module access and source disclosure vary.
Your requirementResponse location & interpretationReference & next check
Legal identityprofile.lite
Keep registration number and jurisdiction together. Use the returned company ID for subsequent profile requests.
Company profile API contract →
Confirm the legal entity before mapping an account.
Directors & officersprofile.officers
Separate current appointments from former roles; preserve source and appointment context.
Officer and company attributes →
Limit personal data to your documented purpose and permitted use.
Ownership & corporate groupsprofile.shareholders
profile.group_structures_full
Reported holdings and returned relationships are not a calculated UBO result.
Ownership API field reference →
How to assess beneficial ownership →
Company financial dataprofile.financial
Match each metric to its reporting period, currency, units and individual or consolidated scope.
Financial API field reference →
Finding private-company statements →
CRM enrichmentenrichment
Check section_status.enrichment separately. Commercial attributes are not automatically registry facts.
Enrichment attribute reference →
Keep availability and provenance alongside each mapped value.
Worked example: enrich without erasing evidence

Illustrative application policy, not a live lookup or a built-in CompanyProof CRM connector. Assume three existing CRM accounts and a workflow that requires a confirmed legal entity before writing company fields.

  1. Confirmed company, empty shareholder collection: retain the confirmed company ID and record “no shareholder records returned.” Do not write “no owners.”
  2. Confirmed company, module access error: a profile can return HTTP 200 while a nested module contains an error. Keep other usable fields, mark that module unavailable and check access; do not overwrite a prior value with a verified absence.
  3. Ambiguous company-name match: hold the update for review. Confirm registration number and jurisdiction before fetching or mapping the selected profile.

Your application defines write, retention and review policies. The profile contract explains arrays, wrappers, nullability and module errors. Use the response-state explorer to compare illustrative available, empty and unavailable states.

Inspect available, empty and unavailable responses

Switch states to see why a missing module must not become a negative finding. Fictional response excerpts; no API request is made.

INSPECT A RESPONSE STATE
ILLUSTRATIVE DATA
REVENUE · FY 2024£28.6m
Origin
Illustrative filed accounts
Reporting period
Year ended 31 Dec 2024
Retrieved
29 Aug 2026 · 10:42 UTC
Currency & scope
GBP millions · individual
01 / READ THE RECORD

The value comes with a story.

A financial figure belongs to a company, a currency and a reporting period.

profile.financialResponse excerpt +
{
  "years": ["2024"],
  "groups": [{
    "name": "Income statement",
    "list": [{ "name": "Revenue",
      "list": { "2024": "28.6" } }]
  }]
}

Keep the original context alongside the value in your application.

02 / FOLLOW THE CONNECTIONS

A company is never
just a name.

Meet the people behind it. Trace its reported ownership. See where it sits in a wider group.

Select a connection below to see the relationship and its context. Fictional company and records.

THE COMPANY, CONNECTEDSELECT A CONNECTION ↗
NNorthstar HoldingsLtd · United Kingdom
+ Alex Morgan · 10% holding
OWNERSHIP ↑↓ CORPORATE GROUP
Corporate shareholderNorthstar Ventures Ltd
United KingdomReported ordinary shareholding
Illustrative filing relationship.
Not a calculated UBO result.

03 / LOOK BEYOND THE HEADLINE

Read the business.
Not just the balance.

Explore reported financials over time, with the period, currency and reporting scope intact. A useful number comes with its context.

NORTHSTAR HOLDINGS LTDILLUSTRATIVE ACCOUNTS
£28.6mFY 2024 · GBP millions
Choose a year to inspect its reporting context ↗
View the illustrative chart data as a table
Fictional Northstar accounts · GBP millions · individual company · periods ended 31 December
YearRevenueOperating profit
202218.42.1
202322.72.8
202428.63.9

These values illustrate reporting context. They are not measured CompanyProof customer results or live filings.

04 / OPEN THE RECORD

Six ways in.
One company ID.

Switch between identity, officers, ownership, group, financials and enrichment. Inspect the example, then see the JSON behind it.

Northstar Holdings LtdUnited Kingdom / DEMO-GB-001
ILLUSTRATIVE PROFILE

THE COMPANY RECORD

ONE COMPANY ID6 connected modules
MODULE 04 / 06

Group structure

4 entities / 3 jurisdictionsSelect a company to inspect

The legal entity stays connected to its wider corporate group.

profile.group_structures_fullFields & availability

Explore returned parent and subsidiary relationships. Connect related companies without losing the identity and jurisdiction of the specific business you are reviewing.

Group entities
id, name, registration_number
Jurisdiction
country
Relationships
children[]
Record context
selected, source

Keep relationship provenance: modelled links and registry-sourced relationships carry different evidence.

Read the complete field reference ↗

Fictional demonstration, not a live lookup. Module and field availability vary by company, market and access.

Evaluate your required fields ↗

FROM REQUEST TO RECORD

Two requests.
A wider view.

Resolve the company once. Retrieve its profile using the same company ID.

  1. 01

    Find the right legal entity

    Search by name or identifier and country. Confirm the match before requesting its profile.

    POST /v2/companies/search
  2. 02

    Bring the record into your product

    Retrieve available modules. Preserve their source details, reporting context and availability.

    GET /v2/companies/{id}/profile
Follow the profile quickstart
Ready to evaluate live records?

Use a live key with a paid plan or an active evaluation. Each accepted search or profile request uses one credit.

Plans and credit usage →Connect through MCP →
SEARCH → COMPANY PROFILEOpenAPI 3.1 ↗
# Run server-side with your live API key.
# 1. Search using the company's registration number.
curl --fail-with-body --request POST \
  'https://companyproof.ai/v2/companies/search' \
  --header "Authorization: Bearer $COMPANYPROOF_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
    "identifier_type": "registration_number",
    "identifier": "09410808",
    "country": "GB"
  }'
 
# 2. Confirm the match, then set the returned ID.
# Replace the placeholder with companies[n].id.
COMPANY_ID='REPLACE_WITH_RETURNED_COMPANY_ID'
 
curl --fail-with-body \
  "https://companyproof.ai/v2/companies/$COMPANY_ID/profile" \
  --header "Authorization: Bearer $COMPANYPROOF_API_KEY"
Bearer authentication · HTTPS

PLAN THE REQUESTS

Estimate company
profile API credits.

Each accepted search or profile request uses one credit. Reusing the confirmed company ID for later profile calls avoids an extra search. Use this calculator to make your request assumptions explicit.

Illustrative inputs, editable by you. Each new company uses one search and one profile call. Each refresh reuses a stored company ID and uses one profile call.

ACCEPTED SEARCH + PROFILE CALLS

2,250 credits / month

Search 1,000
Profile 1,250

1,000 × 2 + 250 × 1 = 2,250 credits. The labelled bars show each operation’s share of the total.

This estimates requests, not price or usable-record coverage. Extra accepted searches, repeated profile calls and retries can add credits. Verification and intelligence have separate rules. An empty search result can still be a successful request.

Compare current plans →Read access and credit rules →

Keep live keys on your server. Inspect section_status for profile and enrichment availability, then inspect errors inside each profile module. Follow error handling and rate-limit guidance before retrying.

TWO CAPABILITIES. ONE COMPANYPROOF.

Get the facts.
Then check the claim.

Retrieval and verification answer different questions. Use either capability on its own, or connect them in one workflow.

COMPANY DATA API

“What do we know
about this company?”

CompanyNorthstar Holdings Ltd
StatusActive
Group3 subsidiaries

Returns a company profile with available records and source context.

YOU’RE HERE · COMPANY DATA
CLAIM VERIFICATION API

“Does this company
claim match the record?”

CLAIM

“Northstar is dissolved.”

CorrectedObserved status: Active

Compares a supported claim with evidence and returns a verdict and correction.

Explore claim verification

Illustrative examples. Automatic claim verdicts cover the six documented company identity fields.

FREQUENTLY ASKED QUESTIONS

A few more details.

What is a company data API?

It gives software programmatic access to structured company information. CompanyProof offers company search and a consolidated profile, plus separate verification and agent interfaces.

Which company information is available?

Profiles can include legal identity, officers, shareholders, group structure, financials and enrichment. Actual modules and fields depend on source availability and access.

Where does the company data come from?

CompanyProof uses company information collected and structured from official registries. Preserve the source context returned for the specific record you use.

Are all fields available in every country?

No. Registry disclosure, source coverage and module access vary. Validate required fields in your target jurisdictions before integration.

Can I retrieve company financial statements?

The financial module can return reported financial metrics and filing periods where available. Keep the currency, units and individual or consolidated scope with each value.

Does the API identify ultimate beneficial owners?

Shareholder and group records can support ownership research. The current profile contract does not itself promise a calculated ultimate beneficial owner result.

How is company data different from claim verification?

A profile returns observed information. Claim verification compares a supported assertion with available evidence and returns a verdict and correction where appropriate.

Can AI agents use the same data?

CompanyProof provides an MCP interface and documented adaptive intelligence routes. Select the interface according to whether you need structured records, research or claim verification.

How should I handle a missing module?

Inspect section_status and any returned access or error details. Keep unavailable information separate from an empty result or a negative finding.

How do I evaluate pricing and usage?

Review the current pricing page and documented credit rules. Test representative profile requests and module combinations before estimating monthly usage.

YOUR MARKETS. YOUR REQUIRED FIELDS.

Build on a
fuller picture.

Bring your target countries, required fields, representative companies and monthly request estimate. We’ll help scope an API evaluation against your acceptance criteria.

Discuss your integration Read the documentation ↗