Vehicle Ownership Verification API
New
Check the ownership details recorded against a vehicle registration number, and use the structured result in your resale, financing or fleet-transfer workflow.
Overview
Vehicle ownership verification checks the ownership details recorded against a vehicle registration number, and compares them with a trusted vehicle data source. Resale, financing and fleet-transfer work turns on one question. Who does the registration record name now, and does anything on it still point at a previous holder or a lender? Businesses that buy, finance, insure or transfer vehicles may need that answer before they release funds, publish a listing or take an asset onto their books. An API lets you run the check inside the application your team already works in. You stop collecting documents and reviewing them by hand for every vehicle. The fields you get back differ by data source, by vehicle record and by the service contract you select.
- Category
- Vehicle Services
- Coverage
- Pan-India vehicle registration records
- Input
- Vehicle registration number
- Output
- Ownership details available for that record, as structured data
- Typical users
- Lenders, insurers, marketplaces, fleet and leasing operators
- Coverage note
- You get what the underlying vehicle data source holds for that record
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 12 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/owner \
-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/owner", {
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/owner",
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
| 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 12 characters |
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
- Vehicle finance: ownership check before a used-vehicle loan is disbursed
- Insurance: matching the policy proposer to the recorded vehicle owner
- Used-vehicle marketplaces: screening seller details before a listing goes live
- Logistics and fleet: reconciling ownership during a fleet transfer
- Rental and leasing: confirming the asset is recorded against the lessor
- Dealerships and auctions: ownership review on trade-in and repossessed stock
What this service does
Ownership fields you can get back
The recorded owner name, ownership-related dates, the ownership serial position and any financier interest carried on the record. Which fields appear differs by data source, by vehicle record and by the service contract you select.
Starts from the registration number
The check runs on the vehicle registration number your team already holds. There is no document to collect and nothing to upload before you send the request.
Runs where the decision is made
Connect the API to a lending application, a marketplace listing flow, a fleet system or dealer management software. Ownership is then reviewed at the decision point instead of in a separate queue.
The same check on every vehicle
Manual document review gets harder as vehicle counts rise. An API workflow applies the same check to each vehicle, whether your team handles one a day or several hundred.
How a check runs
Tell us where the ownership check fits
Describe the point in your process where you need the check. We then set up access for your organization under the applicable service contract.
Send the registration number
Your application sends the registration number of the vehicle you need ownership details for.
The lookup runs against the record
The service processes the submitted registration number and retrieves the ownership details available for it.
Get the ownership details back
Your application receives the available ownership details in a structured response.
Act on the result
Send the outcome into the disbursal, listing, handover or fleet-transfer step it was requested for, and store it with the decision it supported.
Questions
- What do I send to check vehicle ownership?
- The vehicle registration number. There is no document upload and no data-entry step before you make the request.
- What details come back from a vehicle ownership check?
- The ownership information held against the registration record. That can include the recorded owner name, ownership-related dates, the ownership serial position and any financier interest. The exact set depends on the data source, the vehicle record and the service contract you select.
- Do I need consent to check who owns a vehicle?
- Ownership information can relate to an identifiable person. The check should rest on a lawful basis, and on the consent of the person concerned where your process requires it. Use the result only for the purpose you ran it for, and give access only to the team that needs it.
- Why does the record still show a financier after the loan is closed?
- A financier entry shows what the registration record carries now, and the status of any loan sits outside it. A closed loan whose paperwork has not reached the registering authority can still appear. Treat the entry as one input alongside the documentation the parties supply.
- How do I get access to the vehicle ownership API?
- Choose Get API and tell us about your workflow and the volumes you expect. We confirm what the service can support for your case and set up access under the applicable service contract.
- Why do two vehicles return different ownership fields?
- Registration records are not uniform. Older records, records recently transferred between states, and records with an update still in progress can carry fewer fields or different values. Build your workflow to handle a partial response instead of assuming every field is there.
Catalog entry last updated .