RC Vehicle Service History

Endpoint Overview

POST /api/v1/rc/vehicle-service-history

Description

The RC Vehicle Service History API provides comprehensive service and maintenance records for vehicles registered in India. This endpoint retrieves detailed historical data about service visits, repairs, and maintenance activities performed at authorized dealerships for supported vehicle manufacturers including Maruti, Hyundai, and Mahindra.

This API enables businesses to access verified service history information using the vehicle's registration number (RC number), providing insights into the vehicle's maintenance patterns, service costs, dealer interactions, and overall upkeep. The data is sourced directly from authorized service centers, ensuring accuracy and reliability for informed decision-making in vehicle-related transactions and assessments.

Key Benefits

Comprehensive Service Records: Access detailed service history including dates, costs, mileage, and service types from authorized dealerships

Multi-Manufacturer Support: Retrieve service data for three major Indian automobile manufacturers (Maruti, Hyundai, and Mahindra)

Transaction-Level Details: Get granular information about each service visit including labor costs, parts costs, and payment methods

Dealer Network Insights: Obtain complete dealer information including location, codes, and service advisor details for verification purposes

Use Cases

Used Car Industry

Insurance Sector

Fleet Management

Pre-Purchase Vehicle Inspection: Verify service history and maintenance records before purchasing used vehicles to assess vehicle condition and validate seller claims

Vehicle Valuation: Determine accurate market value based on documented service patterns, maintenance frequency, and total service expenditure

Dealer Inventory Management: Screen and categorize incoming vehicles based on service history quality for better pricing and faster turnover

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
id_number	String	Yes	Vehicle registration number (RC number) without spaces or special characters (e.g., "DL11CF3XXX")
maker	String	Yes	Vehicle manufacturer name. Must be one of: `"maruti"`, `"hyundai"`, or `"mahindra"`.

Example Request

