Finanvo MCA Documents API

Security: API credentials are intentionally shown as placeholders. Never publish a real x-api-key or x-api-secret-key in a public page, frontend JavaScript, screenshots, or client-shared HTML. Provide credentials through a secure channel and call protected APIs from a backend where possible.

At a glance

Use APIs 1–2 for company discovery. Use APIs 3–6 for the document retrieval workflow.

Company lookup

Search by CIN or find a CIN using a company name.

APIs 1–2

List documents

Retrieve available document metadata and ref_key values for a CIN.

API 3 · LIST_DOCS_V3

Submit & track

Submit selected document references and poll the transaction status.

APIs 4–5

Download file

Use the transaction ID and document reference to fetch the file.

API 6

End-to-end flowchart

Client-friendly sequence showing which response values are passed to the next API.

1Find companyAPI 1: CIN → name
or API 2: name → CIN

→2List documentsAPI 3: CIN → docs + ref_keys

→3Select documentsChoose one or more ref_keys

→4Submit orderAPI 4 → transaction_id

→5Check statusAPI 5 → status + download links

→6Download fileAPI 6 → PDF / Excel / supported file

Important: API 3 requires the LIST_DOCS_V3 plan. As provided, one credit is deducted per CIN listing only once, and that listing remains valid for 3 months. Confirm current plan rules with your Finanvo account representative.

Common configuration

Base URL for APIs 1–5

https://api.finanvo.in

Required headers for APIs 1–5

x-api-key: YOUR_API_KEY x-api-secret-key: YOUR_API_SECRET_KEY Content-Type: application/json

API 6 uses the download host shown in its endpoint below. Do not assume the same authentication headers apply there unless confirmed by your API provider.

POST/company/search/by-cinsAPI 1

Find company name by CIN

Pass a CIN to retrieve the matching company name.

Request body

{ "cins": "U74140KA2007PTC041915" }

Example response

{ "data": [ { "dataid": "U74140KA2007PTC041915", "name": "NOVERGY ENERGY SOLUTIONS PRIVATE LIMITED" } ] }

GET/search/company?query=NOVERGYAPI 2

Find CIN by company name

Search using a company name or keyword. URL-encode query values that contain spaces or special characters.

Example response

{ "data": [ { "dataid": "U74140KA2007PTC041915", "name": "NOVERGY ENERGY SOLUTIONS PRIVATE LIMITED" } ] }

GET/company/cin-docs?cin=U74900WB2007PTC119328API 3

List available company documents

Returns document metadata for the CIN. Save each document's ref_key; these references are used when submitting an order.

Plan: LIST_DOCS_V3 — 1 credit per CIN list, charged once and valid for 3 months (as supplied).

Example response

{ "cin": "U74900WB2007PTC119328", "docs": [ { "ref_key": "5r6oeye3go2dbw", "formId": "MSME", "fileName": "Form MSME", "doc_name": "MSME_01_11_2025_signed.pdf", "year": "2025", "dateOfFiling": "31/10/2025", "documentCategory": "Other eForm Documents", "description": "260465746:MSME_01_11_2025_signed.pdf:Document added successfully.", "numberOfPages": "6", "fileSize": "1837747", "paymentDate": "31/10/2025", "fileType": "pdf", "dscUploadDate": "31/10/2025" }, { "ref_key": "5r65617trbp8mu", "formId": "ADT - 1", "fileName": "Optional attachment(s)- if any", "doc_name": "AGM NPPL RESOLUTION.pdf", "year": "2025", "dateOfFiling": "09/10/2025", "documentCategory": "Other eForm Documents", "description": "258278885:ADT_fileAttachment5:Document added successfully.", "numberOfPages": "1", "fileSize": "441394", "paymentDate": "09/10/2025", "fileType": "pdf", "dscUploadDate": "09/10/2025" } ] }

POST/subscription/submit-order/down-docsAPI 4

Submit a document order

Send the CIN and the selected ref_key values returned by API 3.

Request body

{ "cin": "U74900WB2007PTC119328", "ref_keys": [ "5r6oeye3go2dbw", "5r65617trbp8mu", "5r65617trbqku5" ] }

Example response

