Skip to main content
VerifyAll logo
LiveInstant answerSandbox

Vehicle Challan Verification API

Find the traffic fines still open on a vehicle before you onboard, buy or finance it: the pending count, the unpaid total and every challan’s offences, fine and court status.

Request API access Book a demo View API documentation

The documentation opens in the VerifyAll dashboard after sign-in, for accounts with approved API access. New to the API? Start with the developer guide.

Overview

What the Vehicle Challan Verification API does

The Vehicle Challan Verification API answers the question a fleet operator, lender or buyer asks before taking on a vehicle: which fines are still open against it? Send an Indian registration number and the answer lists the traffic challans recorded against the vehicle, how many are pending and the total unpaid, with each challan’s number, date, place, offences, fine, status and court details.

It is a call of its own, POST /universal/vehicle-challan-verification, billed as Vehicle Challan Verification. No RC verification is needed first and none is run, so you pay for the challans only. When you also need the owner, validity, finance and permit details, the RC + Challan Verification API returns the challans with them in one answer.

The answer is the same whichever of our record sources served it: if the first source is unavailable at the moment of the call, a second one is asked automatically, and you are billed once either way. A vehicle with no challans is a normal answer with a count of 0, never an error.

How it works

  1. 1

    Your server sends POST /universal/vehicle-challan-verification with the registration_number, written without spaces, an optional chassis_number (the full number or at least its last 5 characters, which helps some records match) and an optional client_ref.

  2. 2

    The request is checked first: a registration number in the wrong format, or a chassis number shorter than 5 characters, is refused with a 400 and the list of problems, before anything runs or is charged.

  3. 3

    The vehicle’s challans are looked up in live records and the answer comes back in the same call, usually within about 5 seconds: the pending figures first, then items.

  4. 4

    The result is stored with a checkResultId and billed once as Vehicle Challan Verification from your prepaid wallet. Read it again with GET /check-results/{id}, find it by your client_ref, or download the challan PDF report for the record.

Request and response

Challan verification API endpoints and fields

The main fields; the full reference with every field, error code and a cURL sample is in the dashboard docs.

Endpoints
EndpointWhat it does
POST/universal/vehicle-challan-verificationThe traffic challans recorded against a vehicle, by registration number, without an RC verification

Request fields

Vehicle Challan Verification API request fields
FieldWhat it is
registration_numberRequiredThe vehicle registration number without spaces, for example MH05DS4747.
chassis_numberOptionalOptional: the chassis number, or at least its last 5 characters. Helps some records match.
client_refOptionalYour own reference, stored with the result (up to 100 characters). The X-Client-Ref header does the same.

What the answer returns

Vehicle Challan Verification API answer fields
FieldWhat it is
registration_numberThe registration number checked.
count / pending_countChallans on record for the vehicle, and how many of them are not paid yet.
total_pending_amountThe sum of the pending fines, as a decimal string with two places (0.00 when nothing is pending).
paid_or_disposed_count / in_court_countHow many challans were paid or settled, and how many were sent to a court, pending or not.
items[].challan_number / dateThe challan number as issued, and when it was issued (UTC date and time; null when only the day is recorded).
items[].place / state / authorityWhere the offence was recorded, the state code (MH, DL and so on) and the issuing office when it is named.
items[].offences / amountThe offence descriptions as recorded, and the fine for the challan.
items[].statuspending (not paid yet), paid, disposed (settled by a court or otherwise closed) or other.
items[].in_court / court_name / court_statusWhether the challan was sent to a court, which court, and where the proceeding stands as recorded.
items[].accused_name_maskedThe name of the accused as recorded, masked.

Base URL https://api.verifyall.ai. Authenticate with the X-API-Key header (a va_sandbox_ or va_live_ key). Every answer carries data, status_code, success, message and message_code; checks add outcome, checkResultId, charged and charged_amount.

Key features

Vehicle Challan Verification API features and capabilities

  • Challans without the RC

    A call of its own: no RC verification runs or is billed, which suits re-checking vehicles you already verified.

  • A pending total to act on

    pending_count and total_pending_amount give one figure per vehicle, so a rule can be a simple limit you set on open fines.

  • Court challans marked

    in_court, court_name and court_status show which fines have moved to a court and need a different follow-up.

  • A second source behind it

    If the first record source is unavailable, a second one answers in the same call, with the same fields and one charge.

Use cases

Where businesses use the Vehicle Challan Verification API

  • Fleet compliance reviews

    Check each vehicle in your fleet on the cycle you choose and see which have fines pending, where they were recorded and which have reached a court.

  • Driver and vehicle onboarding

    Before a vehicle joins a delivery, ride-hailing or logistics platform, see whether it carries unpaid fines and decide whether they must be cleared first.

  • Used-vehicle purchase and listing

    Know the pending total before a price is agreed or a listing goes live, so open fines are settled by the seller, not found by the buyer.

  • Gates and yards

    Check a truck or visitor vehicle for open fines when it arrives, without paying for its full RC record each time.

Industries

Coverage

Vehicles registered in India, looked up by registration number. The answer covers the traffic challans on record for the vehicle, pending and paid, with the court status where a challan was sent to a court.

Limitations to plan for

  • Challans are as recorded by the traffic authorities when the check runs; a fine paid in the last few days can still show as pending.
  • Challans are tied to the vehicle, not to a driver, and the accused name on each challan comes back masked.
  • A registration number with no challan record answers record_not_found. The lookup ran, so it is charged like any completed check. A vehicle with no challans is not this: it answers with a count of 0.
  • If the challan records cannot be read just now from any source, the call answers 424 and is not charged; try again later.

Integration

How to integrate the Vehicle Challan Verification API

From a business account to your first live call.

  1. Step 1

    Create a business account on VerifyAll and get it approved, as for running checks in the dashboard.

  2. Step 2

    Request Developer API access under Developers in the dashboard: the APIs you need, your expected monthly volume and your use case. The VerifyAll team reviews it and shares the API Services Agreement.

  3. Step 3

    Once the agreement is signed and access is approved, create your Sandbox key and build against sample data. Sandbox calls are never charged.

  4. Step 4

    Create your Production key, recharge your wallet and switch the key in your code: the endpoint and fields stay the same.

Get started

Request access to the Vehicle Challan Verification API

Tell us what you want to verify. We reply within one business day with access steps, Sandbox details and your API pricing.

Tell us about your integration

Tell us what you want to verify and how many checks you expect. Our team replies within one business day with access steps, Sandbox details and your API pricing.

We use these details only to reply to your request. See our privacy policy.

  • Contact sales

    Questions on volumes, onboarding or the API agreement.

    Contact sales

  • View API documentation

    The full reference for Vehicle Challan Verification API (endpoints, fields, errors, cURL) opens in the dashboard once your access is approved.

    Open the docs (sign-in)

  • Create a business account

    API keys are issued to an approved business account. Sign up, then request access under Developers.

    Create account

Pricing

Production calls are charged per check from your prepaid VerifyAll wallet, at your account’s API price; GST is added separately when you recharge. Sandbox calls are never charged. Your API prices are shown in the dashboard once access is approved. How pricing works

Already have a business account? Sign in to request access

Vehicle Challan Verification API: frequently asked questions

Answers for teams planning an integration.

Still have questions? Our team is happy to help.

Contact Support

All vehicle verification APIsRun Challan verification in the dashboard, without codeBrowse the API Marketplace

Start with the Vehicle Challan Verification API

Request access, build against the Sandbox, then go live with your Production key.

Request API access