What is a company directors check?
A company directors check identifies the individuals recorded as directors of a company on a trusted corporate data source. A company details check tells you the entity exists. A directors check tells you who is answerable for it.
Each director in India carries a director identification number, or DIN, which stays with the individual across companies. So a directorship reads in both directions: from a company to its people, and from a person to the companies they are linked to.
How the Company Directors API returns a board list
The API returns the directors linked to a company record in a structured response. You can pull the list when you need it, and pull it again when the relationship comes up for review.
Onboarding, credit and procurement teams need that list at the point where a mandate, a guarantee or an agreement is being prepared. Looked up by hand, it arrives late and rarely gets refreshed. Boards change, and the case file does not.
Why a director list is pulled by CIN
The request starts from the company identifier instead of the company name. Boards are recorded against the registered entity, and a group can run several entities under near-identical names. A name-led search can hand you the directors of a sibling company instead of the one you are contracting with.
What Basic and Advanced add to a director list
The list comes at two levels. Basic returns the list itself: the directors linked to the record, with the identifying information available for each.
Advanced stays with that list and says more about each directorship. Where the record holds them, you get the role recorded against an individual, the dates around the appointment, and whether the directorship still stands. The level you can call depends on the selected service contract, and what comes back varies by data source and by the record.
| Information | Basic | Advanced |
|---|---|---|
| Directors linked to the company record | Yes | Yes |
| Identifying information for each director | Yes | Yes |
| Role recorded against an individual | No | Where recorded |
| Dates around the appointment | No | Where recorded |
| Whether the directorship still stands | No | Where recorded |
Who needs a director list, and when
The list matters most where an obligation attaches to named people. Lending and NBFC teams pull it before facility documents are drawn, because a guarantee or a mandate has to be signed by someone the register recognizes. Corporate banking uses it for authorized-signatory review.
Insurance underwriters use it to build the schedule of directors a commercial or liability cover is written against. Marketplaces, staffing firms and procurement teams use it to surface the control persons and related parties standing behind a seller, vendor or supplier entity. They run it before an account is approved or an award is made.
What to compare a director list against
A list becomes a control only when you compare it with something. Decide before you integrate which match runs automatically, which goes to a reviewer, and what happens when an expected name is missing from the record.
Where the director list fits in onboarding and review
Call the check next to a company details request in the same onboarding step. An analyst then sees the entity and the people together instead of in two systems. It also suits a periodic review job that refreshes the list across a book of existing customers.
Directorships change between reviews. A stored list is a point-in-time observation. Re-check as often as your policy says, and keep the earlier response if you need to show what the record said when a decision was made.
Consent rules when you pull a director list
A directors check looks at identified people as well as at a company. Run it for a legitimate business purpose tied to a relationship you hold or are entering into. Keep it inside the authorized use your service contract sets out, and give the individuals concerned the notice your privacy policy and applicable law require.
Handle the response under your normal controls for personal information: least-privilege access, a defined retention period, and a record of why the check was run.
Availability depends on the data source and the record. A returned name supports a decision; it does not settle one.