---
type: "product"
title: "Vehicle & RC Verification API India | Registration, Ownership & Insurance Check"
description: "Verify vehicle registration certificate (RC) details instantly — owner, chassis, engine, insurance, blacklist status, permits, and more. Pan-India coverage via VAHAN."
category: "verification"
canonical: "https://eps.eko.in/products/vehicle-rc-verification-api"
---


> **Canonical URL:** https://eps.eko.in/products/vehicle-rc-verification-api
> This is a machine-readable Markdown version of the page for AI agents and LLMs. The primary (HTML) version lives at the canonical URL above.

# Vehicle & RC Verification API for Ownership, Insurance & Compliance Checks

Get complete vehicle information from a registration number — owner details, chassis, engine, insurance status, blacklist check, permits, and more. Pan-India coverage via VAHAN database.

_Complete vehicle registration, ownership & insurance verification_

To get started, fill the form at https://eps.eko.in/signup (with your name, mobile number and email) or call us at +919513181707

## Overview

The Vehicle & RC Verification API enables businesses to fetch comprehensive vehicle information using a registration number. It returns RC status, owner details, chassis and engine numbers, manufacturer and model, insurance validity, permit details, blacklist and challan status, and more — all in a single API call. Designed for platforms that onboard drivers or vehicles, verify fleet compliance, underwrite motor insurance, or assess vehicle-related risk.

## Features

- RC & Vehicle Details: Get registration status, make/model, chassis, engine, color, body type, fuel type, and manufacturing year.
- Owner & Address: Retrieve owner name, father's name, present and permanent address with structured components.
- Insurance Status: Check insurance company, policy number, and validity — critical for fleet compliance and motor insurance.
- Blacklist & Challan Check: Identify blacklisted vehicles and pending traffic challans for risk assessment.
- Permit Details: Verify commercial vehicle permits and tax validity.
- Financier Information: Know if the vehicle is under finance and the lending institution — essential for used car and loan platforms.

## Who Should Use This

- Mobility and ride-hailing platforms
- Logistics and delivery companies
- Fleet operators
- Motor insurance companies
- Vehicle finance and lending platforms
- Used car marketplaces

## Use Cases

- Driver and vehicle onboarding
- Fleet compliance monitoring
- Motor insurance underwriting
- Vehicle finance and loan verification
- Used car marketplace verification
- Logistics and delivery platforms
- Parking and toll management

## What Can You Verify With Vehicle & RC Verification API?

- **Status** — Verification status string (e.g. 'Active', 'Inactive').
- **Vehicle Registration Number** — Vehicle registration number as recorded in the VAHAN database.
- **RC Status** — Current RC status — 'Active', 'Inactive', 'Suspended', etc.
- **Owner** — Full name of the registered owner of the vehicle.
- **Father's Name of Owner** — Father's name of the registered owner.
- **Present Address** — Present address of the owner as a single string.
- **Split Present Address** — Present address broken into structured components.
- **Permanent Address** — Permanent address of the owner as a single string.
- **Split Permanent Address** — Permanent address broken into structured components.
- **Registration Authority (RTO)** — Regional Transport Office (RTO) that issued the RC.
- **Date of Registration** — Date of first registration of the vehicle (YYYY-MM-DD).
- **RC Expiry Date** — RC validity expiry date (YYYY-MM-DD). Private vehicles are typically 15 years from registration.
- **Class** — Vehicle class as registered with the RTO (e.g. 'Motor Car', 'LMV', 'HTV').
- **Type** — Ownership type — 'Private' or 'Commercial'.
- **Is Commercial Vehicle?** — True if the vehicle is registered for commercial use.
- **Vehicle Manufacturer Name** — Manufacturer / make of the vehicle.
- **Model** — Vehicle model name.
- **Fuel Type** — Fuel type — 'Petrol', 'Diesel', 'CNG', 'Electric', etc.
- **Norms Type** — Emission standard the vehicle complies with (e.g. 'Bharat Stage VI').
- **Chassis** — Chassis number of the vehicle as per RC.
- **Engine** — Engine number of the vehicle as per RC.
- **Vehicle Insurance Company Name** — Name of the insurance company that issued the current motor policy.
- **Vehicle Insurance Policy Number** — Insurance policy number.
- **Vehicle Insurance Upto** — Insurance validity date (YYYY-MM-DD). Check against today to flag lapsed policies.
- **RC Financier** — Name of the financier / lending institution if the vehicle is under a loan.
- **Blacklist Status** — Whether the vehicle appears on a blacklist — 'Not Blacklisted' or 'Blacklisted'.
- **Reason** — Reason for blacklisting.
- **Permit Type** — Type of permit — e.g. 'Tourist', 'Contract Carriage', 'Goods'.
- **Permit Valid Upto** — Permit validity end date.
- **National Permit Upto** — National permit validity date.

