The MCA Corporate Verification API is an essential tool for any company looking to onboard merchants or other business partners in India. This API provides a secure and efficient way to verify whether your merchants are registered with the Registrar of Companies (ROC) and have the same details that you expect. By accessing the MCA Corporate Verification API, businesses can ensure that their onboarding process is safer, faster, and smarter.
With the MCA Corporate Verification API, businesses can access the ROC database to verify the registration details of their merchants. This includes information such as the company name, registration number, address, and other key details. This information can be used to ensure that the merchants you are onboarding are legitimate and have the correct registration details.
In addition to its verification capabilities, the MCA Corporate Verification API is also designed to be highly reliable and easy to use. The API is built on a modern, RESTful architecture, which makes it easy for developers to integrate into their applications. The API also includes comprehensive documentation and technical support, making it easy for businesses to get started and build high-quality onboarding applications.
Overall, the MCA Corporate Verification API is an essential tool for any business looking to onboard merchants or other business partners in India. By verifying the registration details of your merchants, you can ensure that your onboarding process is safer, faster, and smarter, while also protecting your business from potential fraud or other risks.
Pass the CIN code and receive information about the company.
Merchant onboarding: The MCA Corporate Verification API can be used to verify the registration details of merchants during the onboarding process. This helps to ensure that the merchants are legitimate and have the correct registration details.
Risk management: Businesses can use the MCA Corporate Verification API to manage the risk of fraud or other illegal activities by verifying the registration details of potential partners. This can help to protect the business from potential financial and legal risks.
Compliance: The MCA Corporate Verification API can help businesses comply with regulatory requirements by verifying the registration details of their partners. This includes requirements related to KYC (know your customer) and AML (anti-money laundering).
Due diligence: The MCA Corporate Verification API can be used as part of the due diligence process for mergers and acquisitions or other business transactions. This helps to ensure that the businesses being acquired have the correct registration details and are legitimate.
Data analysis: Businesses can use the MCA Corporate Verification API to gather data on the number of businesses registered with the Registrar of Companies in India. This can be used for market research, data analysis, or other purposes.
Besides the number of API calls, there is no other limitation.
Make your onboarding process safer, faster, and smarter by verifying if your merchants are registered with the Registrar of Companies, and are registered with the same details that you expect.
With the MCA Verification API, you can now confidently onboard merchants knowing that they are authorized and registered with the RoC.
Use get call on the left and pass the request id to fetch api call results.
Verification - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"request_id":"95d125d5-d2db-4c11-8d94-708803de90f7"}
curl --location --request POST 'https://zylalabs.com/api/1477/mca+corporate+verification+api/1223/verification' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"task_id": "74f4c926-250c-43ca-9c53-453e87ceacd1",
"group_id": "8e16424a-58fc-4ba4-ab20-5bc8e7c3c41e",
"data": {
"cin": "L85110KA1981PLC013115"
}
}'
Used to fetch api result using the request id received in responses.
Get Result - Endpoint Features
| Object | Description |
|---|---|
request_id |
[Required] |
[{"action":"verify_with_source","completed_at":"2026-05-14T18:14:42+05:30","created_at":"2026-05-14T18:14:41+05:30","group_id":"8e16424a-58fc-4ba4-ab20-5bc8e7c3c41e","request_id":"95d125d5-d2db-4c11-8d94-708803de90f7","result":{"source_output":{"authorised_capital":24000000000,"charges":null,"cin":"L85110KA1981PLC013115","class_of_company":"Public","company_category":"Company limited by Shares","company_name":"INFOSYS LIMITED","company_status":"Active","company_subcategory":"Non-govt company","date_of_balance_sheet":"2025-03-31","date_of_incorporation":"1981-07-02","date_of_last_agm":"2025-06-25","directors":[{"begin_date":"2023-01-12","din":"00169343","end_date":null,"name":"GOVIND VAIDIRAM IYER"},{"begin_date":"2014-01-10","din":"00347229","end_date":"2023-03-22","name":"KIRAN MAZUMDAR SHAW"},{"begin_date":"1998-04-10","din":"00306761","end_date":"2011-08-23","name":"MARTI GURUNATH SUBRAHMANYAM"},{"begin_date":"1997-10-10","din":"00009627","end_date":"2013-11-13","name":"DEEPAK MADHAV SATWALEKAR"},{"begin_date":"2014-01-10","din":"06782450","end_date":"2021-12-12","name":"PRAVIN UDHYAVARA BHADYA RAO"},{"begin_date":"2013-04-11","din":"01764813","end_date":"2013-08-14","name":"LEO PURI"},{"begin_date":"2009-05-02","din":"00043501","end_date":"2015-06-05","name":"KUNDAPUR KAMATH"},{"begin_date":"2002-01-10","din":"00041461","end_date":"2014-08-01","name":"SAROJINI DAMODARAN SHIBULAL"},{"begin_date":"2016-01-14","din":"05229262","end_date":"2021-01-13","name":"PUNITA KUMAR SINHA"},{"begin_date":"2011-06-11","din":"02825465","end_date":"2013-12-31","name":"VENKATRAMAN BALAKRISHNAN"},{"begin_date":"2001-03-29","din":"00001835","end_date":"2010-04-13","name":"RAMA BIJAPURKAR"},{"begin_date":"2016-10-14","din":"00504146","end_date":"2020-04-20","name":"DODDABALLAPUR NAGARAJACHAR PRAHLAD"},{"begin_date":"2011-06-11","din":"00517585","end_date":"2014-06-10","name":"BANGALORE GANGAIAH SRINIVAS"},{"begin_date":"2000-05-27","din":"00042167","end_date":"2011-06-11","name":"MOHANDAS TELLICHEERY VENKATARAMAN PAI"},{"begin_date":"2011-01-13","din":"00047985","end_date":"2017-08-24","name":"SESHASAYEE RAMASWAMI"},{"begin_date":"2000-11-13","din":"00004258","end_date":"2014-12-31","name":"OMKAR GOSWAMI ."},{"begin_date":"2006-08-21","din":"00040295","end_date":"2014-06-14","name":"NARAYANA MURTHY"},{"begin_date":"2011-08-21","din":"00041656","end_date":"2014-10-10","name":"SENAPATHY GOPALAKRISHNAN"},{"begin_date":"2000-05-27","din":"00041394","end_date":"2014-08-01","name":"SRINATH BATNI"},{"begin_date":"2015-02-04","din":"00001766","end_date":"2020-02-03","name":"ROOPA KUDVA"},{"begin_date":"2003-04-10","din":"00278512","end_date":"2012-08-13","name":"SRIDAR ARVAMUDHAN IYENGAR"},{"begin_date":"2011-04-15","din":"00621398","end_date":"2018-05-11","name":"RAVI VENKATESAN"},{"begin_date":"2002-05-01","din":"00041553","end_date":"2011-06-11","name":"DINESH KRISHNA SWAMY"},{"begin_date":"2005-07-12","din":"00301797","end_date":"2014-01-17","name":"DAVID L BOYLES"},{"begin_date":"2006-04-14","din":"00092981","end_date":"2017-08-24","name":"JEFFREY SEAN LEHMAN"},{"begin_date":"2011-10-01","din":"03617989","end_date":"2014-06-14","name":"ANN MARIE FUDGE"},{"begin_date":"2011-06-11","din":"03545559","end_date":"2013-09-12","name":"ASHOK VEMURI"},{"begin_date":"2014-04-29","din":"06858688","end_date":"2015-11-23","name":"CAROL MARTHA BROWNER"},{"begin_date":"2014-06-14","din":"06897177","end_date":"2017-08-24","name":"VISHAL INDER SIKKA"},{"begin_date":"2014-12-04","din":"07029756","end_date":"2017-08-24","name":"JOHN WILLIAM ETCHEMENDY"},{"begin_date":"2020-04-20","din":"08733837","end_date":"2023-04-19","name":"URI LEVINE"},{"begin_date":null,"din":null,"end_date":null,"name":"SALIL SATISH PAREKH"},{"begin_date":null,"din":null,"end_date":null,"name":"SURYANARAYANA ANUR GURUGOPALA RAJU MANIKANTHA"},{"begin_date":null,"din":null,"end_date":null,"name":"JAYESH DHANVANTKUMAR SANGHRAJKA"},{"begin_date":null,"din":null,"end_date":"2018-01-02","name":"PRAVIN UDHYAVARA BHADYA RAO"},{"begin_date":null,"din":null,"end_date":"2018-11-16","name":"DWARAKANATH RANGANATH MAVINAKERE"},{"begin_date":null,"din":null,"end_date":"2012-04-13","name":"PARVATHEESAM KANCHINADHAM"},{"begin_date":null,"din":null,"end_date":"2015-10-12","name":"RAJIV BANSAL"},{"begin_date":null,"din":null,"end_date":"2024-03-31","name":"NILANJAN ROY"},{"begin_date":"2023-05-26","din":"10166891","end_date":null,"name":"HELENE MARIE JACQUELINE MADELEINE AURIOL POTIER"},{"begin_date":"2018-01-02","din":"01876159","end_date":null,"name":"SALIL SATISH PAREKH"},{"begin_date":"2020-07-15","din":"00019437","end_date":null,"name":"BOBBY KANUBHAI PARIKH"},{"begin_date":"2021-03-25","din":"09101763","end_date":null,"name":"CHITRA NAYAK"},{"begin_date":"2018-07-13","din":"08177291","end_date":null,"name":"MICHAEL NELSON GIBBS"},{"begin_date":"2017-08-24","din":"00041245","end_date":null,"name":"NANDAN MOHAN NILEKANI"},{"begin_date":"2017-07-14","din":"00016304","end_date":null,"name":"SUNDARAM DAMODARANNAIR"},{"begin_date":"2024-01-01","din":"00045204","end_date":null,"name":"NITIN PARANJPE"},{"begin_date":null,"din":"09299580","end_date":"2019-03-01","name":"JAYESH DHANVANTKUMAR SANGHRAJKA"}],"email_id":"[email protected]","llp_name":null,"llpin":null,"no_of_designated_partners":"","no_of_partners":null,"number_of_members":null,"paid_up_capital":20278116895,"registered_address":"ELECTRONICS CITY,HOSUR ROAD, BANGALORE, KARNATAKA, Karnataka - 560100","registration_number":"","related_companies":null,"roc_code":"","source":"#companyMasterData","status":"id_found","whether_listed_or_not":"Listed"}},"status":"completed","task_id":"74f4c926-250c-43ca-9c53-453e87ceacd1","type":"ind_mca"}]
curl --location --request GET 'https://zylalabs.com/api/1477/mca+corporate+verification+api/1224/get+result?request_id=95d125d5-d2db-4c11-8d94-708803de90f7' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The POST Verification endpoint returns a status indicating whether the provided CIN is valid, along with details such as the action taken, timestamps, and any error messages. The GET Get Result endpoint returns the verification results associated with a specific request ID, including the same fields as the POST response.
Key fields in the response data include "action," "status," "request_id," "completed_at," "created_at," and "error." These fields provide insights into the verification process and any issues encountered.
The response data is structured in JSON format, with each verification result encapsulated in an object. This object contains key-value pairs that detail the verification status and associated metadata.
The POST Verification endpoint provides verification status and error messages, while the GET Get Result endpoint retrieves detailed results of previous verification requests, including timestamps and actions taken.
Data accuracy is maintained by sourcing information directly from the Registrar of Companies (ROC) database, ensuring that the verification process relies on official and up-to-date records.
Typical use cases include merchant onboarding, risk management, compliance checks, due diligence for business transactions, and data analysis for market research.
Users can customize their requests by providing specific CIN codes in the POST Verification endpoint to target particular companies for verification. The GET Result endpoint requires a valid request ID to fetch specific results.
Users can expect responses to indicate either successful verification with relevant company details or failure with specific error messages, such as "BAD_REQUEST" for invalid CIN inputs.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
241ms
Service Level:
100%
Response Time:
54ms
Service Level:
100%
Response Time:
1,701ms
Service Level:
100%
Response Time:
127ms
Service Level:
100%
Response Time:
74ms
Service Level:
100%
Response Time:
104ms
Service Level:
100%
Response Time:
255ms
Service Level:
100%
Response Time:
140ms
Service Level:
100%
Response Time:
123ms
Service Level:
100%
Response Time:
85ms
Service Level:
100%
Response Time:
1,341ms
Service Level:
100%
Response Time:
770ms
Service Level:
100%
Response Time:
1,289ms
Service Level:
100%
Response Time:
1,736ms
Service Level:
100%
Response Time:
1,301ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
1,655ms
Service Level:
100%
Response Time:
2,109ms
Service Level:
83%
Response Time:
1,373ms
Service Level:
100%
Response Time:
0ms