Chassis to RC API
New
Start from a chassis number and get the vehicle registration record it belongs to, with the details your intake, claim or catalog step needs.
Overview
A chassis to RC lookup starts from a chassis number and finds the vehicle registration record linked to it. The chassis number is stamped into the frame at manufacture and stays with the vehicle for life. That makes it the most durable identifier a vehicle carries. That durability is why it turns up in the files businesses work from every day. Examples include an insurance proposal, a dealer stock sheet, an auction lot record and a scrapping application. The chassis number is present in all of them, and the registration number may not be. You can run the lookup from your own software through an API, and get the available registration information back as structured data. Basic and Advanced give you two depths of detail. What you get differs by data source, by vehicle record and by the service contract you select.
- Category
- Vehicle Services
- Coverage
- Pan-India vehicle records, resolved from the chassis number
- Input
- Chassis number
- Output
- Registration record details available for that chassis number
- Typical users
- Insurers, lenders, scrapping facilities, auction platforms, fleet teams
- Detail depth
- Basic and Advanced, depending on your service contract
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
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
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
Headers
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
Idempotency-Key | string | Required | A 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
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
input | object | Required | The details to check. | — |
input. | string | Required | — | Matches ^[A-Z0-9]+$. 5 to 20 characters |
options | object | Optional | Settings for this call. | — |
options. | string | Optional | Your own reference for this call. It comes back unchanged as meta.reference. | 1 to 128 characters |
options. | object | Optional | The person's consent to this check. | — |
options. | boolean | Required | Send true once the person has agreed to the check. | Always true |
options. | string (date-time) | Required | When the person gave consent. | — |
options. | string | Required | What 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-by-chassis \
-H "X-Api-Key: $FINSOUR_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"input": {
"chassisNumber": "<chassisNumber>"
}
}'Node.js
const response = await fetch("https://gateway.staging.finsour.io/v1/vehicle/rc-by-chassis", {
method: "POST",
headers: {
"X-Api-Key": process.env.FINSOUR_API_KEY,
"Idempotency-Key": crypto.randomUUID(),
"Content-Type": "application/json",
},
body: JSON.stringify({
"input": {
"chassisNumber": "<chassisNumber>"
}
}),
});
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-by-chassis",
headers={
"X-Api-Key": os.environ["FINSOUR_API_KEY"],
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"input": {
"chassisNumber": "<chassisNumber>",
},
},
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
| Name | Type | Present | Description | Constraints |
|---|---|---|---|---|
data | object | Always | The result of the check. | — |
data. | boolean | Always | — | — |
data. | string | Always | — | Matches ^[A-Z0-9]+$. 5 to 20 characters |
data. | string or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | object | Always | — | — |
data. | string | Always | When 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
| Code | Status | Meaning | Retrying |
|---|---|---|---|
API_VERSION_UNSUPPORTED | 400 | That API version is no longer supported. | Do not retry automatically |
IDEMPOTENCY_KEY_INVALID | 400 | That Idempotency-Key does not meet the required format. | Do not retry automatically |
IDEMPOTENCY_KEY_REQUIRED | 400 | An Idempotency-Key header is required for this request. | Do not retry automatically |
REQUEST_MALFORMED | 400 | The request could not be parsed. | Do not retry automatically |
AUTH_KEY_EXPIRED | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_INVALID | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_MISSING | 401 | No API key was presented. | Do not retry automatically |
AUTH_KEY_REVOKED | 401 | The API key is not valid. | Do not retry automatically |
INSUFFICIENT_BALANCE | 402 | The available balance is not enough for this request. | Do not retry automatically |
AUTH_IP_NOT_ALLOWED | 403 | This API key may not be used from this address. | Do not retry automatically |
ENTITLEMENT_MISSING | 403 | This organization is not entitled to that product in this environment. | Do not retry automatically |
ORGANIZATION_SUSPENDED | 403 | This organization is not active. | Do not retry automatically |
PRODUCT_NOT_AVAILABLE | 403 | That product is not available. | Do not retry automatically |
PRODUCT_RETIRED | 403 | That product has been withdrawn. | Do not retry automatically |
SCOPE_INSUFFICIENT | 403 | This API key does not carry the scope this product requires. | Do not retry automatically |
PRODUCT_NOT_FOUND | 404 | No such product. | Do not retry automatically |
IDEMPOTENCY_KEY_REUSED | 409 | That idempotency key was already used for a different request. | Do not retry automatically |
PRICE_UNAVAILABLE | 409 | No active price covers this product right now. | Safe to retry |
REQUEST_IN_PROGRESS | 409 | An earlier attempt with this key is still running. | Safe to retry |
SETTLEMENT_PENDING | 409 | This request is awaiting reconciliation by an operator. | Do not retry automatically |
API_VERSION_SUNSET | 410 | That API version passed its announced sunset date. | Do not retry automatically |
REQUEST_TOO_LARGE | 413 | The request body is too large. | Do not retry automatically |
UNSUPPORTED_MEDIA_TYPE | 415 | That content type is not accepted on this route. | Do not retry automatically |
SANDBOX_FIXTURE_MISSING | 422 | No sandbox fixture exists for this input. Use a different test value. | Do not retry automatically |
UPSTREAM_REJECTED | 422 | The upstream source rejected the input. | Do not retry automatically |
VALIDATION_FAILED | 422 | The request payload is invalid. | Do not retry automatically |
CONCURRENCY_LIMIT | 429 | Too many simultaneous requests. | Safe to retry |
QUOTA_EXCEEDED | 429 | The allowance for this window is spent. | Do not retry automatically |
RATE_LIMITED | 429 | Too many requests. | Safe to retry |
INTERNAL_ERROR | 500 | An unexpected error occurred. | Safe to retry |
OUTCOME_UNCERTAIN | 502 | The outcome of this request is not yet known. Retry with the same Idempotency-Key. | Do not retry automatically |
UPSTREAM_UNAVAILABLE | 502 | The upstream source is unavailable. Retry shortly. | Safe to retry |
MAINTENANCE_MODE | 503 | The service is in a maintenance window. | Safe to retry |
NO_PROVIDER_AVAILABLE | 503 | No provider can serve this product right now. | Safe to retry |
SERVICE_OVERLOADED | 503 | The service is shedding load. Retry shortly. | Safe to retry |
UPSTREAM_TIMEOUT | 504 | The 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
| Scope | Limit | Window | At the limit |
|---|---|---|---|
| Your API key, within your organisation's limit | The figure in X-RateLimit-Limit | Per minute | 429 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
- Insurance: resolving a proposal or claim file to a registration record
- Vehicle finance: tying a loan file to the asset recorded behind it
- Scrapping and dismantling: matching a vehicle to its record before acceptance
- Auctions and marketplaces: confirming lot identity before a catalog is published
- Logistics and fleet: reconciling an asset register against vehicles on the yard
- Dealerships and stockyards: identifying stock not yet matched to a record
What this service does
One number that outlasts the plate
The chassis number stays with a vehicle for its life. The lookup can reach a registration record when the plate has been replaced, the certificate is missing or the engine has been swapped.
Pick the depth your step needs
Choose Basic where the job is to identify the vehicle, and Advanced where the next step assesses it. Both return only what the underlying record holds, and that differs by data source, by record and by the service contract you select.
Identity settled at intake
Yard receipt, inspection and stock intake all need the vehicle tied to a record before anything else happens. The lookup runs at that point.
Fields your systems can write straight in
The available registration information comes back as structured data, ready for an underwriting file, an asset register, a lot record or a dealer management system.
How a check runs
Get chassis lookups switched on
Show us where the chassis lookup sits in your intake process. We open access for your organization under the applicable service contract.
Take the chassis number down
Read the chassis number from the vehicle or the document you hold, and confirm the characters before the request is sent.
Submit it at Basic or Advanced
Your application sends the chassis number together with the depth of detail your next step needs.
Read the registration record
The record the chassis number resolves to comes back with the details held against it, in a structured response.
Move the file forward
Route the outcome into the underwriting, intake, valuation or catalog step it was requested for, and keep it with the number it resolved from.
Questions
- What do I send to run a chassis to RC lookup?
- Just the chassis number, taken from the vehicle or from your own file. Nothing else is needed to start: no plate details, no certificate and no upload.
- What does a chassis to RC lookup return?
- The record the chassis number resolves to, with the details held against it. Basic gives you core vehicle and registration details, and Advanced adds a wider set of attributes. What is present differs from one record to the next, and depends on the data source and the service contract you select.
- What is the difference between Basic and Advanced chassis to RC?
- Basic resolves the chassis number to a registration record and returns its core details, which is usually enough to confirm identity at intake. Advanced returns more of what that record holds, for workflows that assess the vehicle.
- Do I need consent to look up an RC from a chassis number?
- Yes, in the sense that a registration record describes a person as well as a vehicle. Each lookup should rest on a lawful basis, and on the consent of the person concerned where your process calls for it. Limit who can run it, and use what comes back only for the purpose you gathered it for.
- How do I get access to the chassis to RC API?
- Press Get API and tell us what the lookup is for, along with the volumes you expect. We confirm what is possible for your case and open access under the applicable service contract.
- Why does one chassis number return more detail than another?
- Records differ in age, completeness and how recently they were updated. A lookup can also return nothing if the chassis number was mistyped or the underlying source does not hold the record. Handle a partial or empty response as a normal path.
Catalog entry last updated .