Skip to content

Vehicle Document OCR API

Read a vehicle Registration Certificate image and get the printed details back as structured fields.

Overview

Vehicle document OCR reads a photograph or scan of a vehicle's Registration Certificate and returns the printed details as structured fields. Vehicle information then enters your systems without being typed in by hand. The RC is the document you ask for whenever a vehicle enters a process you did not originate. That covers a loan taken at a dealership, a motor policy, a driver-partner signing up, or a truck subcontracted onto a route. Reading it by hand is slow at the counter and error-prone at volume. This service works alongside Vehicle RC Verification. OCR turns the document into fields your form can use, and verification checks the registration number against a trusted vehicle data source. The fields available differ by document format, by the condition of the image and by the service contract you select.

Coverage
RC formats issued across Indian states, including card and older paper documents
Input
Registration certificate image or scan
Output
Printed RC details, returned as structured fields
Typical users
Lenders, insurers, fleet and gig platforms, marketplaces, rental operators
Coverage note
Reads what is legible on the image you send; fields differ by format and capture quality

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

POSThttps://gateway.staging.finsour.io/v1/documents/vehicle-rc

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

Scheme API key travels in the X-Api-Key header

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

Content type multipart/form-data

Headers

NameTypeRequiredDescriptionConstraints
Idempotency-KeystringRequiredA 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-VersionstringRequiredSend 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

NameTypeRequiredDescriptionConstraints
filefileRequiredThe document to read.—
payloadstring (JSON)OptionalA JSON string carrying the call's options.—
payload.optionsobjectOptionalSettings for this call.—
payload.options.referencestringOptionalYour own reference for this call. It comes back unchanged as meta.reference.1 to 128 characters
payload.options.consentobjectOptionalThe person's consent to this check.—
payload.options.consent.obtainedbooleanRequiredSend true once the person has agreed to the check.Always true
payload.options.consent.atstring (date-time)RequiredWhen the person gave consent.—
payload.options.consent.purposestringRequiredWhat the check is for, for example kyc.1 to 64 characters

Request samples

cURL

curl -X POST https://gateway.staging.finsour.io/v1/documents/vehicle-rc \
  -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/vehicle-rc", {
  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/vehicle-rc",
    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

Status 202 · content type application/json

NameTypePresentDescriptionConstraints
dataobjectAlwaysThe job that will read the document.—
data.jobIdstringAlwaysThe job's id. Poll GET /v1/jobs/{jobId} with it.Matches ^[0-9A-HJKMNP-TV-Z]{26}$
data.statusstringAlwaysAlways 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:

NameTypePresentDescriptionConstraints
jobIdstringAlways——
statusstringAlways—One of queued, processing, completed, needs_review, unreadable, failed, expired, cancelled
documentTypestring or nullAlwaysThe kind of document found, once it has been read; null before that.—
confidencenumber or nullAlwaysThe document's confidence, 0 to 1, to two places; null until it has been read.Minimum 0. Maximum 1
fieldsobjectAlwaysWhat 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.registrationNumberstring or nullAlways——
fields.chassisLast5string or nullAlways——
fields.ownerNamestring or nullAlways——
fields.fuelTypestring or nullAlways——
fieldsToReviewarray of stringsAlwaysWhen status is needs_review, the fields a person should confirm; empty otherwise.—
failureReasonstringSometimesPresent 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

CodeStatusMeaningRetrying
API_VERSION_UNSUPPORTED400That API version is no longer supported.Do not retry automatically
IDEMPOTENCY_KEY_INVALID400That Idempotency-Key does not meet the required format.Do not retry automatically
IDEMPOTENCY_KEY_REQUIRED400An Idempotency-Key header is required for this request.Do not retry automatically
REQUEST_MALFORMED400The request could not be parsed.Do not retry automatically
AUTH_KEY_EXPIRED401The API key is not valid.Do not retry automatically
AUTH_KEY_INVALID401The API key is not valid.Do not retry automatically
AUTH_KEY_MISSING401No API key was presented.Do not retry automatically
AUTH_KEY_REVOKED401The API key is not valid.Do not retry automatically
INSUFFICIENT_BALANCE402The available balance is not enough for this request.Do not retry automatically
AUTH_IP_NOT_ALLOWED403This API key may not be used from this address.Do not retry automatically
ENTITLEMENT_MISSING403This organization is not entitled to that product in this environment.Do not retry automatically
ORGANIZATION_SUSPENDED403This organization is not active.Do not retry automatically
PRODUCT_NOT_AVAILABLE403That product is not available.Do not retry automatically
PRODUCT_RETIRED403That product has been withdrawn.Do not retry automatically
SCOPE_INSUFFICIENT403This API key does not carry the scope this product requires.Do not retry automatically
PRODUCT_NOT_FOUND404No such product.Do not retry automatically
IDEMPOTENCY_KEY_REUSED409That idempotency key was already used for a different request.Do not retry automatically
PRICE_UNAVAILABLE409No active price covers this product right now.Safe to retry
REQUEST_IN_PROGRESS409An earlier attempt with this key is still running.Safe to retry
SETTLEMENT_PENDING409This request is awaiting reconciliation by an operator.Do not retry automatically
API_VERSION_SUNSET410That API version passed its announced sunset date.Do not retry automatically
REQUEST_TOO_LARGE413The request body is too large.Do not retry automatically
OCR_UNSUPPORTED_MEDIA_TYPE415That document format is not accepted.Do not retry automatically
UNSUPPORTED_MEDIA_TYPE415That content type is not accepted on this route.Do not retry automatically
SANDBOX_FIXTURE_MISSING422No sandbox fixture exists for this input. Use a different test value.Do not retry automatically
UPSTREAM_REJECTED422The upstream source rejected the input.Do not retry automatically
VALIDATION_FAILED422The request payload is invalid.Do not retry automatically
CONCURRENCY_LIMIT429Too many simultaneous requests.Safe to retry
OCR_QUEUE_SATURATED429The document queue is full. Retry shortly.Safe to retry
QUOTA_EXCEEDED429The allowance for this window is spent.Do not retry automatically
RATE_LIMITED429Too many requests.Safe to retry
INTERNAL_ERROR500An unexpected error occurred.Safe to retry
OUTCOME_UNCERTAIN502The outcome of this request is not yet known. Retry with the same Idempotency-Key.Do not retry automatically
UPSTREAM_UNAVAILABLE502The upstream source is unavailable. Retry shortly.Safe to retry
MAINTENANCE_MODE503The service is in a maintenance window.Safe to retry
NO_PROVIDER_AVAILABLE503No provider can serve this product right now.Safe to retry
OCR_UNAVAILABLE503Document reading is unavailable right now. Retry later.Safe to retry
SERVICE_OVERLOADED503The service is shedding load. Retry shortly.Safe to retry
UPSTREAM_TIMEOUT504The 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

