Skip to content

Published services, current details, and clear categories.

Explore APIs

Vehicle Document OCR API

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

Request and response

You confirm the required fields and consent steps with us during onboarding.

You send

Registration certificate image or scan

You receive

Printed RC details, returned as structured fields

Coverage
RC formats issued across Indian states, including card and older paper documents
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
Overview

What you can do with the Vehicle Document OCR API

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.

  • 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 it works

The five-step Vehicle Document OCR API workflow

Our team walks you through the exact request and response for this service during onboarding.

Step 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.

Step 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.

Step 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.

Step 4

Get the printed fields back

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

Step 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.

Industries

Where teams use Vehicle Document OCR API

These sectors build the check into a decision they already make.

  • 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

Used in these industries

What is vehicle document OCR?

Vehicle document OCR reads a photograph or scan of a vehicle's Registration Certificate and returns the details printed on it as structured fields. The information can then enter a system 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 application taken at a dealership, a motor policy, a driver-partner signing up to deliver, or a truck subcontracted onto a route.

Somebody currently reads the card and retypes it, and every retyped character can introduce an error that surfaces much later.

How the RC OCR API works

Your application submits the image your customer has already captured and receives the printed fields as structured data. The capture stays inside your own onboarding screen. The customer is not sent elsewhere, and your team is not left with a folder of images to work through.

That is worth most where the same capture repeats, in a rider onboarding funnel, at a dealership desk, or across a branch network collecting documents for vehicle loans.

The RC formats your capture step has to handle

Registration certificates in India come in several forms. Older vehicles may still carry a paper booklet, and most recent registrations are issued as a card. Several states print bilingual cards that set the state language alongside English.

Details are split across the front and the back. A workflow that reads one side will be missing fields it needs.

The images vary more than the documents do. An RC is usually photographed on a phone, at an angle, in a showroom or at the roadside, sometimes through a plastic sleeve.

OCR and RC verification do different jobs

OCR reads what is printed on the document in front of it. It does not establish that the document is genuine, that it is current, or that the vehicle is recorded the way the card says it is.

That is a separate check. Vehicle RC Verification takes a registration number and returns the registration information held by a trusted vehicle data source. That is what you rely on when the answer has to be more than the card.

The two work together. OCR turns the image into fields your form can use, and verification checks the registration number against the record. Neither one replaces the other.

Who reads RC details with OCR

  • Vehicle finance and NBFCs. Fill a loan application from the RC captured at the dealership, instead of asking an applicant to read out an engine or chassis number.
  • Insurance. Motor policy issuance and renewal, and claim intimation, where the RC is photographed at the point the claim is raised.
  • Logistics and fleet operators. Onboard owned and subcontracted vehicles, where the RC is the source for class, fuel type and registration dates.
  • Gig, delivery and staffing platforms. Rider and driver-partner vehicle onboarding done entirely on a phone, with no branch visit.
  • Rental, leasing and self-drive. Capture vehicle details at handover and build the asset record from the document itself.
  • Used-vehicle marketplaces and dealerships. Create a listing or a trade-in record from a photograph instead of a typed form.

How to read an RC online

  • Capture the registration certificate, both sides where your process needs the fields printed on the back.
  • Check the image is legible before it is submitted, and prompt for a retake where it is not.
  • Submit the image through the API.
  • Read the printed details from the structured fields returned.
  • Show the fields back to the person for confirmation, and route anything unclear to a reviewer.

Where RC OCR fits your onboarding screen

Treat the output as a draft your customer confirms. A visible confirmation step catches the fields OCR is most likely to struggle with, such as a worn chassis number or a smudged date. It costs the customer far less than a correction weeks later.

Keep a manual path open. Documents get damaged, and a workflow with nowhere to go when a capture fails will strand the applicant it was built to help.

Where the registration number matters to the decision, treat the read value as unconfirmed and follow the capture with a verification call. The fields available differ by document format, by the condition of the image and by the service contract you select.

A Registration Certificate carries an owner's name and address, which makes the image, and everything read from it, personal information. Collect it with notice and consent, use it only for the purpose the customer was told about, and give access only to the team that needs it.

Images deserve their own attention. They are easy to accumulate and easy to forget. Set a retention period for the uploaded file separately from the fields extracted from it, and delete what the process no longer needs.

FAQ

Common questions

What teams ask before they integrate Vehicle Document OCR API.

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.

Get started

Add Vehicle Document OCR API to your workflow

Tell us how you plan to use it. Our team sets up API access, agrees your pricing and takes you through onboarding.