Company Details API
Popular
Look up the registration record held against a company identifier, then use the name, status, incorporation and office details inside your own onboarding, credit or procurement workflow.
Overview
A company details check confirms what the corporate register holds against an incorporated company. That covers the registered name, the class and category of company, the current status, and the incorporation and registered office details available. If you onboard other businesses, it shows that the counterparty is a real and live legal entity. The Company Details API brings that lookup into your own software. Your application sends the company identifier and gets the available registration information in a structured response your onboarding, credit or procurement workflow can store and act on. Basic covers the core registration information, and Advanced adds the wider filing and status information held on the record. The fields you get back vary by data source and by the individual company record. The level you can call depends on the selected service contract.
- Category
- Corporate Registry Services
- Coverage
- Registered company records across India
- Input
- Company identifier (CIN)
- Output
- The registration record held for that company, where one is available
- Typical users
- Lenders and NBFCs, fintech and payment platforms, insurers, marketplaces, procurement and finance teams
- Coverage note
- Fields vary by data source and by the individual company record. The level you can call depends on the selected service contract.
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
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
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
Headers
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
Idempotency-Key | string | Required | A 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
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
input | object | Required | The details to check. | — |
input. | string | Required | — | Matches ^[LU][0-9]{5}[A-Z]{2}[0-9]{4}[A-Z]{3}[0-9]{6}$ |
options | object | Optional | Settings for this call. | — |
options. | string | Optional | Your own reference for this call. It comes back unchanged as meta.reference. | 1 to 128 characters |
options. | object | Optional | The person's consent to this check. | — |
options. | boolean | Required | Send true once the person has agreed to the check. | Always true |
options. | string (date-time) | Required | When the person gave consent. | — |
options. | string | Required | What 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-profile \
-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-profile", {
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-profile",
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
| Name | Type | Present | Description | Constraints |
|---|---|---|---|---|
data | object | Always | The result of the check. | — |
data. | boolean | Always | — | — |
data. | string | Always | — | Matches ^[LU][0-9]{5}[A-Z]{2}[0-9]{4}[A-Z]{3}[0-9]{6}$ |
data. | object or any or null | Always | — | — |
data. | array of objects | Always | One entry per filing, in the order the registry lists them; empty for a company with none. | — |
data. | string or null | Always | The financial year, YYYY-YYYY (for example 2020-2021). | Matches ^[0-9]{4}-[0-9]{4}$ |
data. | string or any or null | Always | The day the financial year ended. | — |
data. | string or null | Always | What was filed, upper-cased, as given (for example BALANCE SHEET). | — |
data. | string or any or null | Always | Turnover in paise, a decimal string. | — |
data. | string or any or null | Always | Profit in paise, a decimal string; a loss is negative. | — |
data. | object | Always | — | — |
data. | string | Always | When 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
| Code | Status | Meaning | Retrying |
|---|---|---|---|
API_VERSION_UNSUPPORTED | 400 | That API version is no longer supported. | Do not retry automatically |
IDEMPOTENCY_KEY_INVALID | 400 | That Idempotency-Key does not meet the required format. | Do not retry automatically |
IDEMPOTENCY_KEY_REQUIRED | 400 | An Idempotency-Key header is required for this request. | Do not retry automatically |
REQUEST_MALFORMED | 400 | The request could not be parsed. | Do not retry automatically |
AUTH_KEY_EXPIRED | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_INVALID | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_MISSING | 401 | No API key was presented. | Do not retry automatically |
AUTH_KEY_REVOKED | 401 | The API key is not valid. | Do not retry automatically |
INSUFFICIENT_BALANCE | 402 | The available balance is not enough for this request. | Do not retry automatically |
AUTH_IP_NOT_ALLOWED | 403 | This API key may not be used from this address. | Do not retry automatically |
ENTITLEMENT_MISSING | 403 | This organization is not entitled to that product in this environment. | Do not retry automatically |
ORGANIZATION_SUSPENDED | 403 | This organization is not active. | Do not retry automatically |
PRODUCT_NOT_AVAILABLE | 403 | That product is not available. | Do not retry automatically |
PRODUCT_RETIRED | 403 | That product has been withdrawn. | Do not retry automatically |
SCOPE_INSUFFICIENT | 403 | This API key does not carry the scope this product requires. | Do not retry automatically |
PRODUCT_NOT_FOUND | 404 | No such product. | Do not retry automatically |
IDEMPOTENCY_KEY_REUSED | 409 | That idempotency key was already used for a different request. | Do not retry automatically |
PRICE_UNAVAILABLE | 409 | No active price covers this product right now. | Safe to retry |
REQUEST_IN_PROGRESS | 409 | An earlier attempt with this key is still running. | Safe to retry |
SETTLEMENT_PENDING | 409 | This request is awaiting reconciliation by an operator. | Do not retry automatically |
API_VERSION_SUNSET | 410 | That API version passed its announced sunset date. | Do not retry automatically |
REQUEST_TOO_LARGE | 413 | The request body is too large. | Do not retry automatically |
UNSUPPORTED_MEDIA_TYPE | 415 | That content type is not accepted on this route. | Do not retry automatically |
SANDBOX_FIXTURE_MISSING | 422 | No sandbox fixture exists for this input. Use a different test value. | Do not retry automatically |
UPSTREAM_REJECTED | 422 | The upstream source rejected the input. | Do not retry automatically |
VALIDATION_FAILED | 422 | The request payload is invalid. | Do not retry automatically |
CONCURRENCY_LIMIT | 429 | Too many simultaneous requests. | Safe to retry |
QUOTA_EXCEEDED | 429 | The allowance for this window is spent. | Do not retry automatically |
RATE_LIMITED | 429 | Too many requests. | Safe to retry |
INTERNAL_ERROR | 500 | An unexpected error occurred. | Safe to retry |
OUTCOME_UNCERTAIN | 502 | The outcome of this request is not yet known. Retry with the same Idempotency-Key. | Do not retry automatically |
UPSTREAM_UNAVAILABLE | 502 | The upstream source is unavailable. Retry shortly. | Safe to retry |
MAINTENANCE_MODE | 503 | The service is in a maintenance window. | Safe to retry |
NO_PROVIDER_AVAILABLE | 503 | No provider can serve this product right now. | Safe to retry |
SERVICE_OVERLOADED | 503 | The service is shedding load. Retry shortly. | Safe to retry |
UPSTREAM_TIMEOUT | 504 | The 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
| Scope | Limit | Window | At the limit |
|---|---|---|---|
| Your API key, within your organisation's limit | The figure in X-RateLimit-Limit | Per minute | 429 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: borrower entity checks before a facility is sanctioned
- Fintech and PSP: corporate merchant onboarding and periodic review
- Marketplaces: seller entity checks before a storefront goes live
- Insurance: proposer entity checks on commercial and group covers
- Logistics and fleet: transporter and aggregator contracting checks
- Procurement: supplier registration checks before a purchase order
What this service does
Fields you can expect on a company record
Registered company name, class and category of company, current status, incorporation details and registered office details. Advanced also returns capital-related information, filing and annual-return dates, charge entries and associated directorships where the record holds them. The exact fields vary by data source and by the individual company record.
One integration, both detail levels
Basic returns the core registration information for a record. Advanced adds the wider filing and status information held on the same record. One integration covers both, and the level you can call depends on the selected service contract.
The check runs inside onboarding
Connect the check to onboarding forms, internal dashboards, loan origination systems, vendor master records and CRM. You confirm the entity as part of the journey instead of in a separate manual step beside it.
A company record you can query later
You can store a structured response, compare it with what the customer declared, and let review and audit teams query it later. A screenshot or a line in a case note makes that hard.
How a check runs
Get the company's CIN
Take the corporate identity number from the customer, your onboarding form or your existing entity record. If you hold only a company PAN, resolve it to the corporate identifier first.
Send the CIN and pick a level
Your application sends the identifier through the API, along with the level of information the journey needs.
The service reads the register record
The service processes your request against a trusted corporate data source and assembles the registration information available for that record.
Read the structured response
Your application receives the available company information in a structured response it can store, display or pass to a rules engine.
Act on what the record says
Compare the returned information with what the customer declared. Route mismatches, and any status other than active, to review under your own policy.
Questions
- What do I send to check company details?
- Send the company identifier, the corporate identity number assigned to the company at incorporation. The identifier works better than the company name because names repeat across states and change over time. A name search returns candidates, while an identifier returns a record.
- What company information comes back?
- The registration information held against the record, which can include the registered name, class and category of company, current status, incorporation details and registered office details. The Advanced level adds the wider filing and status information held on the same record. The exact fields vary by data source and by the individual company record.
- What is the difference between Basic and Advanced company details?
- Basic returns the core registration information, which is usually enough to confirm that an entity exists and is active. Advanced adds the wider filing and status information held on the record, for teams doing deeper diligence. The level you can call depends on the selected service contract.
- Do I need the company's consent to run this check?
- Run the check only for a legitimate business purpose tied to a relationship you hold or are entering into. Stay within the authorized use described in your service contract, and give the notice your privacy policy and applicable law require. Handle the response under your usual data-protection, retention and access controls, because company records carry information about named individuals.
- Why do two companies return different fields?
- Because the response shows what each record actually holds. Older records, dormant entities and companies at different filing stages do not all carry the same information, and availability depends on the underlying data source. Build for a partial response instead of assuming every field is there.
- How do I get access to the Company Details API?
- Use Get API on this page. Our team will take you through onboarding, the service contract and the technical documentation for the integration.
Catalog entry last updated .