Skip to content

Vehicle RC Verification API

Popular

Check the registration details recorded against a vehicle number, then use the result inside your onboarding, lending or fleet workflow.

Overview

Vehicle RC verification checks the registration details recorded against a vehicle and compares the available details with a trusted vehicle data source. A Registration Certificate holds the main facts about a vehicle, including its registration and vehicle details. If you handle vehicle financing, insurance, resale, fleet operations or other automotive transactions, you may need to confirm those details before you finish a process. An API lets you run the check inside your own application instead of repeating manual lookups. For lending, insurance, fleet management and automotive marketplaces, an automatic check can cut manual review and support faster vehicle workflows.

Coverage
India
Input
Vehicle registration number
Output
Structured registration and vehicle details
Typical use
Onboarding, financing, resale, fleet

The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.

Endpoint URL and method

POSThttps://gateway.staging.finsour.io/v1/vehicle/rc

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Authentication

Scheme API key travels in the X-Api-Key header

Send your API key in this header on every call, from your own server: a key sent from a browser is refused. A key starting fs_test_ calls the sandbox and one starting fs_live_ calls production, at the same address. Create keys in the FinSour console.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Request parameters

Content type application/json

Headers

NameTypeRequiredDescriptionConstraints
Idempotency-KeystringRequiredA key you generate for each attempt. Sending the same key again returns the first answer instead of running the check twice; the same key with a different body is refused.8 to 255 characters. Matches ^[A-Za-z0-9._:-]+$

Body

NameTypeRequiredDescriptionConstraints
inputobjectRequiredThe details to check.—
input.registrationNumberstringRequired—Matches ^[A-Z0-9]+$. 5 to 12 characters
optionsobjectOptionalSettings for this call.—
options.referencestringOptionalYour own reference for this call. It comes back unchanged as meta.reference.1 to 128 characters
options.consentobjectOptionalThe person's consent to this check.—
options.consent.obtainedbooleanRequiredSend true once the person has agreed to the check.Always true
options.consent.atstring (date-time)RequiredWhen the person gave consent.—
options.consent.purposestringRequiredWhat the check is for, for example kyc.1 to 64 characters

Request samples

cURL

curl -X POST https://gateway.staging.finsour.io/v1/vehicle/rc \
  -H "X-Api-Key: $FINSOUR_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {
    "registrationNumber": "<registrationNumber>"
  }
}'

Node.js

const response = await fetch("https://gateway.staging.finsour.io/v1/vehicle/rc", {
  method: "POST",
  headers: {
    "X-Api-Key": process.env.FINSOUR_API_KEY,
    "Idempotency-Key": crypto.randomUUID(),
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "input": {
      "registrationNumber": "<registrationNumber>"
    }
  }),
});

console.log(response.status, await response.json());

Python

import os
import uuid

import requests

response = requests.post(
    "https://gateway.staging.finsour.io/v1/vehicle/rc",
    headers={
        "X-Api-Key": os.environ["FINSOUR_API_KEY"],
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "input": {
            "registrationNumber": "<registrationNumber>",
        },
    },
    timeout=30,
)

print(response.status_code, response.json())

Generated from the fields above. Replace each value in angle brackets with your own; the key is read from FINSOUR_API_KEY.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Response schema

Status 200 · content type application/json

NameTypePresentDescriptionConstraints
dataobjectAlwaysThe result of the check.—
data.foundbooleanAlways——
data.registrationNumberstringAlways—Matches ^[A-Z0-9]+$. 5 to 12 characters
data.registrationobject or any or nullAlways——
data.ownerobject or any or nullAlways——
data.vehicleobject or any or nullAlways——
data.insuranceobject or any or nullAlways——
data.pollutionobject or any or nullAlways——
data.fitnessobject or any or nullAlways——
data.taxobject or any or nullAlways——
data.permitobject or any or nullAlways——
data.financeobject or any or nullAlways——
data.sourceobjectAlways——
data.source.fetchedAtstringAlwaysWhen the answer was fetched: RFC 3339 UTC with a Z, never an epoch or an IST offset.Matches ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{1,9})?Z$

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Error codes

