RC To Sale Amount

Endpoint Overview

POST /api/v1/rc/rc-to-sale-amount

Description

The RC to Sale Amount API retrieves the estimated sale amount associated with a vehicle registration certificate (RC) number. By providing a vehicle's RC number, the API returns the corresponding sale amount along with a unique client identifier and the RC number itself.

This endpoint is particularly valuable for financial institutions, insurance providers, used vehicle marketplaces, and automotive lenders who need a quick, programmatic way to assess vehicle valuation based on registration data — without manual lookups or third-party intermediaries.

Key Benefits

Instant Valuation: Retrieve estimated sale amounts in real time using just the vehicle's RC number.

Seamless Integration: RESTful design makes it easy to embed into existing loan origination, insurance underwriting, or vehicle trading workflows.

Dual Environment Support: Test safely in sandbox before going live in production — both environments use JWT-based authentication for consistency.

Reliable Data Output: Structured JSON responses with standardized status codes and message codes simplify downstream processing and error handling.

Use Cases

Financial Services

Insurance

Automotive Marketplace

Auto Loan Underwriting: Determine vehicle sale value at the time of loan application to calculate LTV (Loan-to-Value) ratios accurately.

Asset Valuation for NBFCs: Quickly assess collateral value for secured lending products using RC-based vehicle lookup.

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Follow these steps to authenticate:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token for the target environment.

Include in Requests: Add the token to the Authorization header in the format Bearer <YOUR_JWT_TOKEN>.

Use environment-specific tokens for the corresponding base URLs:

Sandbox: https://sandbox.surepass.app

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

⚠️ Do not use a production JWT token against the sandbox endpoint, or vice versa. Each environment issues its own token.

Request Parameters

Request Headers

Header	Required	Description
`Authorization`	Yes	JWT Bearer token in the format `Bearer <YOUR_JWT_TOKEN>`
`Content-Type`	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
`id_number`	String	Yes	The vehicle's Registration Certificate (RC) number (e.g., `MH00AY1100`)

Example Request

{
    "id_number": "MH00AY1100"
}

Process Response

Response Parameters

Parameter	Type	Description
`data`	Object	Contains the result payload
`data.client_id`	String	A unique identifier generated for this request/transaction
`data.rc_number`	String	The RC number provided in the request, echoed back in the response
`data.sale_amount`	String	The estimated sale amount associated with the provided RC number (in INR, as a numeric string)
`status_code`	Integer	HTTP-equivalent status code for the operation (e.g., `200` for success)
`success`	Boolean	`true` if the request was processed successfully, `false` otherwise
`message`	String	Human-readable message describing the result (e.g., `"Success"`)
`message_code`	String	Machine-readable message code for programmatic handling (e.g., `"success"`)

Example Successful Response

{
    "data": {
        "client_id": "rc_to_sale_amount_gPTlxwbBppomVQlQibuh",
        "rc_number": "MH00AY1100",
        "sale_amount": "6150000.0"
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Unauthorized (401)

Invalid Input (400)

{
    "data": null,
    "status_code": 401,
    "success": false,
    "message": "Authentication credentials were not provided or are invalid.",
    "message_code": "unauthorized"
}

Returned when the Authorization header is missing, malformed, or contains an expired/invalid JWT token. Ensure you are using the correct token for the target environment (sandbox vs. production).

Integration Best Practices

Security Recommendations

Never expose JWT tokens client-side: Always make API calls from your backend server. Embedding tokens in frontend code or mobile apps risks credential compromise.

Rotate tokens regularly: Set up a token refresh schedule and avoid using long-lived tokens in production environments.

Use HTTPS exclusively: Both sandbox and production base URLs use HTTPS. Never downgrade to HTTP for any API interaction.

Restrict token scope: Issue tokens with the minimum required permissions. Avoid using admin-level tokens for endpoint-specific integrations.

Validate id_number before submission: Sanitize and validate the RC number format on your end before calling the API to reduce unnecessary requests and exposure of raw user input.

User Experience Guidelines

Handle loading states gracefully: Since this is a real-time lookup, display a loading indicator while awaiting the response to prevent user confusion.

Display sale_amount with formatting: The sale_amount is returned as a numeric string (e.g., "6150000.0"). Parse and format it (e.g., ₹61,50,000) before presenting to end users.

Provide clear error messaging: Map message_code values to user-friendly messages in your UI (e.g., "not_found" → "We couldn't find a record for this vehicle. Please check the RC number.").

Cache results where appropriate: If the same RC number is queried frequently (e.g., in a dashboard), consider short-lived caching to reduce API calls and improve response time.

Test in sandbox first: Always validate your integration in the sandbox environment using test RC numbers before switching to production credentials.

Code Samples

cURL

Python

Node.js

Related APIs

RC Details API – Fetches comprehensive vehicle registration certificate details including owner name, vehicle model, fuel type, and registration date for a given RC number.

RC Validity Check API – Verifies whether a vehicle's registration certificate is currently valid, expired, or blacklisted.

Vehicle Insurance Verification API – Checks the active insurance policy status linked to a registered vehicle using its RC number.

Chassis Number to RC API – Retrieves RC information by looking up a vehicle's chassis number instead of the registration number.

Compliance and Legal Considerations

Data Privacy: The RC number is a government-issued identifier. Ensure your application collects and stores it in compliance with applicable data protection laws, including India's Digital Personal Data Protection Act (DPDP), 2023.

Authorized Use Only: This API should only be used for legitimate business purposes such as lending, insurance underwriting, or vehicle trade. Unauthorized bulk querying or scraping of vehicle records may violate terms of service and applicable regulations.

Audit Trails: Maintain server-side logs of API calls for audit and dispute resolution purposes, especially in regulated industries like banking and insurance.

User Consent: Ensure you have obtained appropriate consent from vehicle owners before querying their RC-linked data through this API.

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-to-sale-amount' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "id_number": "MH00AY1100" }'

{ "data": { "client_id": "rc_to_sale_amount_gPTlxwbBppomVQlQibuh", "rc_number": "MH00AY1100", "sale_amount": "6150000.0" }, "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