Skip to content

Director Details API

New

Look up the information held against an individual director identifier, including the companies linked to that person, for enhanced due diligence and periodic review.

Overview

A director details check looks up the information held against an individual director identifier on a trusted corporate data source, including the companies that person is linked to. It reads the corporate register from the person's side. The Director Details API brings that view into your own software. Your application sends the director identifier and gets the available information in a structured response. A credit, risk or compliance team can then see a person's wider corporate footprint without assembling it by hand. Basic returns the core information and the linked companies. Advanced adds the wider information held against those links. Available fields vary by data source and by the record. The response concerns an identified individual. Run the check only for a legitimate business purpose and within the authorized use your service contract describes.

Coverage
Director records associated with registered Indian companies
Input
Director identifier (DIN)
Output
Information held against the identifier and the companies linked to it, where available
Typical users
Credit, risk and compliance teams at lenders and NBFCs, fintech and payment platforms, insurers, marketplaces and real estate businesses
Coverage note
Availability of fields depends on the data source and the record. The service contract you select 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/director-profile

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.dinstringRequired—Matches ^[0-9]{8}$
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/director-profile \
  -H "X-Api-Key: $FINSOUR_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {
    "din": "<din>"
  }
}'

Node.js

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

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

Python

import os
import uuid

import requests

response = requests.post(
    "https://gateway.staging.finsour.io/v1/business/director-profile",
    headers={
        "X-Api-Key": os.environ["FINSOUR_API_KEY"],
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "input": {
            "din": "<din>",
        },
    },
    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.dinstringAlways—Matches ^[0-9]{8}$
data.directorobject or any or nullAlways——
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: promoter and guarantor exposure across linked companies
  • Fintech and PSP: control-person screening during merchant due diligence
  • Insurance: director footprint checks in commercial and liability underwriting
  • Marketplaces: repeat-operator checks when a new seller entity appears
  • Real estate: checks on the people behind a developer or project company
  • Staffing and gig platforms: control checks on contracting and vendor entities

What this service does

  • What a DIN lookup returns

    The information held against the individual director identifier, together with the companies linked to it. At the Advanced level you also get the role recorded against each link, appointment-related dates and status information for the directorship, where the record holds them. The fields present vary by data source and by the individual record.

  • Read the register from the person's side

    A company check answers who sits on one board. This answers what else an individual is linked to. That is the question that matters when a team is weighing promoter exposure, related parties or a counterparty that looks newly formed.

  • Screening depth without a second integration

    Basic returns the core information and the linked companies for an identifier. Advanced adds the wider information held against those links. The selected service contract decides which level you can call.

  • Built for enhanced due diligence

    The check suits enhanced due diligence, periodic review and exception handling. You can call it only when a company-level check raises something worth pursuing, which keeps the personal information you hold in proportion to the decision being made.

How a check runs

  1. Find the individual's DIN

    Take the director identification number for the individual. If you do not hold it, a company directors check on an entity you already know can surface the individuals linked to that record.

  2. Record why you are checking

    Write down the legitimate business purpose for the check, and confirm it sits inside the authorized use described in your service contract and your own privacy policy.

  3. Send the DIN with your chosen level

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

  4. Read the links that come back

    Your application receives the available information held against the identifier, including the companies linked to it, in a structured response.

  5. Review before you act on a name

    Use the links as an input to review. Where a result would count against someone, give your team a set way to confirm it and the individual a way to correct it.

Questions

What do I send to look up a director by DIN?
Send the director identification number for the individual. A directorship trail can be followed reliably only from the identifier, because personal names repeat, are transliterated inconsistently and change. If you do not hold the DIN, a company directors check on an entity you already know can surface the individuals linked to that record.
What does a director details response include?
The available information held against the identifier, together with the companies linked to it. The Advanced level adds the wider information held against those links, which can include the role recorded at each company, appointment-related dates and status information. The fields present vary by data source and by the individual record.
Do I need consent to look up a director's other companies?
Consent and authorized use are central to a check that returns information about an identified individual. Run the lookup only for a legitimate business purpose connected to a relationship you hold or are entering into. Keep it within the authorized use described in your service contract, and give the notice and consent your privacy policy and applicable law require.
Can I treat a directorship as a red flag?
Treat it as an input to human review. A link on the list does not show that a person did anything wrong, and two people can share a name without being the same person. A historical directorship can also appear long after it ended, and your team needs a set way to confirm a link before it counts against anyone.
Why does one DIN return more detail than another?
Because records hold different amounts. How long the individual has been linked to companies, how those companies have filed over time and the underlying data source all change what is present. Build your workflow to handle a partial response instead of assuming every field is there.
How do I get access to the Director Details API?
Select Get API on this page. Our team will guide you through onboarding, the service contract and the technical documentation for the integration.

Catalog entry last updated .