Company API

Many businesses and organizations face issues with company onboarding processes as they require a lot of effort and pose significant barriers to implementing truly digital solutions.

Company API is designed with flexibility in mind to provide information on the onboarded company relative to a specific use case in a structured format. The information is retrieved using multiple data sources (such as countries registries (where available),regional data sources (that provide access to registries data through API for the countries where API is not available). Information available on the company is split into Data Groups each one of them has a specific use case it is applicable to.

Currently following Data Groups are available:

  • Basic. Allows to check company status (Active / Inactive / Unknown) and sub-status (e.g. In process of liquidation).

  • Contact. Provides information on Addresses, phone numbers, website, email of the company.

  • Business Activity. Provides information on general company details (legal form, legal name), company ids (VAT number, LEI, TIN), Industry and activities of the company, company Managers.

  • Ownership. Provides information on Shareholders of the company.

  • Ownership extended. Provides information on UBOs of the company

  • Screening. Provides information on screening results for the company.


  1. If startSession query string is defined and it is true the company API will return a session id and create a record in the cache valid for two weeks. TBD if the session id is returned in a response header or as part of the body response.

  2. If UQ-Session-ID is passed the API will check if an existing record in the cache exists (session id + client id). If the record doesnโ€™t exist a 400 status code is returned with a specific error message accordingly. If the record exists and the searchSummary doesnโ€™t match, again an error is returned. Otherwise the content is merged and the cache refreshed. Note: if startSession above is passed to the API with value true this header is ignored.

You can find the full YAML swagger specification here

You can find the full JSON swagger specification here

Last updated