ScopeLimitWindowAt the limit
Your API key, within your organisation's limitThe figure in X-RateLimit-LimitPer minute429 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

  • Vehicle finance: filling a loan application from the RC captured at the dealership
  • Insurance: reading the RC at motor policy issuance, renewal and claim intimation
  • Logistics and fleet: onboarding owned and subcontracted vehicles from the certificate
  • Gig and delivery platforms: driver-partner vehicle onboarding done on a phone
  • Rental and leasing: capturing vehicle details at handover to build the asset record
  • Used-vehicle marketplaces: creating a listing or trade-in record from a photograph

What this service does

  • Fields the read can return

    Registration number, owner name, engine and chassis numbers, vehicle class, maker and model, fuel type and registration-related dates, as printed on the document. What is available depends on the document format, the condition of the image and the service contract you select.

  • Handles the formats in circulation

    Card-format certificates, older paper documents and bilingual state layouts, captured on a phone rather than a scanner. Front and back are both read, which matters because a card splits its details across the two sides.

  • Capture stays in your own screen

    The customer stays in your onboarding flow instead of being sent elsewhere, and your team is not left with a folder of images to work through by hand.

  • Pairs with RC verification

    OCR reads the document. Vehicle RC Verification checks the registration number against a trusted vehicle data source. Use them together where the decision needs more than what the card shows.

How a check runs

  1. Set up access for RC capture

    Tell us how your capture flow works. We turn on access for your organization under the applicable service contract.

  2. Photograph the certificate

    Your application collects an image of the registration certificate, with both sides where your process needs the fields printed on the back.

  3. Send the image for reading

    Your application sends the captured image to the API for reading, once you have recorded the notice and consent.

  4. Get the printed fields back

    Your application receives the details printed on the document as structured fields your form can use without retyping.

  5. Confirm before you use it

    Show the fields back for confirmation, route anything unclear to a reviewer, and carry the confirmed values into the application, policy or asset record.

Questions

What do I upload for vehicle document OCR, and what comes back?
You send an image or scan of the registration certificate. You get back the printed details as structured fields: registration number, owner name, engine and chassis numbers, vehicle class, maker and model, fuel type and registration-related dates. Which fields appear differs by document format, by the condition of the image and by the service contract you select.
Does RC OCR verify the registration certificate?
No. OCR reads what is printed on the document you send it, and it does not establish that the document is genuine or current. Where the decision needs more than the card, pair the capture with Vehicle RC Verification, which checks the registration number against a trusted vehicle data source.
Do I need both sides of the RC for OCR?
It depends on the fields your process relies on. Details are split across the front and the back of a card-format certificate. A workflow that needs the fields printed on the reverse should capture both sides.
What happens when the RC photo is blurred or damaged?
Registration certificates are usually photographed on a phone, at an angle, sometimes through a plastic sleeve or on a worn document. Build the flow to prompt for a retake and to show the read fields back for confirmation. Keep a manual path for captures that cannot be salvaged.
Do I need consent to process an RC image?
A Registration Certificate carries an owner's name and address, so the image and the fields read from it are personal information. Collect them with notice and consent, and use them only for the purpose the customer was told about. Give access only to the team that needs them, and set retention periods for the stored image and the extracted fields.
How do I get access to the vehicle document OCR API?
Use Get API to describe your capture flow and the volumes you expect. We confirm what the service can support for your case, then set up access under the applicable service contract.

Catalog entry last updated .