POSTE-Challan Verification

Fetch pending traffic challans for any vehicle using its registration number — challan number, offence, fine amount, date, status, and issuing authority returned in a single API call.

POST/tools/kyc/touras/e-challan

Send a vehicle registration number to the E-Challan Verification API and receive a complete list of pending traffic violations from the national e-challan system (Parivahan). The response includes each challan's unique number, offence description, fine amount, date of violation, payment status, and issuing state/authority. Use it to automate fleet compliance checks, assess driver risk during onboarding, support motor insurance underwriting, or surface challan data in used-vehicle platforms.

Body parameters

Field	Type	Required	Description
`initiator_id`	string	required	Registered mobile number of the API user (see Platform Credentials).e.g. 9962981729
`user_code`	string	required	User code of the retailer/agent the service is run for.e.g. 20810200
`client_ref_id`	string	optional	Unique reference id per API call, generated by your system.e.g. REQ-20260101-001
`registration_number`	string	required	Vehicle registration number to look up challans for (e.g. MH02AB1234).e.g. MH02AB1234

initiator_idstringRequired

Registered mobile number of the API user (see Platform Credentials).

example: 9962981729

user_codestringRequired

User code of the retailer/agent the service is run for.

example: 20810200

client_ref_idstringoptional

Unique reference id per API call, generated by your system.

example: REQ-20260101-001

registration_numberstringRequired

Vehicle registration number to look up challans for (e.g. MH02AB1234).

example: MH02AB1234

Headers

Field	Type	Required	Description
`developer_key`	string	required	Static API key issued to your account after KYC.
`secret-key`	string	required	Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
`secret-key-timestamp`	string	required	Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
`content-type`	string	required	application/jsone.g. application/json

developer_keystringRequired

Static API key issued to your account after KYC.

secret-keystringRequired

Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).

secret-key-timestampstringRequired

Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.

content-typestringRequired

application/json

example: application/json

Responses

statusnumber
Primary success indicator (0 = success).
messagestring
Human-readable response / error message.
response_status_idnumber
Granular status id; see the shared error-codes table.
response_type_idnumber
A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.
dataobject
API-specific response payload.
- vehicle_numberstring
  Registration number of the vehicle as echoed back from the source system.
- pending_challansnumber
  Total count of pending (unpaid) challans found for the vehicle.
- total_fine_amountnumber
  Aggregate fine amount in INR across all pending challans.
- challansarray
  List of individual challan records. Each element represents one traffic violation.
  - challan_numberstring
    Unique challan reference number issued by the traffic authority.
  - challan_idstring
    Internal challan ID in the national e-challan system.
  - violationstring
    Description of the traffic offence (e.g. 'Overspeeding', 'Red Light Jump', 'No Helmet').
  - datestring
    Date on which the violation was recorded (YYYY-MM-DD).
  - finenumber
    Fine amount in INR for this individual challan.
  - statusstring
    Payment status of the challan — typically 'Pending' or 'Paid'.
  - statestring
    State in which the challan was issued.
  - issuing_authoritystring
    Traffic police unit or RTO that issued the challan.
  - payment_sourcestring
    Payment channel through which the fine can be paid (e.g. 'Online', 'Court').