Vehicle RC OCR API

Endpoint Overview

POST /api/v1/ocr/vehicle-rc

Description

The Vehicle RC OCR API extracts key information from vehicle registration certificates (RC) using advanced optical character recognition technology. This API accepts vehicle RC images in various formats (file upload, base64, or URL) and returns structured data containing registration details, owner information, and vehicle specifications.

Key Benefits

Automated extraction of vehicle RC data eliminates manual data entry errors

Supports multiple input formats (image upload, base64, URL) for flexible integration

Extracts comprehensive vehicle information including registration, owner, and technical details

Reduces KYC processing time from minutes to seconds

Use Cases

Insurance

Finance

Automotive

Streamline vehicle insurance policy issuance by automatically extracting RC details

Verify vehicle information during claims processing

Reduce fraud by validating RC data against insurance applications

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.io

Production: https://kyc-api.surepass.io

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for authentication (JWT)
Content-Type	Yes	`application/json` for JSON requests or `multipart/form-data` for file uploads

Request Body

The API supports three different input methods. Choose one based on your implementation needs:

Option 1: File Upload

Parameter	Type	Required	Description
file	File	Yes	Vehicle RC image to be processed
use_pdf	Boolean	No	Set to `true` if the uploaded file is a PDF

Option 2: Base64 String

Parameter	Type	Required	Description
base_64	String	Yes	Vehicle RC image encoded in Base64 format

Option 3: Image URL

Parameter	Type	Required	Description
link	String	Yes	URL/link to the Vehicle RC image

Example Request (Base64)

{
  "base_64": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL..."
}

Example Request (URL)

{
  "link": "https://example.com/vehicle-rc-image.jpg"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Contains the extracted vehicle RC information
data.client_id	String	Unique identifier for the OCR request
data.registration_number	String	Vehicle's registration number
data.chassis_number	String	Unique number identifying the vehicle's chassis
data.engine_number	String	Unique number identifying the vehicle's engine
data.owner_name	String	Name of the vehicle owner
data.relative	String	Name of the relative of the vehicle owner
data.address	String	Address of the vehicle owner
data.fuel_used	String	Type of fuel used by the vehicle
data.date_of_registration	String	Date when the vehicle was registered (YYYY-MM-DD)
data.registration_validity	String	Validity date of the vehicle's registration (YYYY-MM-DD)
data.owner_sr_no	String	Serial number of the owner
data.state	String	State where the vehicle is registered
data.vehicle_weight	String	Weight of the vehicle (may be null)
status_code	Integer	HTTP status code of the response
success	Boolean	Indicates if the API call was successful
message	String	Human-readable status message
message_code	String	Machine-readable status code

Example Successful Response

{
    "data": {
        "client_id": "ocr_vehicle_rc_LyycewqbxweVKvlURPpb",
        "registration_number": "RJ14XJ1234",
        "chassis_number": "ME3U3K5F1LK7312345",
        "engine_number": "U3K5F1LK38123456",
        "owner_name": "MAHENDARA SINGH RAJPUT",
        "relative": "RAJENDAR SINGH RAJPUT",
        "address": "A-403  JAGATPURA Jaipur RJ 302017",
        "fuel_used": "PETROL",
        "date_of_registration": "2020-10-08",
        "registration_validity": "2035-10-07",
        "owner_sr_no": "01",
        "state": "Rajasthan",
        "vehicle_weight": null
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Authentication Error

Invalid Image

Invalid File Format

Server Error

{
    "error": null,
    "message": "Your token is invalid. Please ensure that correct token is being used.",
    "status_code": 401,
    "success": false,
    "message_code": "invalid_token"
}

Occurs when the JWT token is missing, invalid, or expired.

Integration Best Practices

Security Recommendations

Store API keys securely and never expose them in client-side code

Implement proper error handling to avoid exposing sensitive information

Use HTTPS for all API communications to ensure data encryption

Implement token refresh mechanisms to handle JWT expiration

User Experience Guidelines

Provide clear instructions to users about acceptable RC image formats and quality

Implement a preview feature to help users capture clear images of their RC

Display a loading indicator during OCR processing to indicate progress

Allow users to manually correct extracted information if needed

Code Samples

cURL

Python

Node.js

Related APIs

PAN Card OCR API: Extract information from PAN cards using OCR technology

Aadhaar Card OCR API: Extract information from Aadhaar cards using OCR technology

Driving License OCR API: Extract information from driving licenses using OCR technology

Voter ID OCR API: Extract information from voter ID cards using OCR technology

Compliance and Legal Considerations

When using this API, ensure compliance with data protection regulations such as the Personal Data Protection Bill (PDPB) in India. Only process vehicle RC data with proper user consent and for legitimate business purposes. Store extracted data securely and retain it only for the necessary duration. The API should be used in accordance with the terms of service provided by Surepass.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

{ "data": { "client_id": "ocr_vehicle_rc_LyycewqbxweVKvlURPpb", "registration_number": "RJ14XJ1234", "chassis_number": "ME3U3K5F1LK7312345", "engine_number": "U3K5F1LK38123456", "owner_name": "MAHENDARA SINGH RAJPUT", "relative": "RAJENDAR SINGH RAJPUT", "address": "A-403 JAGATPURA Jaipur RJ 302017", "fuel_used": "PETROL", "date_of_registration": "2020-10-08", "registration_validity": "2035-10-07", "owner_sr_no": "01", "state": "Rajasthan", "vehicle_weight": null }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

Vehicle RC

Vehicle RC OCR API#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Option 1: File Upload#

Option 2: Base64 String#

Option 3: Image URL#

Example Request (Base64)#

Example Request (URL)#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses