RC Challan Details

Fetches traffic challan records from the Government e-Challan system. Returns both pending and disposed challan records along with offence details, fine amounts, and court information.

Key Benefits:

→ Retrieve pending and disposed challan records using only the vehicle registration number.

→ Access structured offence and violation data for each challan.

→ Government-authoritative source — data from official state traffic portals.

→ Supports compliance checks, pre-purchase vehicle due diligence, and fleet management.

Use Cases:

→ Vehicle verification before issuing loans, insurance policies, or used-car transactions.

→ Fleet compliance monitoring and challan management.

→ Pre-purchase due diligence for individuals and dealerships.

→ KYC and background verification workflows.

Request Body Parameters:

→ vehicleNumber (required): Vehicle registration number, 5 to 12 letters and digits (e.g. UP93BK9110). Lowercase letters, spaces and hyphens are accepted and removed before the lookup. Send the registration number, not a challan number.

→ request_id (optional): Your own unique reference for this request. A UUID is generated when omitted and returned as requestId.

Response Details:

→ disposedData: List of challan records that have been resolved/disposed.

→ pendingData: List of challan records that are still pending payment or court hearing.

→ Each record includes: challan number, date/time, place, status, offence details, fine amount, court info.

This API retrieves comprehensive information about vehicle challans (traffic tickets) issued for a specific vehicle. It provides details such as challan numbers, offense descriptions, fine amounts, challan status, and whether the case requires court appearance.

The API allows users to search for challan records across multiple state portals simultaneously by providing the vehicle's RC number, chassis number, and engine number.

Key Benefits:

→ Access challan information from multiple states through a single API call.

→ Retrieve detailed offense information including fine amounts and challan status.

→ Identify court-challaned cases that require legal proceedings.

→ Verify pending traffic violations before vehicle purchases or transfers.

→ Simplify compliance and verification workflows for businesses and platforms.

Use Cases:

→ Pre-purchase vehicle verification to identify outstanding challans.

→ Fleet management companies monitoring driver compliance with traffic laws.

→ Used car dealerships performing due diligence before vehicle acquisition.

→ Insurance and financial institutions verifying vehicle liabilities.

→ Vehicle background verification and compliance checks.

Request Body Parameters:

→ rc_number (required): Vehicle registration number: 2 letters, 1 or 2 digits, 1 to 3 letters, then 1 to 4 digits (e.g. GJ01AB1234). Spaces around the value are trimmed and lowercase is converted to uppercase. Bharat (BH) series numbers are not accepted.

→ chassis_number (required): Chassis number of the vehicle. Trimmed and converted to uppercase.

→ engine_number (required): Engine number of the vehicle. Trimmed and converted to uppercase.

→ state_only (optional): Boolean. When set to true, restricts the search to the portals listed in state_portal.

→ state_portal (optional): Array of state portal codes to search (for example DL, TS, KA, GJ).

→ consent (optional): Defaults to Y.

→ request_id (optional): Your own unique reference for this request. A UUID is generated when omitted.

Response Details:

→ Challan number and challan date/time.

→ Offense details and violation descriptions.

→ Challan location and state details.

→ Fine amount and challan payment status.

→ Court challan indicators and court-related details.

→ Backend source status including successful and failed searches.

→ Vehicle accused name and portal source information.

Flow:

1. Provide the vehicle RC number, chassis number, and engine number.

2. Optionally restrict search to selected state portals.

3. Submit the API request.

4. System fetches challan records from supported state portals.

5. Review pending, disposed, or court challans returned in the response.

6. Use the challan details for verification, compliance, or legal workflows.

This API endpoint allows you to retrieve the mobile number associated with a specific vehicle registration (RC) number. It provides a secure and efficient way to verify the connection between a vehicle and its registered owner's contact information, which is essential for various verification and authentication processes.

Key Benefits:

→ Instant verification of mobile numbers linked to vehicle registration.

→ Reduces manual verification efforts and associated costs.

→ Helps prevent fraud by confirming authentic vehicle-owner relationships.

→ Streamlines customer onboarding for automotive and insurance services.

Use Cases:

→ Vehicle ownership verification during used car transactions.

→ Service center appointment scheduling and customer verification.

→ Automated customer communication for vehicle maintenance alerts.

Request Body Parameters:

→ rc_number (required): Vehicle registration number (e.g. RJ14XJ1234). Any non-empty value is accepted by the API; send it without spaces.

This API endpoint allows you to retrieve the Registration Certificate (RC) numbers associated with a specific mobile number. It provides a convenient way to look up vehicle registration details when only the mobile number of the vehicle owner is available. The service performs a search across the vehicle registration database and returns all RC numbers linked to the provided mobile number.

Key Benefits:

→ Quickly verify vehicle ownership using just a mobile number.

→ Retrieve multiple RC numbers associated with a single mobile number.

→ Simplify vehicle verification processes for financial and insurance services.

→ Reduce manual data entry and potential errors in vehicle identification.

Use Cases:

→ Verify vehicle ownership during loan application processing.

→ Validate collateral information for vehicle-backed loans.

→ Streamline vehicle insurance policy issuance by confirming ownership details.

Request Body Parameters:

→ mobile_number (required): 10-digit mobile number, digits only, with no country code or spaces (e.g. 9876543210).

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:

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

Request Body Parameters:

→ rc_number (required): Vehicle registration number: 2 letters, 1 or 2 digits, 1 to 3 letters, then 1 to 4 digits (e.g. GJ01RV8999). Spaces around the value are trimmed and lowercase is converted to uppercase. Bharat (BH) series numbers are not accepted.