## API Preview — Vehicle & RC Verification

`POST /tools/kyc/vehicle-rc`

### Example inputs

| Field | Value |
| --- | --- |
| Vehicle Number | HJ01ME5678 |

### Example outputs

| Field | Value |
| --- | --- |
| Status | Active |
| Vehicle Registration Number | HR26DA8398 |
| RC Status | Active |
| Owner | Arya Sharma |
| Father's Name of Owner | Rajesh Sharma |
| Present Address | 123, Sector 45, Gurgaon, Haryana 122003 |
| Permanent Address | 456, MG Road, Gurgaon, Haryana 122001 |
| Registration Authority (RTO) | HR-26 Gurgaon |
| Date of Registration | 2020-06-15 |
| RC Expiry Date | 2039-06-14 |
| Class | Motor Car |
| Type | Private |
| Is Commercial Vehicle? | false |
| Vehicle Manufacturer Name | Mahindra & Mahindra |
| Model | XUV300 |
| Fuel Type | Petrol |
| Norms Type | Bharat Stage VI |
| Chassis | MA1TE2ELXLM123456 |
| Engine | N10A1234567 |
| Vehicle Insurance Company Name | Tata AIG General Insurance |
| Vehicle Insurance Policy Number | 0165274682 |
| Vehicle Insurance Upto | 2025-06-14 |
| RC Financier | HDFC Bank Ltd |
| Blacklist Status | Not Blacklisted |
| Reason | Unpaid challan |
| Permit Type | Tourist |
| Permit Valid Upto | 2026-02-28 |
| National Permit Upto | 2026-02-28 |

## Integration Steps

1. **[Sign Up](/console)** — Sign up in minutes with your mobile number (OTP verify).
2. **Verify Identity** — Complete your basic KYC with PAN and address details to verify your identity.
3. **Test APIs Live** — Load funds into your wallet and test the verification APIs live — evaluate before you integrate.
4. **[Integrate with AI](/ai)** — Ready to build? Visit our AI hub for free plugins & tools to integrate faster.
5. **Go Live** — Start verifying vehicle registrations in production.

## FAQs

### What details are returned?
Owner name, RC status, vehicle class, fuel type, manufacturer, model, body type, color, chassis and engine number, registration and expiry dates, insurance company and validity, blacklist status, emission norms, and financier details.

### Is pan-India coverage available?
Yes, we cover all states and union territories through integration with the VAHAN national database.

### Can I verify commercial vehicles?
Yes, commercial vehicles return additional details like permit type, permit validity, national permit, and tax status.

### How accurate is the verification?
All verifications are done against official RTO databases (VAHAN). Updates to vehicle information reflect in the source within 15–30 days.

### Is real-time verification available?
Yes, all verifications are performed in real-time with sub-second response times for most queries.

### Can I check if a vehicle is blacklisted?
Yes, the API returns blacklist status along with detailed reasons if the vehicle has been blacklisted.

### Are all returned fields available for every vehicle?
No. Field availability may vary by vehicle type, RTO/source record, partner configuration, and data availability. The API response should be handled programmatically for missing or unavailable fields.

### How do I get started?
Four steps: **sign up** at the [developer console page](/console), verify your identity with PAN and address details, load your wallet to test the APIs live, then integrate and go live. Sandbox credentials are issued immediately — you can call your first endpoint before any paperwork clears.

### What is EPS?
**EPS (Eko Platform Services)** is the technology arm of Eko — the developer tools, AI tooling and APIs that power modern fintech integration, from money transfer and AePS to identity verification.

### What are the different ways to integrate with Eko EPS?
Three paths, pick whichever suits your stack:

