RC Owner History

Endpoint Overview

POST /api/v1/rc/rc-owner-history

Description

This API retrieves the complete ownership history of a vehicle using its registration certificate (RC) number. It provides a chronological record of all owners who have possessed the vehicle, including the current owner's details and their position in the ownership sequence. This information is valuable for verifying vehicle provenance, conducting due diligence before vehicle purchases, and maintaining accurate vehicle ownership records.

Key Benefits

Verify vehicle ownership history to identify potential fraud or undisclosed transfers

Access chronological ownership data with sequential numbering for complete provenance tracking

Obtain current owner information alongside historical ownership records in a single API call

Support compliance requirements for vehicle financing, insurance, and resale transactions

Use Cases

Automotive

Financial Services

Government & Compliance

Used car dealerships can verify vehicle ownership history before purchasing inventory

Vehicle marketplaces can display ownership history to build buyer confidence

Automotive service centers can validate ownership during service registration

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 format)
Content-Type	Yes	application/json

Request Body

Parameter	Type	Required	Description
id_number	String	Yes	Vehicle registration certificate (RC) number

Example Request

{
    "id_number": "GJ01RV8999"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Contains the vehicle ownership information
data.client_id	String	Unique identifier for the request
data.rc_number	String	Registration number of the vehicle
data.current_owner_number	String	Current owner's position in the ownership sequence
data.current_owner_name	String	Name of the current vehicle owner
data.owner_history	Array	List of all owners (past and current) in chronological order
data.owner_history[].owner_name	String	Name of the owner
data.owner_history[].owner_number	String	Sequential number indicating order of ownership
status_code	Number	HTTP status code of the response
success	Boolean	Indicates if the request was successful
message	String	Additional information about the response (null if successful)
message_code	String	Code indicating the status of the response

Example Successful Response

{
    "data": {
        "client_id": "rc_owner_history_fItRxcCeVoihtfxjggcF",
        "rc_number": "GJ01RV8123",
        "current_owner_number": "3",
        "current_owner_name": "MAHAMMADALI",
        "owner_history": [
            {
                "owner_name": "HEMPREET SINGH BAJAJ",
                "owner_number": "1"
            },
            {
                "owner_name": "VARUNKUMAR DINESHKUMAR GADHAVI",
                "owner_number": "2"
            },
            {
                "owner_name": "MAHAMMADALI",
                "owner_number": "3"
            }
        ]
    },
    "status_code": 200,
    "success": true,
    "message": null,
    "message_code": "success"
}

Possible Error Responses

Invalid RC Number

Authentication Error

Service Unavailable

{
    "status_code": 422,
    "success": false,
    "message": "Verification Failed.",
    "message_code": "verification_failed"
}

The provided RC number is in an invalid format or does not exist in the records.

Integration Best Practices

Security Recommendations

Store JWT tokens securely and never expose them in client-side code

Implement token refresh mechanisms to handle token expiration

Validate and sanitize RC numbers before sending to prevent injection attacks

Implement proper error handling to avoid exposing sensitive information

User Experience Guidelines

Display ownership history in chronological order with clear indication of the current owner

Implement caching strategies to improve response times for frequently queried vehicles

Provide clear error messages to end-users when RC numbers are invalid or not found

Consider implementing progressive loading for applications displaying ownership history

Code Samples

cURL

Python

Node.js

Related APIs

RC Details API: Retrieves comprehensive details about a vehicle registration certificate

RC Verification API: Validates the authenticity of a vehicle registration certificate

RC Status Check API: Checks the current status of a vehicle registration certificate

Compliance and Legal Considerations

This API provides access to vehicle ownership data which may be subject to privacy regulations. Ensure you have proper consent and legal basis for accessing this information. The data should be used in compliance with local transport authority regulations and data protection laws. Vehicle ownership information should not be used for unauthorized surveillance or tracking purposes.

{ "data": { "client_id": "rc_owner_history_fItRxcCeVoihtfxjggcF", "rc_number": "GJ01RV8123", "current_owner_number": "3", "current_owner_name": "MAHAMMADALI", "owner_history": [ { "owner_name": "HEMPREET SINGH BAJAJ", "owner_number": "1" }, { "owner_name": "VARUNKUMAR DINESHKUMAR GADHAVI", "owner_number": "2" }, { "owner_name": "MAHAMMADALI", "owner_number": "3" } ] }, "status_code": 200, "success": true, "message": null, "message_code": "success" }

RC Owner History

RC Owner History#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses

RC Owner History

Description

Use Cases

Technical Implementation

Request Headers

Request Body

Example Request

Response Parameters

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples