What does the Reverse RC API do?
The Reverse RC API verifies vehicle details using the Chassis Number and optionally the Engine Number. It provides a real-time, paperless alternative to manual vehicle verification, returning registration, insurance, permit, and owner details from the RC database.
This service is provided by Zoop on the ULI Platform.
Who can use this API?
Lenders onboarded to the ULI Platform who have subscribed to the RC Reverse service on the Dev Portal. Separate subscriptions are required for Sandbox and Production environments.
What are the prerequisites before I can use this API?
Complete all common platform prerequisites (IP whitelisting, URL whitelisting, credentials, service subscription, and JWT token generation) as described in Getting Started with ULI Platform APIs.
In addition, this API requires Zoop-specific credentials:
- x-zoop-api-key — A unique API key generated by Zoop for your organisation.
- x-zoop-app-id — A unique App ID generated by Zoop for your organisation.
Contact the support team at support@rbihub.in to get these credentials provisioned.
What are the API endpoints?
| Environment | URL |
|---|---|
| Sandbox | https://extgw.nonprod.rbihub.io/zoop/rcreverse/1.0/en |
| Production | https://extgw.api.rbihub.io/zoop/rcreverse/1.0/en |
Method: POST
What headers do I need to send?
| Header | Description |
|---|---|
Authorization | JWT token from the authentication server |
client-id | Your Client ID (Base64 encoded), provided during registration |
provider | Set to 134 for Zoop |
x-zoop-api-key | Zoop API key assigned to your organisation |
x-zoop-app-id | Zoop App ID assigned to your organisation |
x-env-route | Set to /sb for Sandbox only; omit for Production |
What do I send in the request body?
| Field | Required | Description |
|---|---|---|
chassis_number | Mandatory | Chassis number of the vehicle. Max 23 characters. Special characters allowed: ~ / * -. Not case sensitive. |
engine_number | Optional | Engine number of the vehicle. If provided, must not be empty or whitespace only. Not case sensitive. |
consent | Mandatory | Customer's consent for verification. Must be set to Y to proceed. |
consent_text | Mandatory | Text shown to the user while obtaining consent. Min 20 characters, max 200 characters. |
task_id | Mandatory | Unique identifier for the API call. Must be in UUIDv4 format. |
ts | Mandatory | Timestamp in ISO-8601 format (yyyy-MM-ddTHH:mm:ssZ) |
txncode | Mandatory | Unique transaction code provided by the lender |
ver | Mandatory | API version — set to 1.0 |
data | Mandatory | Base64 encoded XML payload. Sample XML will be shared by the support team. |
hmac | Mandatory | SHA-256 hash of the value under the data key |
What does the response contain?
On success, the response includes the following vehicle details:
| Field | Description |
|---|---|
rc_registration_number | Vehicle's registration number |
rc_status | Current registration certificate status |
rc_expiry_date | RC expiry date |
rc_chassis_number | Masked chassis number |
rc_engine_number | Masked engine number |
vehicle_make_model | Vehicle model and variant |
vehicle_fuel_description | Fuel type |
vehicle_type | Type of vehicle (e.g., 2W, 4W) |
vehicle_financed | Whether the vehicle is financed (Y/N) |
financer | Name of the loan financer |
insurance.policy_number | Insurance policy number |
insurance.expiry_date | Insurance expiry date |
insurance.company | Insurance company name |
insurance_expired | Whether insurance has expired |
rc_permit_number | Vehicle permit number |
rc_permit_type | Type of vehicle permit |
rc_fit_upto | Fitness certificate validity date |
rc_tax_upto | Tax paid up to date |
norms_description | Emission/pollution norms (e.g., BS6) |
user_name | Name of the vehicle owner/user |
state | State where the vehicle is registered |
rc_rto_code | RTO code for registration |
challan[] | List of challans including amount, date, status, and challan number |
What do the error codes mean?
| Error Code | Message |
|---|---|
| EZP001 | System Error |
| EZP002 | Invalid request structure |
| EZP003 | Invalid JSON format |
| EZP004 | External service error |
| EZP005 | Network connectivity issue |
| EZP006 | Communication Error |
| EZP007 | Empty response from external service |
| EZP020 | Please provide consent as Y or N |
| EZP021 | Please provide consent_text |
| EZP022 | Please provide task_id |
| EZP023 | Please provide valid Chassis Number |
| EZP024 | Please provide valid engine number |
Provider errors are mapped to platform error code E043. Refer to the Platform Error Code PDF for the full list of platform error codes.
Who do I contact if the API fails?
Write to support@rbihub.in with the following details:
- Service name:
RC Reverse (Zoop) - Environment: Sandbox or Production
- Provider code:
134 - Full request payload (headers + body)
- Error code and message received
- Screenshot or log of the error
- Status of prerequisites: IP whitelisting, URL whitelisting, service subscription, token generation
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article