RC Stolen

Endpoint Overview

POST /api/v1/rc/rc-stolen

Description

The RC Stolen Vehicle Verification API allows you to check whether a vehicle has been reported as stolen in India by verifying its Registration Certificate (RC) number against the national database. This API provides comprehensive details about stolen vehicles including FIR information, complainant details, vehicle specifications, and the location from where the vehicle was stolen.

This endpoint is essential for preventing fraud in vehicle transactions, ensuring compliance with legal requirements, and protecting businesses and individuals from unknowingly purchasing or dealing with stolen vehicles. The API returns real-time data from official police records, enabling instant verification during vehicle onboarding, purchase, financing, or insurance processes.

Key Benefits

Fraud Prevention: Instantly verify if a vehicle is reported stolen before any transaction

Comprehensive Data: Access detailed FIR information, vehicle specifications, and complainant details

Real-time Verification: Get instant results from official police databases across India

Risk Mitigation: Protect your business from legal complications and financial losses associated with stolen vehicles

Use Cases

Automotive & Dealerships

Financial Services

Logistics & Transportation

Used Car Dealerships: Verify vehicles before purchase to ensure inventory legitimacy and protect business reputation

Vehicle Marketplaces: Screen listings to prevent stolen vehicles from being sold on the platform

Auto Auctions: Validate vehicles before auction to maintain platform integrity

Fleet Management: Verify vehicles during procurement and periodic audits

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

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

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for API authentication. Format: `Bearer YOUR_JWT_TOKEN`
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
rc_number	string	Yes	The vehicle Registration Certificate number to be verified. Format should follow Indian RC number pattern (e.g., GJ01RV8999). Accepts alphanumeric characters.

Example Request

{
    "rc_number": "GJ01RV8999"
}

Process Response

Response Parameters

Parameter	Type	Description
data	object	Container object holding the verification results
data.client_id	string	Unique identifier for this verification request
data.rc_number	string	The RC number that was verified
data.results	array	Array of stolen vehicle records matching the RC number
data.results[].rc_number	string	Registration Certificate number of the stolen vehicle
data.results[].fir_number	string	First Information Report number filed for the theft
data.results[].state	string	State where the FIR was filed
data.results[].district	string	District/police jurisdiction where the FIR was filed
data.results[].fir_date	string	Date when the FIR was filed (format: YYYY-MM-DD)
data.results[].police_station	string	Police station where the theft was reported
data.results[].vehicle_type	string	Type/category of the vehicle (e.g., MOTOR CYCLE, CAR)
data.results[].vehicle_make	string	Manufacturer/brand of the vehicle
data.results[].engine_number	string	Engine number of the stolen vehicle
data.results[].vehicle_model	string	Model name of the vehicle
data.results[].chassis_number	string	Chassis number of the stolen vehicle
data.results[].vehicle_color	string	Color of the stolen vehicle
data.results[].phone_number	string	Contact number of the complainant
data.results[].complainant_name	string	Name of the person who filed the complaint
data.results[].address	string	Address of the complainant
data.results[].stolen_from	string	Location/place from where the vehicle was stolen
data.results[].status	string	Current status of the vehicle (e.g., Stolen)
data.results[].report_date	string	Date when the report was recorded (format: YYYY-MM-DD)
status_code	integer	HTTP status code of the response
success	boolean	Indicates whether the API request was successful
message	string	Human-readable message describing the result
message_code	string	Machine-readable code for the message

Example Successful Response

{
    "data": {
        "client_id": "rc_stolen_iubVHkfaXJlyagRYOOWk",
        "rc_number": "GJ01RV8999",
        "results": [
            {
                "rc_number": "GJ01RV8999",
                "fir_number": "036795",
                "state": "DELHI",
                "district": "Crime Branch, Delhi",
                "fir_date": "2017-11-01",
                "police_station": "e-Police Station MV Theft",
                "vehicle_type": "MOTOR CYCLE",
                "vehicle_make": "TVS",
                "engine_number": "AB1CD1112333",
                "vehicle_model": "APACHE",
                "chassis_number": "AB123CD45H2G12345",
                "vehicle_color": "GREY",
                "phone_number": "9876543210",
                "complainant_name": "RAJIV TALWAR",
                "address": "DELHI DELHI 110032",
                "stolen_from": "NEAR FLYOVER GTB HOSPITAL CROSSING DELHI",
                "status": "Stolen",
                "report_date": "1800-01-01"
            }
        ]
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid RC Number

Unauthorized

No Records Found

Rate Limit Exceeded

{
    "data": null,
    "status_code": 400,
    "success": false,
    "message": "Invalid RC number format",
    "message_code": "invalid_input"
}

This error occurs when the RC number provided doesn't match the expected format or contains invalid characters.

Integration Best Practices

Security Recommendations

Token Management: Never expose JWT tokens in client-side code or public repositories. Store tokens securely on the server side.

HTTPS Only: Always use HTTPS endpoints to ensure encrypted data transmission.

Token Rotation: Implement regular token rotation policies to minimize security risks.

Input Validation: Validate and sanitize RC numbers before sending requests to prevent injection attacks.

Error Handling: Implement proper error handling to avoid exposing sensitive information in error messages.

Rate Limiting: Implement client-side rate limiting to avoid exceeding API quotas.

User Experience Guidelines

Loading States: Display clear loading indicators during API calls to inform users that verification is in progress.

Result Display: If a vehicle is flagged as stolen, display FIR details, police station information, and contact details prominently.

Empty Results: When no stolen records are found, clearly communicate that the vehicle is not in the stolen database (this is a positive result).

Error Messages: Provide user-friendly error messages that guide users on corrective actions.

Retry Mechanism: Implement automatic retry logic with exponential backoff for transient failures.

Caching Strategy: Consider caching verification results appropriately, but implement cache invalidation to ensure data freshness.

Code Samples

cURL

Python

Node.js

Compliance and Legal Considerations

Data Privacy: This API accesses official police records. Ensure compliance with applicable data protection laws including the Information Technology Act, 2000 and Digital Personal Data Protection Act, 2023. Use the data only for legitimate verification purposes.

Legal Usage: This API should only be used for preventing fraud and ensuring legal compliance in vehicle transactions. Misuse of data or unauthorized access may result in legal consequences.

Record Accuracy: While the API provides data from official sources, there may be delays in database updates. Always cross-verify critical information with local authorities when necessary.

Consent Requirements: When collecting RC numbers from individuals, ensure proper consent is obtained and users are informed about the verification process.

Data Retention: Implement appropriate data retention policies and delete verification records as per your compliance requirements and applicable regulations.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/rc/rc-stolen' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "rc_number": "GJ01RV8999" }'

{ "data": { "client_id": "rc_stolen_iubVHkfaXJlyagRYOOWk", "rc_number": "GJ01RV8999", "results": [ { "rc_number": "GJ01RV8999", "fir_number": "036795", "state": "DELHI", "district": "Crime Branch, Delhi", "fir_date": "2017-11-01", "police_station": "e-Police Station MV Theft", "vehicle_type": "MOTOR CYCLE", "vehicle_make": "TVS", "engine_number": "AB1CD1112333", "vehicle_model": "APACHE", "chassis_number": "AB123CD45H2G12345", "vehicle_color": "GREY", "phone_number": "9876543210", "complainant_name": "RAJIV TALWAR", "address": "DELHI DELHI 110032", "stolen_from": "NEAR FLYOVER GTB HOSPITAL CROSSING DELHI", "status": "Stolen", "report_date": "1800-01-01" } ] }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

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