Skip to main content

RC Document OCR API

Objective

The RC Document OCR API extracts information from a Registration Certificate (RC) document image.

InputOutput
An image of the user's RC Document The textual information extracted from the document. The complete list of output fields is provided under the Success Response Details section

API Endpoint

https://ind-engine.thomas.hyperverge.co/v1/readRC

API Endpoint

readRC

Overview

The API is RESTful and uses standard HTTP verbs and status codes. The responses are in JSON format and you should upload all images and files as form-data through a POST request.

Authentication

You need a unique pair of application ID (appId) and application key (appKey) from HyperVerge to verify your identity for accessing the API.

API Request Details

Method - POST

Headers

ParameterMandatory or OptionalDescriptionAllowed Values
content-type MandatoryThis parameter defines the media type for the request payloadapplication/json
appId MandatoryThe application identifier shared by HyperVerge. You can find the details in the dashboard's credentials tab.This should be a unique value.
appKey MandatoryThe application key shared by HyperVerge. You can find the details in the dashboard's credentials tab.This should be a unique value.
transactionIdMandatoryA unique identifier for tracking a user journeyThis should be both unique and easily associated with the user's journey in your application(s)

Input

The following table provides the complete information on the parameter used in the request body for the API calls.

ParameterDescriptionMandatory or OptionalAllowed ValuesDefault Value
imageThe image file for OCR extractionMandatoryThe file can be of JPG, JPEG or PNG formatNot Applicable

Sample Request

The following code shows a standard cURL request for the API.

curl --location --request POST 'https://ind-engine.thomas.hyperverge.co/v1/readRC' \
--header 'Content-Type: multipart/form-data' \
--header 'appId: <Enter_the_HyperVerge_appId>' \
--header 'appKey: <Enter_the_HyperVerge_appKey>' \
--header 'transactionId: <Enter_the_HyperVerge_transactionID>' \
--form 'image=@"<Enter_image_path_with_extension>"'

Success Response Sample

{
"status": "success",
"statusCode": "200",
"result": [
{
"details": {
"type": "ind_rc",
"registrationNumber": {
"value": "<Extracted_Registration_Number>",
"conf": "<Confidence_Level>"
},
"registrationDate": {
"value": "<Registration_Date_in_DD-MM-YYYY_Format>",
"conf": "<Confidence_Level>"
},
"registrationExpiryDate": {
"value": "<Registration_Expiry_Date_in_DD-MM-YYYY_Format>",
"conf": "<Confidence_Level>"
},
"chassisNumber": {
"value": "<Extracted_Chassis_Number>",
"conf": "<Confidence_Level>"
},
"engineNumber": {
"value": "<Extracted_Engine_Number>",
"conf": "<Confidence_Level>"
},
"ownerName": {
"value": "<Owner_Name>",
"conf": "<Confidence_Level>"
},
"relationName": {
"value": "<Relation_Name>",
"conf": "<Confidence_Level>"
},
"model": {
"value": "<Vehicle_Model>",
"conf": "<Confidence_Level>"
},
"vehicleType": {
"value": "<Type_Of_Vehicle>",
"conf": "<Confidence_Level>"
},
"address": {
"value": "<Owner_Address>",
"conf": "<Confidence_Level>"
},
"manufacturer": {
"value": "<Vehicle_Manufacturer>",
"conf": "<Confidence_Level>"
},
"manufacturingDate": {
"value": "<Manufacturing_Date_in_DD-MM-YYYY_Format>",
"conf": "<Confidence_Level>"
}
}
}
],
"metaData": {
"requestId": "<Request_ID>"
}
}

Success Response Details

ParameterTypeDescription
typestringThe type of document processed
registrationNumber.valuestringThe extracted registration number
registrationNumber.confstringThe confidence level of the extracted registration number, represented as a percentage
registrationDate.valuestringThe extracted registration date in the format "DD/MM/YYYY"
registrationDate.confstringThe confidence level of the extracted registration date, represented as a percentage
registrationExpiryDate.valuestringThe extracted registration expiry date in the format "DD/MM/YYYY"
registrationExpiryDate.confstringThe confidence level of the extracted registration expiry date, represented as a percentage
chassisNumber.valuestringThe extracted chassis number
chassisNumber.confstringThe confidence level of the extracted chassis number, represented as a percentage
engineNumber.valuestringThe extracted engine number
engineNumber.confstringThe confidence level of the extracted engine number, represented as a percentage
ownerName.valuestringThe user's name, extracted from the document
ownerName.confstringThe confidence level of the user's name, represented as a percentage
relationName.valuestringThe user's relative's name, as extracted from the document
relationName.confstringThe confidence level of the extracted relation name, represented as a percentage
model.valuestringThe extracted vehicle model
model.confstringThe confidence level of the extracted vehicle model, represented as a percentage
vehicleType.valuestringThe extracted vehicle type
vehicleType.confstringThe confidence level of the extracted vehicle type, represented as a percentage
address.valuestringThe user's address as extracted from the document
address.confstringThe confidence level of the extracted address, represented as a percentage
manufacturer.valuestringThe extracted manufacturer
manufacturer.confstringThe confidence level of the extracted manufacturer, represented as a percentage
manufacturingDate.valuestringThe extracted manufacturing date in the format "DD/MM/YYYY"
manufacturingDate.confstringThe confidence level of the extracted manufacturing date, represented as a percentage

Error Response Samples

{
"message": "Invalid file type for: image",
"statusCode": 400,
"status": "failure"
}

Error Response Details

A failure or error response from the module contains a failure status, with a relavant status code and error message. The following table lists all error responses.

Status CodeError MessageError Description
400Invalid file type for: imageThe file type provided is not acceptable for the specified file type
401Missing/Invalid credentialsThe request is either missing the mandatory appId and appKey combination or has invalid values
422Document Not DetectedThe request is missing the required RC document or it could not be detected
500Internal Server ErrorPlease check the request headers or contact the HyperVerge team for resolution
Was this helpful?
Ask AIBeta
Hi! How can I help?
Ask me anything about HyperVerge products, APIs, and SDKs.
Try asking: