RC Application Status

Endpoint Overview

POST /api/v1/rc/rc-application-status

Description

This API endpoint retrieves comprehensive details about a vehicle registration certificate (RC) application. It provides information about the application's current status, transaction history, and related processes such as HSRP status, fitness certificate printing, smart card generation, and RC dispatch status. This endpoint is particularly useful for tracking the progress of vehicle registration applications through the various stages of processing within the RTO (Regional Transport Office) system.

Key Benefits

Real-time tracking of RC application status through the entire approval workflow

Comprehensive view of all transactions related to a specific application

Visibility into supplementary processes like smart card generation and dispatch

Single API call to retrieve complete application history and current status

Use Cases

Automotive

Financial Services

Government & Compliance

Vehicle dealerships tracking registration status for newly sold vehicles

Fleet management companies monitoring registration renewals and transfers

Automotive marketplaces verifying registration status during vehicle transactions

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	JWT Bearer token for authentication. Format: `Bearer <your_token>`
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
application_number	String	Yes	The unique application number for the RC application you want to query

Example Request

{
    "application_number": "GJ210409V123654"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Contains the response data
data.client_id	String	Unique identifier for the client making the request
data.application_number	String	The application number that was queried
data.details	Object	Comprehensive details about the application
data.details.application_dated	String	Date when the application was submitted
data.details.application_time	String	Time when the application was submitted
data.details.vehicle_number	String	Registration number of the vehicle
data.details.transactions	Array	List of transactions related to the application
data.details.other_transactions	Array	Additional related transactions and statuses
status_code	Number	HTTP status code of the response
success	Boolean	Indicates if the request was successful
message	String	Additional message (null if successful)
message_code	String	Code indicating the status of the request

Transaction Object Structure

Parameter	Type	Description
s_no	String	Serial number of the transaction
transaction_purpose	String	Purpose of the transaction
authentication_type	String	Type of authentication used
current_status	String	Current status with timestamp and details
portal_name	String	Name of the portal where transaction occurred

Other Transactions Object Structure

Parameter	Type	Description
hsrp_status	String	Status of High-Security Registration Plate
fc_print	String	Status of Fitness Certificate printing
rc_print_smart_card_status	String	Status of RC Smart Card generation
dispatch_rc_status	String	Status of RC dispatch with tracking details

Example Successful Response

{
    "data": {
        "client_id": "rc_application_status_hIWfcPDsxtGzqdDqbOvV",
        "application_number": "GJ210409V123654",
        "details": {
            "application_dated": "09-Apr-2021",
            "application_time": "12:30:10",
            "vehicle_number": "GJ01RZ1234",
            "transactions": [
                {
                    "s_no": "1",
                    "transaction_purpose": "Additional LTT (TO Case)",
                    "authentication_type": "RTO",
                    "current_status": "ONLINE TRANSACTION SUCCESS ON 09-Apr-2021 12:30:10 .TRANSACTION COMPLETE.",
                    "portal_name": "ONLINE SERVICE"
                },
                {
                    "s_no": "2",
                    "transaction_purpose": "Smart Card Fee",
                    "authentication_type": "RTO",
                    "current_status": "ONLINE TRANSACTION SUCCESS ON 09-Apr-2021 12:30:10 .TRANSACTION COMPLETE.",
                    "portal_name": "ONLINE SERVICE"
                },
                {
                    "s_no": "3",
                    "transaction_purpose": "Transfer of Ownership",
                    "authentication_type": "RTO",
                    "current_status": "COMPLETED / APPROVED ON 15-Apr-2021 18:29:48 by user D B PATEL",
                    "portal_name": "ONLINE SERVICE"
                }
            ],
            "other_transactions": [
                {
                    "hsrp_status": "Not Available",
                    "fc_print": "Not Available",
                    "rc_print_smart_card_status": "SMART CARD Generated  28-Apr-2021 12:58:48 by user SMARTCARD VENDOR",
                    "dispatch_rc_status": "DISPATCH RC Generated [ApplNo/Barcode: GJ210409V123654/EG12345678IN] dated 30-Apr-2021 10:47:57 by user SILVER TOUCH TECH LTD"
                }
            ]
        }
    },
    "status_code": 200,
    "success": true,
    "message": null,
    "message_code": "success"
}

Possible Error Responses

Invalid Application Number

Authentication Error

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

The application number provided is invalid or in an incorrect format.

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 gracefully

Validate and sanitize the application number before sending to prevent injection attacks

Implement proper error handling to avoid exposing sensitive information in error messages

User Experience Guidelines

Implement a user-friendly status tracking interface that translates technical status codes into plain language

Display transaction history in chronological order with clear timestamps

Provide estimated completion times based on the current status of the application

Implement notifications for status changes to keep users informed throughout the process

Code Samples

cURL

Python

Node.js

Related APIs

RC Details API: Retrieves comprehensive details of a registered vehicle

RC Verification API: Verifies the authenticity of a registration certificate

RC History API: Provides historical records of a vehicle's registration

RC Owner API: Retrieves information about the current owner of a vehicle

Compliance and Legal Considerations

This API provides access to vehicle registration data which may be subject to privacy regulations. Ensure you have proper consent from the vehicle owner or legal authority to access this information. Usage of this data must comply with the Motor Vehicles Act and related regulations. Data retrieved should not be stored longer than necessary for the intended purpose and must be protected with appropriate security measures.

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/rc/rc-application-status' \ --header 'Content-Type: application/json' \ --data-raw '{ "application_number": "GJ210409V123654" }'

{ "data": { "client_id": "rc_application_status_hIWfcPDsxtGzqdDqbOvV", "application_number": "GJ210409V123654", "details": { "application_dated": "09-Apr-2021", "application_time": "12:30:10", "vehicle_number": "GJ01RZ1234", "transactions": [ { "s_no": "1", "transaction_purpose": "Additional LTT (TO Case)", "authentication_type": "RTO", "current_status": "ONLINE TRANSACTION SUCCESS ON 09-Apr-2021 12:30:10 .TRANSACTION COMPLETE.", "portal_name": "ONLINE SERVICE" }, { "s_no": "2", "transaction_purpose": "Smart Card Fee", "authentication_type": "RTO", "current_status": "ONLINE TRANSACTION SUCCESS ON 09-Apr-2021 12:30:10 .TRANSACTION COMPLETE.", "portal_name": "ONLINE SERVICE" }, { "s_no": "3", "transaction_purpose": "Transfer of Ownership", "authentication_type": "RTO", "current_status": "COMPLETED / APPROVED ON 15-Apr-2021 18:29:48 by user D B PATEL", "portal_name": "ONLINE SERVICE" } ], "other_transactions": [ { "hsrp_status": "Not Available", "fc_print": "Not Available", "rc_print_smart_card_status": "SMART CARD Generated 28-Apr-2021 12:58:48 by user SMARTCARD VENDOR", "dispatch_rc_status": "DISPATCH RC Generated [ApplNo/Barcode: GJ210409V123654/EG12345678IN] dated 30-Apr-2021 10:47:57 by user SILVER TOUCH TECH LTD" } ] } }, "status_code": 200, "success": true, "message": null, "message_code": "success" }

RC Application Status

RC Application Status#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Transaction Object Structure#

Other Transactions Object Structure#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses

RC Application Status

Description

Use Cases

Technical Implementation

Request Headers

Request Body

Example Request

Response Parameters

Transaction Object Structure

Other Transactions Object Structure

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples