Skip to content

Engine to RC API

New

Find the vehicle registration record that an engine number points to, and use the details when the registration number is missing, damaged or disputed.

Overview

An engine to RC lookup starts from an engine number and finds the vehicle registration record linked to it. You work from the engine, instead of from the registration number. Businesses hit this whenever the plate is not a reliable identifier. A vehicle can arrive at a yard without documents, or a claim file can list an engine number and little else. A repossessed asset often has to be cataloged from the stampings on the block. In each of these cases the engine number is what your team actually holds. An API runs the lookup inside your existing software and returns the available registration information as structured data. Basic and Advanced cover different depths of detail. The fields you get differ by data source, by vehicle record and by the service contract you select.

Coverage
Pan-India vehicle records, resolved from the engine number
Input
Engine number
Output
Registration record details available for that engine number
Typical users
Insurers, lenders, auction platforms, salvage yards, fleet teams
Detail depth
Basic and Advanced, set by the service contract you select

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-by-engine

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.engineNumberstringRequired—Matches ^[A-Z0-9]+$. 5 to 20 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-by-engine \
  -H "X-Api-Key: $FINSOUR_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {
    "engineNumber": "<engineNumber>"
  }
}'

Node.js

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

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-engine",
    headers={
        "X-Api-Key": os.environ["FINSOUR_API_KEY"],
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "input": {
            "engineNumber": "<engineNumber>",
        },
    },
    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.engineNumberstringAlways—Matches ^[A-Z0-9]+$. 5 to 20 characters
data.registrationNumberstring or any or nullAlways——
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

  • Insurance: matching a claim file to a registration record from the engine number
  • Vehicle finance: identifying repossessed stock held at a yard without documents
  • Auctions and marketplaces: establishing what a lot is before it is cataloged
  • Logistics and fleet: reconciling engine numbers against an asset register
  • Scrapping and salvage: confirming the record before a vehicle is dismantled
  • Dealerships and workshops: vehicle intake when the certificate is missing

What this service does

  • Reach the RC from the engine number

    The lookup starts from the engine number stamped on the vehicle. You can reach a registration record when the plate or the certificate is missing, damaged or disputed.

  • Two depths: Basic and Advanced

    Basic resolves the registration record and its core vehicle details. Advanced returns a wider set of the attributes held on that record. Available fields differ by data source, by vehicle record and by the service contract you select.

  • Sized for yard and claims volume

    Salvage intake, repossession catalogs and claims desks handle vehicles in batches. An API workflow applies the same lookup to each one instead of routing it to a person.

  • Structured output for your case file

    The available registration information comes back as structured data, ready to write into a claim file, an asset register or an auction listing without retyping.

How a check runs

  1. Open access for engine number lookups

    Tell us where the engine number lookup fits in your process, and we enable it for your organization under the applicable service contract.

  2. Read the engine number off the vehicle

    Take the engine number from the vehicle or from the file you hold, and check the transcription before the request goes out.

  3. Send the number at the depth you need

    Your application submits the engine number, at Basic or Advanced depth depending on what the next step needs.

  4. Get the registration record back

    The registration information available for the submitted engine number comes back in a structured response.

  5. Carry the result into the case

    Route the result into the claim, listing, valuation or intake step it was requested for, and store it with the number it resolved from.

Questions

What do I send to run an engine to RC lookup?
The engine number as recorded on the vehicle. You need no registration number and no document upload to start the lookup.
What does an engine to RC lookup return?
The registration information available for the submitted engine number. That can include core vehicle and registration details, and a wider set of attributes at the Advanced level. Which of those you see depends on the data source, the vehicle record and the service contract you select.
What is the difference between Basic and Advanced engine to RC?
Basic resolves the registration record and returns its core details. Advanced returns more of what that record holds, for workflows that need context before they act. Both are limited to the information the underlying record contains.
Do I need consent to look up an RC from an engine number?
Registration records include information about identifiable people. The lookup 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 the lookup for.
How do I get access to the engine to RC API?
Use the Get API button to describe the workflow and the volumes you expect. We come back on what the service can support for your case, then enable access under the applicable service contract.
Why did my engine number return no record?
Usually a typing error in the engine number. It can also be a record not updated after an engine replacement, or a vehicle the underlying source does not hold. Check the input again, and keep a manual fallback for the cases that do not resolve.

Catalog entry last updated .