Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.kyckr.com/llms.txt

Use this file to discover all available pages before exploring further.

The Kyckr API provides access to legally authoritative company data and filings through a single platform, connecting to a live network of over 300 corporate registries across 120 countries. It retrieves information in real-time or near real-time at the point of request, with data sourced from official, primary government sources. Unlike other providers, the Kyckr API offers both machine-readable data (available as JSON/XML in a normalized structure) and over a thousand different types of original registry documents (PDF). Using the Kyckr API removes the need to build and maintain multiple API connections with hard-to-reach government departments, saving thousands of hours otherwise spent on contracting conversations, authentication procedures, and API/RPA maintenance. With over 15 years of experience building our network, Kyckr continues to improve and expand its connections, earning trust as data specialists who help navigate the complexities of corporate registry data.

​
Use cases

​
Know your business (KYB)

The primary use case for Kyckr’s API is to improve the efficiency and compliance of ‘Know Your Business’ (KYB) processes; the identification and verification of customer information by regulated entities as required under relevant anti-money laundering (AML) legislation. Kyckr provides data to verify both company information and representatives, including directors, company officials and shareholders - this is available both as machine-readable data and contained within original registry documents. The Kyckr Company API is frequently integrated into both proprietary know your company (KYC) orchestration systems, in addition to third-party onboarding or customer lifecycle management platforms (CLM).

​
Entity verification during onboarding

Our data is also used to verify basic company details at the point of onboarding, to ensure potential counterparties are legally registered entities. For example, a major payments company uses Kyckr data to ensure potential customers pass a first-line compliance check: if the data the customer supplies (which includes their name and address) does not match information found at a national corporate registry, their application is rejected. This use case employs the Kyckr API’s ‘search’ and ‘lite profile’ endpoints.