data.vehicle.registration_number
Vehicle identifier used to associate the lookup.
Vehicle lookup capability
Combine challan summaries with vehicle identity, RC status and registration context in one review.
Use this view when your challan workflow also needs vehicle context. It brings the Vehicle Info challan summary together with registration, vehicle class, make/model, RC status and registering-office details. Advance here describes the combined review view; it does not introduce an additional challan endpoint or undocumented violation fields.
Vehicle identifier used to associate the lookup.
Make, model and vehicle classification context.
Returned registration and blacklist labels.
Registering-office context.
Returned challan counts and pending-amount totals.
Available record container; detailed record fields need a non-empty production example.
The preview shows the relevant portion of the RTO Vehicle Info response. The underlying request returns the full response; this is not a separate filtered endpoint. Sample data is fictional.
GET https://api.cstudio.sbs/v1/rto/vehicle-info?vehicle_number=MH12AB1234
Use GET /v1/rto/vehicle-info with vehicle_number. Read the relevant fields from data after the response succeeds.
curl -X GET "https://api.cstudio.sbs/v1/rto/vehicle-info?vehicle_number=MH12AB1234" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json"{
"status": "success",
"success": true,
"registration_number": "MH12AB1234",
"data": {
"regNo": "MH12AB1234",
"rc_status": "ACTIVE",
"blacklist_status": "CLEAN",
"vehicle": {
"registration_number": "MH12AB1234",
"owner_name": "AARAV DESAI",
"owner_count": "1",
"maker": "MARUTI SUZUKI INDIA LTD",
"model": "BALENO DELTA 1.2",
"maker_model": "MARUTI SUZUKI INDIA LTD BALENO DELTA 1.2",
"vehicle_class": "Motor Car(LMV)",
"fuel_type": "PETROL",
"color": "SILVER",
"cubic_capacity": "1197",
"seating_capacity": "5",
"manufacturing_date": "08/2022",
"registration_date": "15-Sep-2022",
"rc_status": "ACTIVE",
"blacklist_status": "CLEAN",
"financer": "",
"hypothecation_status": "NONE (Self-Financed / Unencumbered)",
"present_address": "42, Maple Residency, Baner, Pune, Maharashtra, 411045",
"permanent_address": "42, Maple Residency, Baner, Pune, Maharashtra, 411045",
"registered_address": "42, Maple Residency, Baner, Pune, Maharashtra, 411045"
},
"rto_details": {
"rto": "Pune, Maharashtra",
"rto_code": "MH-12",
"rto_phone": "",
"rto_website": "https://example.com/rto",
"state": "Maharashtra"
},
"challan": {
"summary": {
"total_challans": 0,
"has_pending_challans": false,
"pending_challan_count": 0,
"total_pending_amount": 0,
"total_pending_amount_formatted": "₹0.00"
},
"records": []
}
}
}Give operations teams vehicle identity and challan totals on the same screen.
Compare returned vehicle context with the registration being handed over.
Same plans as RTO Vehicle Info. These fields are available through the same vehicle lookup; separate requests are not needed for each response group.
Need high-concurrency throughput, custom rate limits, dedicated IP whitelisting, or bundled multi-API volume?
It shows how to combine challan fields with vehicle and registration context already present in Vehicle Info. It is a focused view of that response, not a separate data source.