{ "message": "Saved Successfully", "data": { "transaction_id": "31a0c7fe-4ae9-49a7-8358-aaabd1a9c7a9", "refs_count": 3, "credit_consumed": 1, "credit_source_ids": "4065179", "total": 1, "success": 1, "failed": 0, "results": [ { "transaction_id": "31a0c7fe-4ae9-49a7-8358-aaabd1a9c7a9", "cin": "U74900WB2007PTC119328", "status": "success" } ] } }

Next step: store data.transaction_id and pass it to API 5 to check processing status.

GET/subscription/mcd/order-status/{transaction_id}API 5

Check order status

Replace {transaction_id} with the ID returned by API 4. If the order is not complete, check again according to your application's retry interval and provider limits.

Example response

{ "message": "success", "data": { "transaction_id": "31a0c7fe-4ae9-49a7-8358-aaabd1a9c7a9", "cin": "U74900WB2007PTC119328", "status": 2, "processing_status": 0, "is_completed": 0, "docs": [ { "ref_key": "5r65617trbp8mu", "status": "completed", "download_link": "/api/mcd/download-doc?transaction_id=31a0c7fe-4ae9-49a7-8358-aaabd1a9c7a9&ref_key=5r65617trbp8mu", "formId": "ADT - 1", "fileName": "Optional attachment(s)- if any", "year": "2025", "dateOfFiling": "09/10/2025", "documentCategory": "Other eForm Documents", "numberOfPages": "1", "fileSize": "441394", "fileType": "pdf" }, { "ref_key": "5r65617trbqku5", "status": "completed", "download_link": "/api/mcd/download-doc?transaction_id=31a0c7fe-4ae9-49a7-8358-aaabd1a9c7a9&ref_key=5r65617trbqku5", "formId": "ADT - 1", "fileName": "Optional attachment(s)- if any", "year": "2025", "dateOfFiling": "09/10/2025", "documentCategory": "Other eForm Documents", "numberOfPages": "1", "fileSize": "278705", "fileType": "pdf" }, { "ref_key": "5r6oeye3go2dbw", "status": "completed", "download_link": "/api/mcd/download-doc?transaction_id=31a0c7fe-4ae9-49a7-8358-aaabd1a9c7a9&ref_key=5r6oeye3go2dbw", "formId": "MSME", "fileName": "Form MSME", "year": "2025", "dateOfFiling": "31/10/2025", "documentCategory": "Other eForm Documents", "numberOfPages": "6", "fileSize": "1837747", "fileType": "pdf" } ] } }

Download mapping: for each item in data.docs, use its ref_key and the transaction ID to call API 6. The sample shows document-level statuses as completed; use the live response fields as the source of truth for each order.

GEThttps://mcdapi2.mcadownload.in/api/mcd/download-doc?transaction_id={transaction_id}&ref_key={ref_key}API 6

Download a document

Use the transaction ID from API 4 and the selected document's ref_key. The response is the document file itself (for example PDF, Excel, or another supported format), rather than a JSON metadata response.

Example URL

https://mcdapi2.mcadownload.in/api/mcd/download-doc?transaction_id=31a0c7fe-4ae9-49a7-8358-aaabd1a9c7a9&ref_key=5r65617trbp8mu

The host and route above are based on the supplied example. Confirm whether this download endpoint requires authentication headers or has separate access rules.

Integration notes

Recommended application logic

Search or validate the company CIN.
Call API 3 and show available documents.
Let the user select documents and submit API 4.
Persist the returned transaction ID.
Poll API 5 until each requested document is ready or an error is returned.
Use API 6 to download each completed document.

Handle responses safely

Handle empty search results and invalid CINs.
Handle authentication, credit, validation, and server errors.
Do not assume every requested document succeeds; inspect each result/status.
Use a bounded retry interval for status checks.
Protect API secrets on the server; never log credentials.
Check HTTP status codes and content type when downloading files.

Where to place the API documentation link in Finanvo

Recommended: add an API Documentation link in My Profile → API Access, beside the user's API key management section. You can also add a small footer link for discoverability.

Keep the documentation page shareable, but keep API credentials behind authenticated account access. If the docs are intended only for active API customers, verify the user's entitlement before showing keys or credential values.