Retrieve Ultimate Parent

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

Resolves the ultimate parent of a company by its Veridion ID.

Run in Postman



When to use it

To find the group behind a company. A veridion_id from a match, a search, or a location lookup identifies one company. This endpoint tells you which group that company belongs to, so spend, exposure, and risk can be assessed against the group rather than against each company on its own.

To establish whether two companies belong to the same group. Two records with different names, domains, and countries can be branches of one group, and nothing in the companies themselves reveals it. A shared result.ultimate_parent_veridion_id does.

To reach the parent's own profile. The response identifies the parent rather than describing it. result.ultimate_parent_veridion_id is the identifier you pass to the Firmographics API for the parent's financials, industry, and size.

What you get

The supplied ID is resolved to the company it identifies, then that company is returned together with the top of its ownership chain.

A response is split in two:

  • the company you asked about, at the top level, in veridion_id and company_name;
  • the result, under result, identifying the ultimate parent by Veridion ID, name, website domain, and jurisdiction.

The parent is identified, not profiled. For the parent's full firmographic record, pass result.ultimate_parent_veridion_id to the Firmographics API.

📖

What counts as a parent

Which company is returned, and why an affiliate or a minority holder is never a parent, are covered in the How the Ultimate Parent API works section.

Where a Veridion ID comes from

IDs come from the Match & Enrich API, the Search API, the Location Intelligence API, and any other Veridion product that references companies by ID.

The format is a 16 character alphanumeric ID, such as RNXRFUASQL77R3MG;

Already the ultimate parent

When the company you asked about is the top of its own chain, result.ultimate_parent_veridion_id equals veridion_id, and the rest of result describes that same company.

This is a resolved answer, not a failure to find one, and it is always reported this way. So a single comparison is all a client needs, with no null handling: every company resolves to a group, and an independent company is a group of one.

Successful response

A successful request returns 200 OK with the resolution object, returned directly rather than wrapped in an envelope.

📖

Response fields

For a comprehensive list of all data points returned on a resolution, see the Response fields and types page.

Error responses

  • 400 Bad Request, if veridion_id fails the format check
  • 404 Not Found, if veridion_id is well formed but does not resolve to a Veridion company
  • other standard HTTP error responses, detailed in the Response codes section.

Any error response follows a specific structure. Please see the Error response format section for more details.

📘

A 404 is not a company without a parent

404 means the ID could not be resolved to a company.

It is not how a company with no owner is reported. A company at the top of its own chain resolves successfully, with 200 OK, and is returned as its own ultimate parent.

Path Params
string
required

A veridion_id from a match, a search, or a location lookup, which identifies one company.

Headers
string
required

Your individual OAuth Bearer token (e.g. Authorization: Bearer <your_access_token>).

Response

Language
LoadingLoading…
Response
Choose an example:
application/json