Basic Challan Search (MH OTP Entering API)
Introduction
This service is used to retrieve Maharastra Challans along with Central Challans based on OTP validation.
How to call the API
You will need to log in 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
OTP and Session ID are the mandatory parameters to be passed.
Sample Curl
curl --location 'https://api-preproduction.signzy.app/api/v3/vehicle/mh-challans' \
--header 'Authorization: <access-token>' \
--header 'Content-Type: application/json' \
--data '{
"otp": "<sample-otp>",
"sessionId":"<sample-session-id>"
}'Input Field Name | Description | Type | Optional |
|---|---|---|---|
otp | OTP recevied to the user | string | no |
sessionId | Session ID for the particular session | string | no |
Sample Response
{
"result": {
"regNo": "MH01AE6830",
"message": "Challan Details Found",
"status_code": 200,
"challanDetails": [
{
"number": 1,
"challanNumber": "HSPCC22001816416",
"offenseDetails": "Speed violating by driver (LMV)",
"challanPlace": "",
"challanDate": "26/07/2022",
"state": "MH",
"rto": "",
"accusedName": "SAMADHAN ANNA MORE",
"amount": "2000",
"challanStatus": "Paid",
"court_challan": "",
"challanSource": "MH"
},
{
"number": 2,
"challanNumber": "HSPCM22004101996",
"offenseDetails": "Causing danger/Obstructions/Undue inconvenience to other users of public place or to the passengers by allowing the vehicle to be abandoned or to remain at rest on any public place.",
"challanPlace": "",
"challanDate": "19/05/2022",
"state": "MH",
"rto": "",
"accusedName": "SAMADHAN ANNA MORE",
"amount": "500",
"challanStatus": "Paid",
"court_challan": "",
"challanSource": "MH"
},
{
"number": 3,
"challanNumber": "HSPCC22000962266",
"offenseDetails": "Speed violating by driver (LMV)",
"challanPlace": "",
"challanDate": "13/04/2022",
"state": "MH",
"rto": "",
"accusedName": "SAMADHAN ANNA MORE",
"amount": "2000",
"challanStatus": "Paid",
"court_challan": "",
"challanSource": "MH"
},
{
"number": 4,
"challanNumber": "MTPCHM1700185058",
"offenseDetails": "Police stop violation",
"challanPlace": "",
"challanDate": "02/02/2017",
"state": "MH",
"rto": "",
"accusedName": "SAMADHAN ANNA MORE",
"amount": "200",
"challanStatus": "Paid",
"court_challan": "",
"challanSource": "MH"
}
],
"successfulSources": [
"ECHALLAN",
"MH"
],
"failedSources": []
}
}Response Parameter
Parameter Name | Description |
|---|---|
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 |
successfulSources | Sources from which we can fetch the challans successfully. |
failedSources | Sources from which we are not able to fetch the challans successfully. |
Status Codes
CODE | MESSAGE |
|---|---|
200 | Successful Response |
400 | Invalid Input / OTP is expired |
401 | No API key found in request |
409 | Error in fetching data from upstream |
Invalid Input Responses
{
"error": {
"name": "error",
"message": "Invalid Input",
"status": 400,
"reason": "ERROR",
"type": "Bad Request",
"statusCode": 400
}
}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].