CIN OCR API
New
Read an uploaded incorporation document and get the company identifiers back as structured fields. Corporate onboarding then starts from data instead of a retyped CIN.
Overview
CIN OCR reads an incorporation document you submit as an image or an export and returns the company identifiers printed across it as named fields. A company is asked for that document when it applies for a payment account or a corporate loan. It is asked again for a commercial policy, a lease or a place on a vendor list. Your application submits an incorporation document image or export collected from the company. The service reads it and returns the fields it can extract, such as the CIN, company name, date of incorporation and registered office address as printed. Documents issued through the current online incorporation route also show the PAN and TAN alongside them. The fields available differ from one data source and record to the next. Capture sits one step before confirmation: OCR reports what the document says, and looking up the company itself comes next.
- Category
- Document OCR APIs
- Coverage
- Incorporation documents issued to companies registered in India
- Input
- An image, scan or export of a company incorporation document
- Output
- Structured company identifier fields, where the document and image allow
- Typical users
- Payment providers, lenders, insurers, marketplaces, leasing and procurement teams
- Coverage note
- Document formats have changed over the years; available fields vary by record
The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.
Endpoint URL and method
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Authentication
Send your API key in this header on every call, from your own server: a key sent from a browser is refused. A key starting fs_test_ calls the sandbox and one starting fs_live_ calls production, at the same address. Create keys in the FinSour console.
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Request parameters
Headers
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
Idempotency-Key | string | Required | A key you generate for each attempt. Sending the same key again returns the first answer instead of running the check twice; the same key with a different body is refused. | 8 to 255 characters. Matches ^[A-Za-z0-9._:-]+$ |
FinSour-Version | string | Required | Send 2026-11-01 on this call and on every poll to get the receipt and the result described on this page. A call without it is served under 2026-09-01, whose job has a different shape. | — |
Body
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
file | file | Required | The document to read. | — |
payload | string (JSON) | Optional | A JSON string carrying the call's options. | — |
payload. | object | Optional | Settings for this call. | — |
payload. | string | Optional | Your own reference for this call. It comes back unchanged as meta.reference. | 1 to 128 characters |
payload. | object | Optional | The person's consent to this check. | — |
payload. | boolean | Required | Send true once the person has agreed to the check. | Always true |
payload. | string (date-time) | Required | When the person gave consent. | — |
payload. | string | Required | What the check is for, for example kyc. | 1 to 64 characters |
Request samples
cURL
curl -X POST https://gateway.staging.finsour.io/v1/documents/incorporation-certificate \
-H "X-Api-Key: $FINSOUR_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "FinSour-Version: 2026-11-01" \
-F "file=@<path-to-document>"Node.js
import { openAsBlob } from "node:fs";
const form = new FormData();
form.append("file", await openAsBlob("<path-to-document>"));
const response = await fetch("https://gateway.staging.finsour.io/v1/documents/incorporation-certificate", {
method: "POST",
headers: {
"X-Api-Key": process.env.FINSOUR_API_KEY,
"Idempotency-Key": crypto.randomUUID(),
"FinSour-Version": "2026-11-01",
},
body: form,
});
console.log(response.status, await response.json());Python
import os
import uuid
import requests
response = requests.post(
"https://gateway.staging.finsour.io/v1/documents/incorporation-certificate",
headers={
"X-Api-Key": os.environ["FINSOUR_API_KEY"],
"Idempotency-Key": str(uuid.uuid4()),
"FinSour-Version": "2026-11-01",
},
files={"file": open("<path-to-document>", "rb")},
timeout=30,
)
print(response.status_code, response.json())Generated from the fields above. Replace each value in angle brackets with your own; the key is read from FINSOUR_API_KEY.
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Response schema
| Name | Type | Present | Description | Constraints |
|---|---|---|---|---|
data | object | Always | The job that will read the document. | — |
data. | string | Always | The job's id. Poll GET /v1/jobs/{jobId} with it. | Matches ^[0-9A-HJKMNP-TV-Z]{26}$ |
data. | string | Always | Always queued: the job is accepted and has not started. | Always "queued" |
The result
Poll GET /v1/jobs/{jobId}. Once the job has finished, data holds these fields:
| Name | Type | Present | Description | Constraints |
|---|---|---|---|---|
jobId | string | Always | — | — |
status | string | Always | — | One of queued, processing, completed, needs_review, unreadable, failed, expired, cancelled |
documentType | string or null | Always | The kind of document found, once it has been read; null before that. | — |
confidence | number or null | Always | The document's confidence, 0 to 1, to two places; null until it has been read. | Minimum 0. Maximum 1 |
fields | object | Always | What was read. Every key is always present: null means the document does not carry it, or it could not be read with enough confidence. | — |
fields. | string or null | Always | — | — |
fields. | string or null | Always | — | — |
fields. | string or null | Always | ISO date, YYYY-MM-DD; a year or month alone is YYYY or YYYY-MM. | — |
fields. | string or null | Always | — | — |
fields. | string or null | Always | — | — |
fields. | string or null | Always | — | — |
fields. | string or null | Always | — | — |
fieldsToReview | array of strings | Always | When status is needs_review, the fields a person should confirm; empty otherwise. | — |
failureReason | string | Sometimes | Present only when status is unreadable or failed. | One of UNREADABLE_IMAGE, LOW_CONFIDENCE, DOCUMENT_TYPE_MISMATCH, UNSUPPORTED_MEDIA_TYPE, FILE_TOO_LARGE, INPUT_CORRUPT, PAGE_LIMIT_EXCEEDED, TIMEOUT, PROCESSING_ERROR |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Error codes
| Code | Status | Meaning | Retrying |
|---|---|---|---|
API_VERSION_UNSUPPORTED | 400 | That API version is no longer supported. | Do not retry automatically |
IDEMPOTENCY_KEY_INVALID | 400 | That Idempotency-Key does not meet the required format. | Do not retry automatically |
IDEMPOTENCY_KEY_REQUIRED | 400 | An Idempotency-Key header is required for this request. | Do not retry automatically |
REQUEST_MALFORMED | 400 | The request could not be parsed. | Do not retry automatically |
AUTH_KEY_EXPIRED | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_INVALID | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_MISSING | 401 | No API key was presented. | Do not retry automatically |
AUTH_KEY_REVOKED | 401 | The API key is not valid. | Do not retry automatically |
INSUFFICIENT_BALANCE | 402 | The available balance is not enough for this request. | Do not retry automatically |
AUTH_IP_NOT_ALLOWED | 403 | This API key may not be used from this address. | Do not retry automatically |
ENTITLEMENT_MISSING | 403 | This organization is not entitled to that product in this environment. | Do not retry automatically |
ORGANIZATION_SUSPENDED | 403 | This organization is not active. | Do not retry automatically |
PRODUCT_NOT_AVAILABLE | 403 | That product is not available. | Do not retry automatically |
PRODUCT_RETIRED | 403 | That product has been withdrawn. | Do not retry automatically |
SCOPE_INSUFFICIENT | 403 | This API key does not carry the scope this product requires. | Do not retry automatically |
PRODUCT_NOT_FOUND | 404 | No such product. | Do not retry automatically |
IDEMPOTENCY_KEY_REUSED | 409 | That idempotency key was already used for a different request. | Do not retry automatically |
PRICE_UNAVAILABLE | 409 | No active price covers this product right now. | Safe to retry |
REQUEST_IN_PROGRESS | 409 | An earlier attempt with this key is still running. | Safe to retry |
SETTLEMENT_PENDING | 409 | This request is awaiting reconciliation by an operator. | Do not retry automatically |
API_VERSION_SUNSET | 410 | That API version passed its announced sunset date. | Do not retry automatically |
REQUEST_TOO_LARGE | 413 | The request body is too large. | Do not retry automatically |
OCR_UNSUPPORTED_MEDIA_TYPE | 415 | That document format is not accepted. | Do not retry automatically |
UNSUPPORTED_MEDIA_TYPE | 415 | That content type is not accepted on this route. | Do not retry automatically |
SANDBOX_FIXTURE_MISSING | 422 | No sandbox fixture exists for this input. Use a different test value. | Do not retry automatically |
UPSTREAM_REJECTED | 422 | The upstream source rejected the input. | Do not retry automatically |
VALIDATION_FAILED | 422 | The request payload is invalid. | Do not retry automatically |
CONCURRENCY_LIMIT | 429 | Too many simultaneous requests. | Safe to retry |
OCR_QUEUE_SATURATED | 429 | The document queue is full. Retry shortly. | Safe to retry |
QUOTA_EXCEEDED | 429 | The allowance for this window is spent. | Do not retry automatically |
RATE_LIMITED | 429 | Too many requests. | Safe to retry |
INTERNAL_ERROR | 500 | An unexpected error occurred. | Safe to retry |
OUTCOME_UNCERTAIN | 502 | The outcome of this request is not yet known. Retry with the same Idempotency-Key. | Do not retry automatically |
UPSTREAM_UNAVAILABLE | 502 | The upstream source is unavailable. Retry shortly. | Safe to retry |
MAINTENANCE_MODE | 503 | The service is in a maintenance window. | Safe to retry |
NO_PROVIDER_AVAILABLE | 503 | No provider can serve this product right now. | Safe to retry |
OCR_UNAVAILABLE | 503 | Document reading is unavailable right now. Retry later. | Safe to retry |
SERVICE_OVERLOADED | 503 | The service is shedding load. Retry shortly. | Safe to retry |
UPSTREAM_TIMEOUT | 504 | The upstream source did not respond in time. | Safe to retry |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Rate limits
| Scope | Limit | Window | At the limit |
|---|---|---|---|
| Your API key, within your organisation's limit | The figure in X-RateLimit-Limit | Per minute | 429 RATE_LIMITED, with Retry-After in seconds. Every answer past authentication carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Use cases
- Fintech and PSP: incorporated merchant onboarding record creation
- Lending and NBFC: corporate and SME borrower document intake
- Marketplaces: company seller registration and entity capture
- Insurance: proposer entity capture for commercial and group cover
- Real estate: tenant entity capture for commercial leasing
- Procurement: corporate vendor master creation from incorporation documents
What this service does
Company identifiers as fields
Send an incorporation document and get back what the service can recover: the CIN, the company name, the date of incorporation and the registered office address as printed. Documents issued through the current online incorporation route also carry the PAN and TAN. Whether a given identifier comes back depends on the data source and the record.
Nobody retypes a twenty-one character CIN
A CIN is a twenty-one character alphanumeric identifier. It is easy to mistype and expensive to correct once it has spread through a record. Reading it from the document keeps the applicant and the reviewer from copying it out by hand.
Capture inside your corporate application journey
Connect the service to a merchant application form, a corporate credit journey, a vendor onboarding portal or a leasing application. An internal dashboard or a batch run over documents already on file works too.
The CIN every later lookup is keyed on
Company, director and charge lookups are all keyed on the CIN. Capturing it from the document at the start means those checks run against the identifier the document carries.
How a check runs
Collect the document from the company
Accept an upload, scan or export of the incorporation document as part of the merchant, borrower, tenant or vendor application the company is already completing.
Pass the document to the API
Your onboarding system sends the collected pages to the service as soon as it has them.
The service picks out the identifiers
The service processes the submitted file and recovers the company identifier details printed on the document.
Fill the corporate record
Structured fields come back for your merchant, borrower, tenant or vendor record to take as they are.
Confirm the CIN, then look it up
Give the company or a reviewer the pre-filled form to confirm. Send unreadable documents to an exception queue, and pass the confirmed CIN into your next company or director lookup.
Questions
- What document do I upload to read a CIN?
- An image, scan or export of the company incorporation document, collected from the company as part of your own onboarding. Send every page when the document runs to more than one. The service then reads the later sheets as well.
- Which company details come back from CIN OCR?
- Structured fields holding the company identifiers the service could read off the document. That usually means the CIN, the name of the company, the date of incorporation and the registered office address as printed. Documents issued through the current online incorporation route also show the PAN and TAN alongside them. Which of those come back varies by data source and by record.
- Does CIN OCR confirm the company is still registered?
- No. The reading reflects what the document in front of it shows. A company may since have changed its name, moved its registered office or changed status. A company lookup against a business data source is a separate step, and most teams run it right after they capture the document.
- What are the consent rules for an incorporation document?
- The company should know you are collecting its incorporation document, and the extracted values should serve only the onboarding, credit, leasing or compliance purpose behind the request. In a closely held company the registered office address and the tax identifiers printed alongside it can attach to a person. Limit access to the teams whose work needs it, and hold the document and its fields no longer than your stated purpose and retention policy allow.
- Why does an older incorporation document return fewer fields?
- An older certificate carries a different set of printed details from a recent one, because the format has changed over the years. A capture that is skewed, shadowed or heavily compressed hides text that a clean export carries. Assume any field may be missing, and keep an exception route for documents the service cannot read.
- How do we get started with the CIN OCR API?
- Select Get API on this page and describe your corporate onboarding to our team. The service contract you agree sets access, supported formats, multi-page handling and volumes.
Catalog entry last updated .