CodeStatusMeaningRetrying
API_VERSION_UNSUPPORTED400That API version is no longer supported.Do not retry automatically
IDEMPOTENCY_KEY_INVALID400That Idempotency-Key does not meet the required format.Do not retry automatically
IDEMPOTENCY_KEY_REQUIRED400An Idempotency-Key header is required for this request.Do not retry automatically
REQUEST_MALFORMED400The request could not be parsed.Do not retry automatically
AUTH_KEY_EXPIRED401The API key is not valid.Do not retry automatically
AUTH_KEY_INVALID401The API key is not valid.Do not retry automatically
AUTH_KEY_MISSING401No API key was presented.Do not retry automatically
AUTH_KEY_REVOKED401The API key is not valid.Do not retry automatically
INSUFFICIENT_BALANCE402The available balance is not enough for this request.Do not retry automatically
AUTH_IP_NOT_ALLOWED403This API key may not be used from this address.Do not retry automatically
ENTITLEMENT_MISSING403This organization is not entitled to that product in this environment.Do not retry automatically
ORGANIZATION_SUSPENDED403This organization is not active.Do not retry automatically
PRODUCT_NOT_AVAILABLE403That product is not available.Do not retry automatically
PRODUCT_RETIRED403That product has been withdrawn.Do not retry automatically
SCOPE_INSUFFICIENT403This API key does not carry the scope this product requires.Do not retry automatically
PRODUCT_NOT_FOUND404No such product.Do not retry automatically
IDEMPOTENCY_KEY_REUSED409That idempotency key was already used for a different request.Do not retry automatically
PRICE_UNAVAILABLE409No active price covers this product right now.Safe to retry
REQUEST_IN_PROGRESS409An earlier attempt with this key is still running.Safe to retry
SETTLEMENT_PENDING409This request is awaiting reconciliation by an operator.Do not retry automatically
API_VERSION_SUNSET410That API version passed its announced sunset date.Do not retry automatically
REQUEST_TOO_LARGE413The request body is too large.Do not retry automatically
UNSUPPORTED_MEDIA_TYPE415That content type is not accepted on this route.Do not retry automatically
SANDBOX_FIXTURE_MISSING422No sandbox fixture exists for this input. Use a different test value.Do not retry automatically
UPSTREAM_REJECTED422The upstream source rejected the input.Do not retry automatically
VALIDATION_FAILED422The request payload is invalid.Do not retry automatically
CONCURRENCY_LIMIT429Too many simultaneous requests.Safe to retry
QUOTA_EXCEEDED429The allowance for this window is spent.Do not retry automatically
RATE_LIMITED429Too many requests.Safe to retry
INTERNAL_ERROR500An unexpected error occurred.Safe to retry
OUTCOME_UNCERTAIN502The outcome of this request is not yet known. Retry with the same Idempotency-Key.Do not retry automatically
UPSTREAM_UNAVAILABLE502The upstream source is unavailable. Retry shortly.Safe to retry
MAINTENANCE_MODE503The service is in a maintenance window.Safe to retry
NO_PROVIDER_AVAILABLE503No provider can serve this product right now.Safe to retry
SERVICE_OVERLOADED503The service is shedding load. Retry shortly.Safe to retry
UPSTREAM_TIMEOUT504The upstream source did not respond in time.Safe to retry

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Rate limits

ScopeLimitWindowAt the limit
Your API key, within your organisation's limitThe figure in X-RateLimit-LimitPer minute429 RATE_LIMITED, with Retry-After in seconds. Every answer past authentication carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset.

Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.

Use cases

  • Banks and NBFCs
  • Insurance companies
  • Used-car marketplaces
  • Vehicle dealerships
  • Fleet management companies
  • Fintech and lending platforms
  • Vehicle rental and leasing companies

What this service does

  • Fields an RC response can carry

    A response can carry registration details, make and model, fuel type, registration and ownership details, fitness, insurance, financier and pollution details, and other vehicle attributes. Which fields you get depends on the data source behind the check and on the vehicle record itself.

  • Where the RC check sits in your product

    Connect the API to a website, mobile application, internal dashboard, CRM, lending platform or automotive software. The check then runs as part of a transaction instead of beside it.

  • Less collecting and re-keying by hand

    An automatic lookup cuts repeated data entry. Your team spends less time gathering and reviewing registration details by hand.

  • The same handling for one vehicle or a thousand

    Manual checks get hard once a team processes a large number of vehicles. An API workflow treats every vehicle the same way, whether you send one or a thousand.

  • What the result supports afterwards

    Verified registration details can support decisions about financing, insurance, resale, fleet operations and vehicle onboarding.

How a check runs

  1. Start with the vehicle registration number

    Send the required vehicle registration number through your application or a direct API request.

  2. The API looks up the registration record

    The API processes the vehicle information you sent and retrieves the available registration data.

  3. Read the RC details in the response

    Your application receives the available vehicle information in a structured API response.

  4. Use the RC data in your own process

    You can use the returned information for customer onboarding, vehicle evaluation, lending, insurance, fleet management or other business processes.

Questions

What is a Vehicle RC Verification API?
It is an interface that lets you run vehicle registration verification inside your own applications, platforms and internal systems, instead of checking each vehicle separately by hand.
What does a vehicle RC check show?
It shows the registration and vehicle information available for a particular vehicle registration number.
How does the Vehicle RC Verification API work?
Your application sends the required vehicle registration number. The system processes the request and returns the available vehicle registration information in a structured response.
Which vehicle details come back from RC verification?
Depending on the records available, the response may contain registration details, make and model, fuel type, ownership details, fitness, insurance, financier, pollution and other relevant vehicle attributes. The exact fields depend on the data source behind the check and on the vehicle record.
Can I verify a vehicle RC with only the registration number?
Yes. The vehicle registration number is the input for the verification workflow, where the API supports it.
How do I verify a vehicle RC online?
Add the API to your application and send the required vehicle registration information. The available vehicle details come back in the response.
Can banks and NBFCs use vehicle RC verification?
Yes. Banks, NBFCs, fintech companies and other lending businesses can add vehicle verification to the relevant financing and vehicle assessment workflows.
Can dealerships use an RC verification API?
Yes. Dealerships can use registration verification as part of vehicle evaluation, buying, selling, exchange and onboarding.
Does RC verification work for fleet management?
RC verification can slot into fleet-management workflows. It can help you keep and review vehicle information across a whole fleet.

Catalog entry last updated .