Skip to content

Company Directors API

New

Pull the directors recorded against a company record, and check signatories, control persons and related parties inside your own onboarding or review workflow.

Overview

A company directors check identifies the individuals recorded as directors of a company on a trusted corporate data source. A company details check shows that an entity exists. A directors check shows who answers for it, meaning the people who sign, guarantee and control it. The Company Directors API returns that list inside your own software. Your application sends the company identifier and gets the directors linked to the record in a structured response. You can compare that list with the people who signed your documents, the names your customer declared and the screening your policy requires. Basic returns the core list, and Advanced adds the wider information held against those directorships. The fields you get back vary by data source and by the individual record. Your selected service contract sets the level you can call.

Coverage
Directors recorded against registered Indian companies
Input
Company identifier (CIN)
Output
The directors linked to that company record, where information is available
Typical users
Lenders and NBFCs, banks, fintech and payment platforms, insurers, marketplaces, procurement and compliance teams
Coverage note
What each record holds differs by data source. Your selected service contract sets the level you can call.

The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.

Endpoint URL and method

POSThttps://gateway.staging.finsour.io/v1/business/company-directors

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Authentication

Scheme API key travels in the X-Api-Key header

Send your API key in this header on every call, from your own server: a key sent from a browser is refused. A key starting fs_test_ calls the sandbox and one starting fs_live_ calls production, at the same address. Create keys in the FinSour console.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Request parameters

Content type application/json

Headers

NameTypeRequiredDescriptionConstraints
Idempotency-KeystringRequiredA key you generate for each attempt. Sending the same key again returns the first answer instead of running the check twice; the same key with a different body is refused.8 to 255 characters. Matches ^[A-Za-z0-9._:-]+$

Body

NameTypeRequiredDescriptionConstraints
inputobjectRequiredThe details to check.—
input.cinstringRequired—Matches ^[LU][0-9]{5}[A-Z]{2}[0-9]{4}[A-Z]{3}[0-9]{6}$
optionsobjectOptionalSettings for this call.—
options.referencestringOptionalYour own reference for this call. It comes back unchanged as meta.reference.1 to 128 characters
options.consentobjectOptionalThe person's consent to this check.—
options.consent.obtainedbooleanRequiredSend true once the person has agreed to the check.Always true
options.consent.atstring (date-time)RequiredWhen the person gave consent.—
options.consent.purposestringRequiredWhat the check is for, for example kyc.1 to 64 characters

Request samples

cURL

curl -X POST https://gateway.staging.finsour.io/v1/business/company-directors \
  -H "X-Api-Key: $FINSOUR_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {
    "cin": "<cin>"
  }
}'

Node.js

const response = await fetch("https://gateway.staging.finsour.io/v1/business/company-directors", {
  method: "POST",
  headers: {
    "X-Api-Key": process.env.FINSOUR_API_KEY,
    "Idempotency-Key": crypto.randomUUID(),
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "input": {
      "cin": "<cin>"
    }
  }),
});

console.log(response.status, await response.json());

Python

import os
import uuid

import requests

response = requests.post(
    "https://gateway.staging.finsour.io/v1/business/company-directors",
    headers={
        "X-Api-Key": os.environ["FINSOUR_API_KEY"],
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "input": {
            "cin": "<cin>",
        },
    },
    timeout=30,
)

print(response.status_code, response.json())

Generated from the fields above. Replace each value in angle brackets with your own; the key is read from FINSOUR_API_KEY.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Response schema

Status 200 · content type application/json

NameTypePresentDescriptionConstraints
dataobjectAlwaysThe result of the check.—
data.foundbooleanAlways——
data.cinstringAlways—Matches ^[LU][0-9]{5}[A-Z]{2}[0-9]{4}[A-Z]{3}[0-9]{6}$
data.directorsarray of objectsAlwaysActive and deactivated directorships alike, each once; read the statuses rather than assuming currency.—
data.directors[].dinstring or any or nullAlways——
data.directors[].namestring or nullAlwaysThe director's full name. Whole here; Finsour keeps only partial letters of it.—
data.directors[].fatherNamestring or nullAlwaysThe director's father's name. Whole here; Finsour keeps only partial letters of it.—
data.directors[].associationStatusstring or nullAlwaysThe registry's word for the director's tie to the company (for example ACTIVE), upper-cased.—
data.directors[].dinStatusstring or nullAlwaysThe registry's status of the DIN (for example APPROVED, DEACTIVATED), upper-cased, as given.—
data.directors[].appointedOnstring or any or nullAlwaysThe day the director was appointed, when the registry gives it.—
data.sourceobjectAlways——
data.source.fetchedAtstringAlwaysWhen the answer was fetched: RFC 3339 UTC with a Z, never an epoch or an IST offset.Matches ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{1,9})?Z$

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Error codes

