MCA APIs
MCA APIs help you work with company records sourced from India’s Ministry of Corporate Affairs (MCA). Use them when you already know the company’s CIN or LLPIN and need its master data, or when you first need to search for the right company before proceeding with an exact lookup.The active MCA endpoints documented here are Company Master Data and Search Company.
Exact company lookup
Fetch company master data using a Corporate Identification Number (CIN) or Limited Liability Partnership Identification Number (LLPIN).
Search before lookup
Search the Sandbox database using exact
cin or partial company_name when you do not yet have the final identifier.KYB and onboarding
Use MCA company records in vendor onboarding, business verification, and corporate due diligence workflows.
Source-aware retrieval
The company master data flow supports primary and secondary source selection, along with cache-aware behavior.
How it works
1
Collect the company input
Start with either a
cin/llpin or a company name, depending on what your workflow already knows.2
Choose the right endpoint
Use Company Master Data for an exact company lookup, or Search Company when you want to find matching companies first.
3
Send the request
Call the MCA endpoint that matches your use case and pass the identifier or search query in the documented request shape.
4
Use the response in your workflow
Prefill forms, validate a business, shortlist matching companies, or continue to downstream KYB checks using the returned data.
What you can do
Fetch company profile details
Retrieve company name, RoC code, category, class, status, registration date, address, and industrial classification.
Lookup using CIN or LLPIN
Use the same
cin field for both company CIN values and LLPIN values in exact company lookups.Search by company name
Search using a partial company name when you need to identify the right company before performing an exact lookup.
Build onboarding flows
Use MCA data for business verification, merchant onboarding, vendor checks, and internal review workflows.
Source routing and cache behavior
x-source applies to the Company Master Data API. Search Company does not use x-source.POST /kyc/mca/company/master-data, the response behavior depends on two optional headers:
x-sourcex-accept-cache
How x-source behaves
x-source: primaryreturns the response from the primary sourcex-source: secondaryreturns the response from the secondary source- if
x-sourceis omitted, the API first tries the primary source and can fall back to the secondary source when needed
How x-accept-cache behaves
x-accept-cache: trueallows the API to reuse and populate cache- if
x-accept-cacheis nottrue, the request is treated as cache bypass
- use
x-source: primarywhen you want a vendor-only read - use
x-source: secondarywhen you want a secondary-source read - omit
x-sourcewhen you want primary-first behavior with fallback to secondary - use
x-accept-cache: truewhen you are okay with cached responses being reused
x-source: primaryandx-source: secondaryare cached separately from one another- when
x-sourceis omitted and caching is allowed, the API uses a different default cache behavior - in that default mode, a later cached response may reflect either the primary source or the secondary source, depending on which one created the cache entry
Integration methods
Company Master Data API
POST endpoint for exact company lookup using
cin, where cin can contain either a CIN or an LLPIN.Search Company API
GET endpoint for searching the Sandbox database using exact
cin or partial company_name, with optional limit and offset.Director Master Data API (Discontinued)
Older MCA director endpoint retained in docs for reference. It is no longer active for new integration work.
Common use cases
Use MCA APIs when you need to:- Fetch master data for a known company using CIN or LLPIN
- Search for companies by name before proceeding with an exact lookup
- Perform KYB during business onboarding
- Validate merchants, vendors, partners, and suppliers
- Replace manual MCA portal checks with an API-first workflow
Frequently Asked Questions
What is the difference between Company Master Data and Search Company?
What is the difference between Company Master Data and Search Company?
Company Master Data is for exact lookup when you already know the company’s CIN or LLPIN. Search Company is for finding matching companies first using exact
cin or partial company_name.Can I pass LLPIN in the cin field?
Can I pass LLPIN in the cin field?
Yes. For the Company Master Data API, the
cin field can carry either a Corporate Identification Number (CIN) or a Limited Liability Partnership Identification Number (LLPIN).Can I search by company name?
Can I search by company name?
Yes. Use the Search Company API and pass a partial
company_name. The endpoint also supports exact cin search.What does the Search Company API return?
What does the Search Company API return?
Search Company is intended for shortlist and discovery workflows. It returns lightweight company search results that help you identify the correct company before making an exact lookup.
How do x-source and x-accept-cache work?
How do x-source and x-accept-cache work?
For Company Master Data,
x-source controls which source serves the request. primary means the primary source, secondary means the secondary source, and omitting it gives you primary-first behavior with fallback to secondary when needed. If caching is allowed, primary-pinned and secondary-pinned requests are cached separately, while requests without x-source use a separate default cache behavior.Is Director Master Data still available?
Is Director Master Data still available?
No. The Director Master Data API has been discontinued and should not be used for new integrations.