- Call the **REST APIs** directly.
- Use our official **Node.js, Python, PHP, Go or Java SDKs** to skip request-signing boilerplate.
- Let an **AI coding agent** build it via our [MCP server and agent skills](/ai#install).

For multi-step flows (onboard a sender, *then* transfer) start from a [transaction-flow recipe](/recipe) rather than wiring single endpoints together yourself.

### How does API authentication work?
Each request carries your static `developer_key` header plus a per-request `secret-key` header — an **HMAC-SHA256** signature of the current timestamp, keyed by your access key. The access key itself is **never sent over the wire**. You receive UAT keys on signup and production keys after KYC.

The [How Authentication Works](/docs/how-auth-works) guide has the full signing recipe in five languages plus an **in-browser playground** that generates and verifies a real `secret-key` against your own access key.

### Why does my API call return 401 Unauthorized?
Authentication failed. For the known causes, the response body's `status` names the check that failed:

- `2483` — The developer_key is wrong.
- `2484` — The secret-key (signature) is wrong.
- `2485` — The secret-key-timestamp is more than 2 minutes older or newer than the server clock, or was reused from an earlier request.
- `2486` — The secret-key-timestamp is not in milliseconds (13 digits) — often seconds (10 digits).
- `2487` — The secret-key or secret-key-timestamp header is missing.

If your signature checks out in the [secret-key playground](/docs/how-auth-works#try-it-secret-key-playground) and you still get a `401`, make sure the base URL matches your keys (UAT vs production) and, in production, that your server's IP is whitelisted.

### Is there a sandbox environment for testing?
Yes. A full **sandbox** is available immediately on signup — test your integration end-to-end before going live, no commitment required. For offline work you can also run our [mock server](/ai#artifacts) (`npx -y @ekoindia/eps-mock-server`) and get canned responses with no network calls at all.

### What are the sandbox and production base URLs?
Sandbox and production share the same paths and differ **only** by base URL:

- UAT / Sandbox — `https://staging.eko.in/ekoapi/v3`
- Production — `https://api.eko.in/ekoicici/v3`

A common cause of failures is calling the sandbox URL with live credentials, or vice-versa — **make sure the base URL matches the keys you are using**.

### Do I need to whitelist my server IP?
It's optional. **IP whitelisting** is available for **production** access as an extra layer of security — share your **static public (server) IP** with us and we'll whitelist it.

### Can an AI coding agent build the integration for me?
Yes — that is the fastest path. Point your agent (Claude Code, Codex, Cursor, Copilot, …) at our **MCP server** and it can look up any endpoint, generate correctly-signed requests, and scaffold the integration in your own stack. Install it in [one step from the AI hub](/ai#install), or start from a [ready-made prompt](/ai#quick-start).

We also publish an **OpenAPI 3.1 spec**, a **Postman collection** and per-agent **context packs** (`AGENTS.md`, `CLAUDE.md`, `.cursorrules`) so an agent has the ground truth instead of guessing.

### What response times can I expect?
Most verification APIs return in **real time with sub-second responses**, and 99th-percentile latency stays under two seconds across verification endpoints. Transaction APIs (DMT, AePS, BBPS) respond within seconds.

### Can the API handle high volumes?
Yes. The API is designed to handle **large-scale volumes** reliably without performance degradation.

### How is API usage billed?
Usage is billed **per successful API call** with no minimum commitment. Volume-based pricing tiers are available — see the [pricing calculator](/pricing) for indicative rates, or contact our team for a custom quote.

## API Endpoints

- [Vehicle & RC Verification](https://eps.eko.in/docs/vehicle-rc.md) (POST)

## API Documentation

- [Full developer docs](https://eps.eko.in/docs/vehicle-rc)

## Related Products

- [Mobile/OTP Verification](https://eps.eko.in/products/mobile-otp-verification-api): Send, verify & validate mobile OTPs with a signed proof token ([markdown](https://eps.eko.in/products/mobile-otp-verification-api.md))
- [PAN Verification](https://eps.eko.in/products/pan-verification-api): Full PAN identity fetch in <2 seconds ([markdown](https://eps.eko.in/products/pan-verification-api.md))
- [Bank Account Verification](https://eps.eko.in/products/bank-verification-api): Penny-drop bank account validation ([markdown](https://eps.eko.in/products/bank-verification-api.md))
- [GST Verification](https://eps.eko.in/products/gst-verification-api): GSTIN lookup & filing status ([markdown](https://eps.eko.in/products/gst-verification-api.md))
- [DigiLocker Integration](https://eps.eko.in/products/digilocker-api): Fetch notarised docs — Aadhaar, DL, marksheets, etc ([markdown](https://eps.eko.in/products/digilocker-api.md))

- [Site index](https://eps.eko.in/index.md): Full list of API products, industries, and solution packs