Business Registry Verification - Pro

Performs an enhanced business verification and returns detailed company
information, including associated shareholders and officers. In addition to
standard company data, this endpoint provides detailed shareholders and officer
profiles that help assess company structure and management.

registrationInfos is a list with one entry per company covered by the check. Without
ownership traversal it holds a single entry — the subject company. Each entry carries
its own layer, parentNode, mode (the LIVE or CACHE source that actually
answered for that company) and verifyResult.

layerCalls reports how many billable registry vendor calls the check consumed, split
into live and cache. It is null while status is IN_PROGRESS.

Ownership traversal

By default the response covers the subject company and its own register only.
Set maxLayer (2-10, default 2) to walk further up the ownership chain:
every corporate shareholder on a register is looked up in turn, layer by layer,
until maxLayer is reached. maxLayer counts the subject company as layer 1,
so maxLayer: 3 returns the subject, its register, and the registers of its
corporate shareholders.

Traversal runs only when mode is HYBRID, because each layer is resolved
cache-first. With LIVE or CACHE the value is accepted but no traversal is
performed.

A traversed result differs from a single-layer one in four ways:

  • registrationInfos gains one entry per traversed company — the subject at layer
    1, each corporate shareholder at its own depth, with parentNode pointing at the
    registration number of the company that holds it.
  • officersInfos / shareholdersInfos hold the flattened registers of every
    traversed company. Each entry carries layer and parentNode (the
    registration number of the company whose register it came from), which
    together rebuild the tree. Entries read from a company at layer N are tagged
    layer N + 1.
  • boInfos are the individuals whose ownership, multiplied along each chain and
    summed across chains, reaches 25% or more.
  • Traversal is asynchronous. The create call usually returns status
    IN_PROGRESS with no result payload — poll
    GET /v1/business/checks/{id} until status is COMPLETED. layerCalls then
    covers every company the traversal touched, not just the subject.

A branch stops early when the corporate shareholder holds less than 25%, is
registered outside the subject company's country, has incomplete registry data,
or has already been visited on the same path.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Request body of POST /v1/business/enhanced_checks. Same fields as
BusinessCheckRequest, plus the optional ownership traversal depth maxLayer.

string
required

The name of the company to be checked.

string
required

The country of the company. Accepts country full name, ISO 3166-1 alpha-2,
or alpha-3 code (alpha-3 recommended). For US entities, the state code
(e.g. US-DE) is mandatory in LIVE mode and preferred otherwise.
Example formats: Singapore, SG, SGP, US-NY.

string
required

The registration number of the company.

string
enum
required

Mode of the business verification call.

  • LIVE: retrieves the latest records directly from primary official sources.
  • CACHE: leverages global databases for maximized search depth and global reach.
  • HYBRID: hybrid mode that queries cached sources first and falls back to live
    official sources when no match is found. The exact fallback order depends on the
    company's country.
Allowed:
integer
2 to 10
Defaults to 2

Deepest ownership layer to return, counting the subject company as layer 1.
Optional — omit it to keep the single-layer behaviour.

  • 2 (default) — the subject company and its own register only.
  • 3-10 — ownership traversal: every corporate shareholder on a register is
    looked up in turn, layer by layer, until maxLayer is reached. Each returned
    officer / shareholder carries layer and parentNode.

Traversal runs only when mode is HYBRID; with LIVE or CACHE the value is
accepted but no traversal is performed. Values outside 2-10 return 400.

Headers
string

Unique request identifier. Injected by the API gateway if not provided by the client.
The same value is available in the response body requestId field for business-layer tracing.

string

Distributed tracing identifier. Injected by the API gateway if not provided by the client.
Used for cross-service request correlation in logs and monitoring.

Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json