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 |
{"Example Response":"No response example available for now."}
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": "123456789012345678901"
}
}'
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": "2025-03-24T23:32:57+05:30",
"created_at": "2025-03-24T23:32:57+05:30",
"error": "BAD_REQUEST",
"group_id": "8e16424a-58fc-4ba4-ab20-5bc8e7c3c41e",
"message": "Please enter a valid CIN.",
"request_id": "2b70406e-98cf-4873-8402-e383338adfce",
"status": "failed",
"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=Required' --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.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
1,938ms
Service Level:
100%
Response Time:
142ms
Service Level:
67%
Response Time:
1,074ms
Service Level:
100%
Response Time:
593ms
Service Level:
100%
Response Time:
120ms
Service Level:
100%
Response Time:
1,468ms
Service Level:
100%
Response Time:
832ms
Service Level:
100%
Response Time:
1,725ms
Service Level:
100%
Response Time:
168ms
Service Level:
100%
Response Time:
1,089ms
Service Level:
100%
Response Time:
832ms
Service Level:
100%
Response Time:
841ms
Service Level:
100%
Response Time:
1,725ms
Service Level:
100%
Response Time:
609ms
Service Level:
100%
Response Time:
114ms
Service Level:
100%
Response Time:
45ms
Service Level:
100%
Response Time:
1,089ms
Service Level:
100%
Response Time:
868ms
Service Level:
100%
Response Time:
5,118ms
Service Level:
100%
Response Time:
855ms