{
    "id_number": "DL11CF3XXX",
    "maker": "maruti"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Container object holding all response data
data.client_id	String	Unique identifier for the API request transaction
data.id_number	String	Vehicle registration number that was queried
data.maker	String	Vehicle manufacturer name as provided in the request
data.service_history_details	Array	Array of service history records for the vehicle
service_history_details[].dealer_name	String	Name of the authorized dealership where service was performed
service_history_details[].dealer_number	String	Unique identification number assigned to the dealer
service_history_details[].location_code	String	Three-letter code representing the dealer's location
service_history_details[].service_date	String	Date when the service was performed (format: YYYY-MM-DD)
service_history_details[].service_type	String	Type of service performed (e.g., "SERVICE", "REPAIR")
service_history_details[].mileage	String	Vehicle odometer reading at the time of service
service_history_details[].type_of_payment	String	Payment method used for the service transaction
service_history_details[].total_amount	String	Total bill amount for the service including all charges
service_history_details[].labour_amount	String	Amount charged for labor/service work
service_history_details[].part_amount	String	Amount charged for parts and materials
service_history_details[].bill_date	String	Date when the bill was generated (format: YYYY-MM-DD)
service_history_details[].repair_order_date	String	Date when the repair order was created (format: YYYY-MM-DD)
service_history_details[].dealer_address	String	Complete address of the service dealership
service_history_details[].group_of_parent	String	Parent group or organization code for the dealer
service_history_details[].vehicle_code	String	Internal vehicle classification code
service_history_details[].service_advisor	String	Name of the service advisor who handled the service
service_history_details[].job_card_number	String	Unique job card number assigned to the service task
service_history_details[].chassis_number	String	Vehicle chassis number (VIN)
service_history_details[].location_name	String	Full name of the service location
service_history_details[].net_bill_amount	String	Net amount after discounts and adjustments
service_history_details[].online_payment_flag	String	Indicator for online payment transaction
service_history_details[].outstanding_amount	String	Any outstanding balance remaining on the service bill
service_history_details[].paid_amount	String	Amount that has been paid toward the service bill
service_history_details[].dealer_code	String	Official dealer code in the manufacturer's network
service_history_details[].repair_order_bill_date	String/Null	Date of the repair order bill if applicable
service_history_details[].repair_order_bill_number	String	Bill number associated with the repair order
service_history_details[].register_number	String	Vehicle registration number from dealer records
service_history_details[].service_assistant_number	String	Contact number of the service assistant
service_history_details[].service_assistant_name	String	Name of the service assistant
service_history_details[].work_type	String	Classification of the work performed
service_history_details[].status	String	Current status of the service order
service_history_details[].service_category	String	Category classification of the service
service_history_details[].repaid_order_number	String	Reference number for repaid service orders
service_history_details[].repair_order_number	String	Unique repair order identification number
status_code	Integer	HTTP status code of the response (200 for success)
success	Boolean	Indicates whether the request was successful (true/false)
message	String	Human-readable message describing the response status
message_code	String	Machine-readable code for the response message

Example Successful Response

{
    "data": {
        "client_id": "rc_vehicle_service_history_vWbhnPurkxxNsmjpxYVA",
        "id_number": "DL11CF3XXX",
        "maker": "maruti",
        "service_history_details": [
            {
                "dealer_name": "RAM AUTOMOTIVES",
                "dealer_number": "15XXX",
                "location_code": "JUP",
                "service_date": "2025-01-01",
                "service_type": "SERVICE",
                "mileage": "11XX",
                "type_of_payment": "",
                "total_amount": "3300",
                "labour_amount": "0",
                "part_amount": "3300",
                "bill_date": "2025-01-01",
                "repair_order_date": "2025-01-01",
                "dealer_address": "123 INDUSTRIAL AREA, NEW DELHI",
                "group_of_parent": "JAAUP",
                "vehicle_code": "FR1",
                "service_advisor": "RAMESH LOHIYA",
                "job_card_number": "JC250123456",
                "chassis_number": "",
                "location_name": "",
                "net_bill_amount": "",
                "online_payment_flag": "",
                "outstanding_amount": "",
                "paid_amount": "",
                "dealer_code": "",
                "repair_order_bill_date": null,
                "repair_order_bill_number": "",
                "register_number": "",
                "service_assistant_number": "",
                "service_assistant_name": "",
                "work_type": "",
                "status": "",
                "service_category": "",
                "repaid_order_number": "",
                "repair_order_number": "BR/25012345"
            }
        ]
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid Maker

Authentication Error

{
    "status_code": 400,
    "success": false,
    "message": "Invalid maker. Allowed values are: maruti, hyundai, mahindra",
    "message_code": "invalid_maker"
}

This error occurs when the maker parameter contains a value other than the three accepted manufacturers. Verify that the maker field is spelled correctly and uses one of the allowed values.

Integration Best Practices

Security Recommendations

Token Management: Store JWT tokens securely using environment variables or secure key management systems. Never hardcode tokens in client-side code or version control

HTTPS Only: Always use HTTPS protocol for API requests to encrypt data in transit and prevent man-in-the-middle attacks

Rate Limiting: Implement exponential backoff and retry logic to handle rate limits gracefully and avoid overwhelming the API

Data Encryption: Encrypt sensitive vehicle information at rest in your database and implement proper access controls

Token Rotation: Regularly rotate JWT tokens and implement token expiration monitoring to maintain security posture

User Experience Guidelines

Input Validation: Validate registration numbers on the client side before making API calls to reduce unnecessary requests and provide immediate feedback

Loading States: Implement clear loading indicators while fetching service history, as data retrieval may take several seconds

Error Messaging: Display user-friendly error messages that guide users on how to correct input errors or troubleshoot issues

Data Presentation: Present service history in chronological order with clear visual separation between service records for easy scanning

Empty States: Design informative empty state screens when no service history is found, suggesting possible reasons or next steps

Progressive Disclosure: Consider displaying summary information first, then allowing users to expand individual service records for detailed information

Code Samples

cURL

Python

Node.js

Related APIs

RC Verification API - Validate vehicle registration details and ownership information for comprehensive vehicle verification
Vehicle Insurance Verification - Cross-check insurance status and policy details with service history for complete vehicle assessment
Vehicle Valuation API - Determine accurate vehicle market value using service history data combined with market trends
RC Owner Details - Retrieve registered owner information to verify vehicle ownership history

Compliance and Legal Considerations

This API provides access to vehicle service records that may contain sensitive information. Users must ensure compliance with applicable data protection regulations including the Information Technology Act, 2000 and Digital Personal Data Protection Act, 2023. Service history data should be used only for legitimate business purposes with appropriate user consent. Organizations must implement proper data retention policies and ensure secure storage of retrieved information. Any commercial use of this data must comply with the terms of service and licensing agreements with Surepass. The API should not be used for unauthorized surveillance or tracking purposes.

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/vehicle-service-history' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "id_number": "DL11CF3XXX", "maker": "maruti" }'

{ "data": { "client_id": "rc_vehicle_service_history_vWbhnPurkxxNsmjpxYVA", "id_number": "DL11CF3XXX", "maker": "maruti", "service_history_details": [ { "dealer_name": "RAM AUTOMOTIVES", "dealer_number": "15XXX", "location_code": "JUP", "service_date": "2025-01-01", "service_type": "SERVICE", "mileage": "11XX", "type_of_payment": "", "total_amount": "3300", "labour_amount": "0", "part_amount": "3300", "bill_date": "2025-01-01", "repair_order_date": "2025-01-01", "dealer_address": "123 INDUSTRIAL AREA, NEW DELHI", "group_of_parent": "JAAUP", "vehicle_code": "FR1", "service_advisor": "RAMESH LOHIYA", "job_card_number": "JC250123456", "chassis_number": "", "location_name": "", "net_bill_amount": "", "online_payment_flag": "", "outstanding_amount": "", "paid_amount": "", "dealer_code": "", "repair_order_bill_date": null, "repair_order_bill_number": "", "register_number": "", "service_assistant_number": "", "service_assistant_name": "", "work_type": "", "status": "", "service_category": "", "repaid_order_number": "", "repair_order_number": "BR/25012345" } ] }, "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