Challan Search
Introduction
This service is used for retrieving the Challan details imposed on a vehicle by entering the Vehicle number.
How to call the API
You will need to login before sending the request. You are required to pass the access token received from the login call, as the authorization header in the request.
API Input Guidelines
Vehicle Number is Mandatory parameter to be passed. State Portal is an Optional parameter.
In case you need to get Maharastra Challans, please provide the consent in mhChallanConsentBased parameter and please provide the phone number which is associated with that particular vehicle number in phoneNoForOtpMH parameter. As fetching Maharashtra challans is OTP consent based flow, we will need OTP. For that, Basic Challan Search (MH OTP Entering API) will be used.
Sample Curl
curl --location 'https://api-preproduction.signzy.app/api/v3/vehicle/challan-search' \
--header 'Authorization: <auth-token>' \
--header 'Content-Type: application/json' \
--data '{
"statePortal": "<state_parameter_to_search_for_challan"
"vehicleNumber": "<regno>",
"mhChallanConsentBased": true,
"phoneNoforOtpMH": "<phone number>",
"paymentCheck": "<true/false>"
}'Input Parameters
Parameter Name | Required/Optional | Description |
|---|---|---|
Content-Type | Required | application/json |
Authorization | Required | Contains the id parameter returned from the login step |
vehicleNumber  | Required | The vehicle number on which the chalan has been imposed |
statePortal | Optional | Provide the state parameter in which you want to search for the challan of the specified vehicle. |
mhChallanConsentBased | Optional | Provide consent to fetch Maharastra Challan |
phoneNoforOtpMH | Optional | Provide phone number associated with the given vehicle number |
paymentCheck | Optional | To get details where the challan is payable (Offline / Online) |
State Portal Field Information
When you search for a paritcular vehicle, by default we will check both central and that particular state's sources.
for e.g When you search for KA vehicle, KA and central source will be checked by default. But, if you want to find if this vehicle has any challans on MP state's sources then you need to pass MP as variable in statePortal field.
Note :- Every extra parameter that you will pass in statePotal field will lead to increase in latency of API as now need to check more sources to get the data.
State Portal Field
State | Whether we are covering it (Yes/No) | Whether we need to pass a value in Stateportal field (Yes/No) | Remarks | More Information |
|---|---|---|---|---|
Central (ECHALLAN) | Yes | No |  |  |
TS | Yes | Yes (TS) |  |  |
AP | Yes | Yes(AP) |  |  |
MP | Yes | Yes(MP) |  |  |
JH | Yes | Yes(JH) |  |  |
MH | Yes | Yes(MH) |  | It has been consent based now. OTP is required for MH state challans |
KA | Yes | Yes(KA) |  |  |
WB | Yes | Yes (WB) |  |  |
GJ | Yes | Yes (GJ) |  |  |
DL | Yes | Yes(DL) |  |  |
Sample Response
{
"result": {
"regNo": "<vehicle no>",
"message": "Challan Details Found",
"status_code": 200,
"challanDetails": [
{
"number": 1,
"challanNumber": "DL5206500251222094449",
"offenseDetails": "WITHOUT VALID POLLUTION CERTIFICATE",
"challanPlace": "VIVEK VIHAR",
"challanDate": "09/12/2025",
"state": "DL",
"rto": "TRANSPORT DEPARTMENT",
"accusedName": "A****A S**D M***K",
"amount": "10000",
"challanStatus": "Pending",
"court_challan": "1",
"challanSource": "ECHALLAN",
"paymentSource": "<challan>"
},
{
"number": 2,
"challanNumber": "UP36257200812191236",
"offenseDetails": "violation of parking rules.",
"challanPlace": "",
"challanDate": "12/08/2020",
"state": "UP",
"rto": "Noida, Gautam Buddha Nagar",
"accusedName": "A****A S**D M***K",
"amount": "1500",
"challanStatus": "Pending",
"court_challan": "1",
"challanSource": "ECHALLAN",
"paymentSource": "<challan>"
},
{
"number": 3,
"challanNumber": "UP36300200120104334",
"offenseDetails": "violation of parking rules.",
"challanPlace": "",
"challanDate": "20/01/2020",
"state": "UP",
"rto": "Noida, Gautam Buddha Nagar",
"accusedName": "A****A S**D M***K",
"amount": "500",
"challanStatus": "Pending",
"court_challan": "1",
"challanSource": "ECHALLAN",
"paymentSource": "<challan>"
},
{
"number": 4,
"challanNumber": "53656813",
"offenseDetails": "OVER SPEED (Light Motor Vehicle)",
"challanPlace": "MATHURA ROAD - HARKESH NGR - CRRI FROM ASHRAM TO SARITA VIHAR",
"challanDate": "08/03/2023",
"state": "DL",
"rto": "",
"accusedName": "A****A S**D M***K",
"amount": "2000",
"challanStatus": "",
"court_challan": "0",
"challanSource": "DL",
"paymentSource": "<challan>"
}
],
"successfulSources": [
"ECHALLAN",
"DL"
],
"failedSources": []
}
}Sample Response (In case wrong phone number is provided for MH challan)
{
"result": {
"regNo": "<vehicle_number_provided>",
"message": "Challan Details Found",
"status_code": 200,
"challanDetails": [
{
"number": 1,
"challanNumber": "SRD01LG222636667",
"offenseDetails": "Over speeding/ Dangerous Driving",
"challanPlace": "SADASIVPET BYPASS ROAD NH 65",
"challanDate": "03/04/2022",
"state": "TS",
"rto": "TS",
"accusedName": "",
"amount": 1000,
"challanStatus": "Not paid",
"court_challan": "",
"challanSource": "ECHALLAN"
},
{
"number": 2,
"challanNumber": "SRD01LG223420660",
"offenseDetails": "Over speeding/ Dangerous Driving",
"challanPlace": "SADASIVPET BYPASS ROAD NH 65",
"challanDate": "06/05/2022",
"state": "TS",
"rto": "TS",
"accusedName": "",
"amount": 1000,
"challanStatus": "Not paid",
"court_challan": "",
"challanSource": "ECHALLAN"
}
],
"MhChallanPhoneNumbers": [
"<list_of_phone_numbers_associated_with_that_vehicle_number>"
],
"successfulSources": [
"ECHALLAN"
],
"failedSources": [
"MH"
]
}
}Sample Response (In case consent is provided for MH challan)
{
"message: "OTP sent successfuly",
"sessionID": "<session id>"
}
ChallanStatus Possible Values :-
- Pending
- Paid
- Not Paid
- Cash
- Disposed
- Null
- Empty Strings
- Unpaid
Response Parameter
Parameter Name | Description |
|---|---|
id | The unique token returned after login |
result | This parameter contains the actual output |
result.regNo | Contains vehicle registration number |
result.message | Shows the message "Challan Details Found" |
result.status_code | Shows the status of response |
result.challanDetails.number | Shows the number of challans imposed |
result.challanDetails.challanNumber | Shows the particular challan number |
result.challanDetails.offenseDetails | Contains details of particular offense |
result.challanDetails.challanPlace | Informs about the place where the challan has been imposed |
result.challanDetails.challanDate | Informs about the date when the challan has been imposed Informs about the place where challan has been imposed Informs about the place where challan has been imposed |
result.challanDetails.state | Informs about the State where the challan has been imposed |
result.challanDetails.rto | Contains the details of the RTO Authority |
result.challanDetails.accusedName | Informs about the name of the accused person |
result.challanDetails.amount | Shows the fine amount for infringement |
result.challanDetails.challanStatus | Shows the status of how the challan has been paid eg. cash |
result.challanDetails.court_challan | Whether court challan or not |
result.challanDetails.challanSource | Gives the source of the Challan API |
result.challanDetails.courtName | Name of the Court where challan is Present |
MhChallanPhoneNumbers | Gives the list of phone numbers associated with the vehicle number provided (Can be seen only when mhChallanConsentBased is true) |
successfulSources | Sources from which we can fetch the challans successfully. |
failedSources | Sources from which we are not able to fetch the challans successfully. |
Status Code
CODE | MESSAGE |
|---|---|
200 | Successful Response |
400 | Bad Request |
401 | No API key found in request |
409 | Error in getting data |
Invalid Input Responses
{
"error": {
"name": "error",
"message": "Error in getting data",
"status": 409,
"reason": "CONFLICT",
"type": "Conflict",
"statusCode": 409
}
}Getting help
Please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better.
You can reach out to us at [email protected].