CodeStatusMeaningRetrying
API_VERSION_UNSUPPORTED400That API version is no longer supported.Do not retry automatically
IDEMPOTENCY_KEY_INVALID400That Idempotency-Key does not meet the required format.Do not retry automatically
IDEMPOTENCY_KEY_REQUIRED400An Idempotency-Key header is required for this request.Do not retry automatically
REQUEST_MALFORMED400The request could not be parsed.Do not retry automatically
AUTH_KEY_EXPIRED401The API key is not valid.Do not retry automatically
AUTH_KEY_INVALID401The API key is not valid.Do not retry automatically
AUTH_KEY_MISSING401No API key was presented.Do not retry automatically
AUTH_KEY_REVOKED401The API key is not valid.Do not retry automatically
INSUFFICIENT_BALANCE402The available balance is not enough for this request.Do not retry automatically
AUTH_IP_NOT_ALLOWED403This API key may not be used from this address.Do not retry automatically
ENTITLEMENT_MISSING403This organization is not entitled to that product in this environment.Do not retry automatically
ORGANIZATION_SUSPENDED403This organization is not active.Do not retry automatically
PRODUCT_NOT_AVAILABLE403That product is not available.Do not retry automatically
PRODUCT_RETIRED403That product has been withdrawn.Do not retry automatically
SCOPE_INSUFFICIENT403This API key does not carry the scope this product requires.Do not retry automatically
PRODUCT_NOT_FOUND404No such product.Do not retry automatically
IDEMPOTENCY_KEY_REUSED409That idempotency key was already used for a different request.Do not retry automatically
PRICE_UNAVAILABLE409No active price covers this product right now.Safe to retry
REQUEST_IN_PROGRESS409An earlier attempt with this key is still running.Safe to retry
SETTLEMENT_PENDING409This request is awaiting reconciliation by an operator.Do not retry automatically
API_VERSION_SUNSET410That API version passed its announced sunset date.Do not retry automatically
REQUEST_TOO_LARGE413The request body is too large.Do not retry automatically
UNSUPPORTED_MEDIA_TYPE415That content type is not accepted on this route.Do not retry automatically
SANDBOX_FIXTURE_MISSING422No sandbox fixture exists for this input. Use a different test value.Do not retry automatically
UPSTREAM_REJECTED422The upstream source rejected the input.Do not retry automatically
VALIDATION_FAILED422The request payload is invalid.Do not retry automatically
CONCURRENCY_LIMIT429Too many simultaneous requests.Safe to retry
QUOTA_EXCEEDED429The allowance for this window is spent.Do not retry automatically
RATE_LIMITED429Too many requests.Safe to retry
INTERNAL_ERROR500An unexpected error occurred.Safe to retry
OUTCOME_UNCERTAIN502The outcome of this request is not yet known. Retry with the same Idempotency-Key.Do not retry automatically
UPSTREAM_UNAVAILABLE502The upstream source is unavailable. Retry shortly.Safe to retry
MAINTENANCE_MODE503The service is in a maintenance window.Safe to retry
NO_PROVIDER_AVAILABLE503No provider can serve this product right now.Safe to retry
SERVICE_OVERLOADED503The service is shedding load. Retry shortly.Safe to retry
UPSTREAM_TIMEOUT504The upstream source did not respond in time.Safe to retry

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Rate limits

ScopeLimitWindowAt the limit
Your API key, within your organisation's limitThe figure in X-RateLimit-LimitPer minute429 RATE_LIMITED, with Retry-After in seconds. Every answer past authentication carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Use cases

  • Lending and NBFC: identify signatories and guarantors before documents
  • Fintech and PSP: control-person checks in corporate merchant onboarding
  • Corporate banking: authorized-signatory and mandate review on entity accounts
  • Insurance: director schedules for commercial and liability underwriting
  • Marketplaces: control-person checks on high-value seller accounts
  • Procurement: related-party screening across the supplier master

What this service does

  • What a director list gives you

    The directors linked to the company record, with the identifying information available for each. At the Advanced level you also get the role recorded against an individual, appointment-related dates and status information for the directorship, where the record holds them. The exact fields vary by data source and by the individual record.

  • Names now, directorship detail when you need it

    Basic returns the core list of directors linked to a record. Advanced adds the wider information held against those directorships. Your selected service contract sets the level you can call.

  • A list your rules engine can match

    A structured list can be matched automatically against the people who signed your documents, the names the customer declared and the screening lists your policy requires. An analyst no longer reads it once and files it.

  • Same check at onboarding and at review

    One check serves the first review of a counterparty and every refresh after it. Boards change between reviews. A list pulled at onboarding shows the record on that day.

How a check runs

  1. Start with the company's CIN

    Take the corporate identity number for the entity from your onboarding form or existing entity record. If you hold only a company PAN, run a PAN to CIN lookup to get the identifier first.

  2. Choose a level and send the request

    Your application sends the identifier through the API, along with the level of information the review needs.

  3. The service pulls the linked directors

    The service processes your request against a trusted corporate data source and assembles the directors available for that company record.

  4. Take in the director list

    Your application receives the available director information in a structured response it can store, display or pass to a screening step.

  5. Match the names and flag the gaps

    Compare the returned names with your signatories, declared control persons and screening lists. Send anything unexpected to a reviewer under your own policy.

Questions

What do I send to get a company's director list?
Send the company identifier, the corporate identity number for the entity. A name search returns candidates because company names repeat and change, while an identifier returns a record. If you hold only a company PAN, run a PAN to CIN lookup to get the identifier first.
What director information comes back?
The directors linked to the company record, with the identifying information available for each. The Advanced level adds the wider information held against those directorships, which can include the role recorded against an individual, appointment-related dates and status information. The exact fields vary by data source and by the individual record.
What does Advanced add to a director list?
Basic returns the core list of directors linked to the record. Advanced adds the wider information held against those directorships, for teams that need more than the names. Your selected service contract sets the level you can call.
Do I need consent to look up a company's directors?
Treat a directors check as a check on personal information as well as a corporate one, because it returns information about identified individuals. Run it for a legitimate business purpose tied to a relationship you hold or are entering into. Keep it within the authorized use described in your service contract, and give the notice your privacy policy and applicable law require.
Why does the register list directors we never deal with?
Directors on the register are not always the people who negotiate or run things day to day, and boards change between one review and the next. A returned list is a point-in-time observation of the record. Treat a difference as something to review.
How do I get access to the Company Directors API?
Choose Get API on this page. Our team takes you through onboarding, the service contract and the technical documentation for the integration.

Catalog entry last updated .