CIN Basic

Business & KYB

Verifies a company CIN / LLPIN against MCA records and returns company master data, charges and directors/signatories.

Endpoint

POST https://app.emver.io/api/sandbox/v1/cin-basic

Authorization: Bearer YOUR_API_KEY

Content-Type: application/json

Accept: application/json

Request parameters

Field	Type	Description
`cin_basic_cin` required	string	CIN / LLPIN 21-char CIN or LLPIN / FCRN

Example request

cURL

curl -X POST https://app.emver.io/api/sandbox/v1/cin-basic \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "cin_basic_cin": "string"
}'

import requests

response = requests.post(
    "https://app.emver.io/api/sandbox/v1/cin-basic",
    headers={
        "Authorization": "Bearer YOUR_API_KEY",
        "Accept": "application/json",
    },
    json={
        "cin_basic_cin": "string"
    },
    timeout=60,
)
response.raise_for_status()
data = response.json()

const response = await fetch("https://app.emver.io/api/sandbox/v1/cin-basic", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_API_KEY",
    "Content-Type": "application/json",
    "Accept": "application/json",
  },
  body: JSON.stringify({
      "cin_basic_cin": "string"
  }),
});

const data = await response.json();

$response = Http::withToken('YOUR_API_KEY')
    ->acceptJson()
    ->post('https://app.emver.io/api/sandbox/v1/cin-basic', {
        "cin_basic_cin": "string"
    });

$data = $response->json();

Replace YOUR_API_KEY and the placeholder values. Use the switch above to see production URLs.

Response

Structure · 200

{
  "status": INTEGER,
  "message": STRING
}

Example · 200

{
  "status": 200,
  "message": "string"
}

Error · 4xx / 5xx

{
  "status": INTEGER,
  "message": STRING
}

See Errors & status codes for what each status means and which calls are billed.

About this API

CIN Basic

Verifies a company CIN / LLPIN against MCA records and returns company master data, charges and directors/signatories.

Endpoint

POST /api/v1/cin-basic
Content-Type: application/json

Request parameters

Field	Required	Description
`cin_basic_cin`	Yes	CIN / LLPIN - 21-char CIN or LLPIN / FCRN. Example: `U72900KA2016PTC123456`

Sample request

{
  "cin_basic_cin": "U72900KA2016PTC123456"
}

Sample success response

{
  "status": 200,
  "message": "Verification successful",
  "data": {
    "cin": "...",
    "company_id": "...",
    "company_name": "...",
    "roc_code": "...",
    "registration_number": "...",
    "company_category": "...",
    "company_sub_category": "...",
    "class_of_company": "...",
    "authorised_capital": "...",
    "paid_up_capital": "...",
    "number_of_members": "...",
    "date_of_incorporation": "...",
    "registered_address": "...",
    "email": "...",
    "listed_status": "...",
    "date_of_last_agm": "...",
    "date_of_balance_sheet": "...",
    "company_status": "...",
    "charges": "...",
    "directors": "..."
  }
}

Sample error response

{
  "status": 404,
  "message": "No record found for the given input"
}

Response status codes

The status field in the response body indicates the verification outcome.

status	Meaning
`200`	Verification successful
`400`	Invalid input / verification failed
`404`	No record found
`422`	Invalid or missing input parameters
`500`	Source unavailable - retry later