Global VIN Vehicle Data API
Enter a VIN to get vehicle specifications, history and valuation across 150+ countries, plus China coverage (registration / inspection / manufacturing / export / accident / anti-fraud across 31 provinces).
We aggregate public vehicle records from North America, Japan, China and Europe, completing cleaning, standardisation, linking and bilingual modelling, delivered through one REST API. Whether the car is a North American used car, a Japanese auction car or a Chinese-manufactured export, one query covers it.
No need to integrate data sources from a dozen countries yourself.
Enterprise solution enquiryJSON APIBilingual (Chinese/English) response
Search key 3
- Data sources
- Global VIN library
- Verification
- VIN valid
- Data sources
- Multi-region records
- Resolve
- Normalised
- Data sources
- Vehicle master data
- Classification
- Classified
Master vehicle entity parsed
2019 · 2.5L
- Brand
- Toyota (masked sample)
- Model
- Camry
- Model year
- 2019
- Engine
- 2.5L
- Transmission
- Automatic
- Fuel
- Gasoline
- Vehicle category
- Sedan
- Risk rating
- Low risk
Free VIN decoders are everywhere, but they are far from being "ready for a business system".
The real problem isn't whether you can decode a VIN, but how to turn public data scattered across a dozen sources — North American accident databases, Japanese auctions, Chinese motor vehicle registration, European MOT, international stolen-vehicle databases — into a vehicle record your business systems can fetch in one call and track over time.
-
01
Data is scattered
Vehicle history, accidents, title, mileage, theft and specifications are scattered across different national systems with different naming and definitions, so your systems have to stitch them together.
-
02
China data gap
Mainstream international vehicle history databases do not cover Chinese-manufactured vehicles, yet Chinese brands such as BYD, NIO and Geely are expanding overseas fast — a clear gap in related lookups.
-
03
Hard to query programmatically
Each country publishes data as different interfaces or files; pulling vehicle records in bulk by VIN means doing your own parsing and modelling, with no direct system integration.
-
04
Maintenance costs keep piling up
Source changes, field adjustments and regional expansion all require long-term engineering effort, and missed updates easily skew valuations or risk conclusions.
From scattered multi-region records to a directly callable vehicle record
A VIN passes through six auditable stages to become stable, structured, linkable JSON.
Collect
Continuous sync with multi-region public vehicle records
source.capture()Clean
Unifies field naming, units and regional definitions
parse · dedupeNormalize
Unifies specification, history, valuation and risk fields
schema.map()Relate
Links VINs to models, regions and history
graph.link()Aggregate
One call returns specifications, history, valuation and China coverage
aggregate.v1Deliver
Delivered to your business systems via a stable REST API
json_api.v1You don't have to integrate a dozen countries' data sources, normalise fields or build Chinese-language models yourself.Call the API and use the results directly.
One API covering the core VIN lookup scenarios
Unified REST API · JSON responses · Bearer token authentication. Basic VIN lookup is the core of the product, with China coverage, history, valuation and theft checks built on the same data model.
Basic VIN lookup API
Vehicle specification identification and valuation
Enter a 17-character VIN to get brand, model, model year, engine, displacement, fuel, transmission, colour, vehicle category, risk rating, market price and used-car price range. One call aggregates multi-source data.
- Brand / model
- Model year / engine
- Transmission / fuel
- Risk rating
- Market price / used-car price
Model identification · valuation reference · inventory records · used-car listings
{
"success": true,
"data": {
"vin": "LFMGJE72******0251",
"brand_name": "Toyota",
"model_name": "Camry",
"year": "2019",
"engine": "2.5L",
"displacement": "2487cc",
"fuel_type": "Gasoline",
"transmission": "Automatic",
"car_type": "Sedan",
"risk_assessment": "Low Risk",
"used_car_price": "Sample range"
}
}
Vehicle history lookup API
Returns accident, title (clean / salvage / rebuilt / flood / lemon), mileage and theft records by VIN across 150+ countries.
/v1/vin/history
JSON
China coverage VIN lookup API
For vehicles manufactured and registered in China, returns motor vehicle registration, inspection, manufacturing, export, accident and anti-fraud results across 31 provinces, with bilingual responses.
POST /v1/vin/china
Registration / inspection / manufacturing / export / accident / anti-fraud
Theft and anti-fraud API
Cross-checks the VIN against international stolen-vehicle databases and runs VIN cloning detection and mileage authenticity checks, returning a risk conclusion.
POST /v1/vin/fraud-check
Stolen-vehicle database / VIN cloning / mileage check
Batch VIN lookup API
Submit multiple VINs at once and receive specifications, history and valuation for each asynchronously — for bulk processing of dealer stock and auction platforms.
POST /v1/vin/batch
Async jobs · Batch results · CSV export
China coverage: the missing piece of global VIN data
Mainstream international vehicle history databases generally do not cover Chinese-manufactured vehicles. As brands such as BYD, NIO, Geely, Chery and GWM expand overseas, that data gap is becoming a real business risk.
Motor vehicle registration records
Covers motor vehicle registration status and history across all 31 provinces to verify vehicle identity and ownership.
Registration status → verifiableInspection and emissions records
Annual inspection, emissions testing and safety compliance data to support condition and compliance judgements.
Inspection history → traceableManufacturing and factory data
Factory specifications, production dates and original configurations from mainstream Chinese manufacturers.
Factory records → standardisedExport and customs documents
Export certificates, customs clearance records and international transport documents for cross-border trade verification.
Export documents → verifiableAccident and insurance records
Insurance claims, accident reports and damage records for pre-import risk screening.
Accident history → aggregatedVIN cloning and mileage check
VIN cloning detection and mileage authenticity checks to identify false vehicle identities.
Authenticity → verifiedThe China coverage supports further analysis
- Registration status verification across 31 provinces
- Inspection and emissions history
- Export document comparison
- VIN cloning detection
- Mileage authenticity check
- Bilingual (Chinese/English) field response
This data can flow into your real business processes
Not another back office to open, but vehicle records where used-car trading, risk control, customs and inventory management actually happen.
Used-car dealers / distributors
Automatically fill in specifications and verify accident and title status when listing vehicles, reducing the risk of buying the wrong or problem car.
Exporting automakers / importers
Verify registration, manufacturing and export documents before importing Chinese-brand vehicles, avoiding VIN cloning and document mismatch risk.
Auto insurance claims / underwriting
Verify vehicle identity and condition in real time and detect odometer rollback and accident history to support risk pricing and claims.
Import customs / vehicle trading
Run VIN-level identity and document verification on cross-border vehicles to reduce customs disputes and compliance risk.
Fleet / logistics management
Track owned or carried vehicles across their full lifecycle, run bulk checks before cross-border export and automate risk control workflows.
Model database apps / auction houses
Auto-fill vehicle parameters and run pre-auction VIN checks to reduce disputes; leasing uses it for residual value and pre-loan verification.
The value of an API is more than "decoding a VIN"
GooFuture's core value lies before the data reaches the API: turning data scattered across multi-region public vehicle records into a vehicle data model that is program-friendly, linkable and maintainable.
Multi-source in one response
Aggregates records from North America, Japan, China and Europe into a single vehicle record, cutting repeated queries.
A dozen sources → one recordField normalisation
Unifies specification, history and valuation fields across countries so systems can match them.
Multiple definitions → unified entityChina coverage added
Modelled specifically for Chinese-manufactured and registered vehicles, filling the China data gap common to international databases.
International gap → coveredBilingual (Chinese/English) response
Bilingual (Chinese and English) field responses for two-way integration between domestic and overseas systems.
Monolingual → bilingualContinuous sync
Continuous sync after source changes, cutting your maintenance costs.
Source → syncFrom enquiry to your first API call in just three steps
Code and responses are static samples. Your consultant will propose an integration plan based on data scope, call volume and delivery method.
- 01
Contact a consultant
Scan the QR code to add us on WeCom and tell us your business scenario, the data you need (global / China coverage) and your expected call volume.
- 02
Confirm the plan
Confirm endpoint scope, history / valuation / anti-fraud options, delivery method and enterprise support needs.
- 03
Start integration
Get your API key and integration materials, then wire the JSON results into your used-car, insurance, customs or SaaS product.
curl "https://api.goofuture.com/v1/vin/basic" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{"vin":"LFMGJE72******0251"}'
{
"data": {
"brand_name": "Toyota",
"model_name": "Camry",
"year": "2019",
"risk_assessment": "Low Risk",
"used_car_price": "Sample range"
}
}
From testing to production
Choose a plan by call volume, batch capability, history/valuation options and enterprise support. Your consultant quotes based on your business needs.
Basic
For API testing and product validation
- Monthly requests
- 100
- Core endpoints
- Basic VIN lookup
- Rate limits
- Basic rate limiting
- China coverage
- —
Standard
For used-car dealers and small teams
- Monthly requests
- 5,000
- Core endpoints
- Basic + history + valuation
- Monitoring conditions
- 10 conditions
- China coverage
- Optional
Professional
For exporting automakers and SaaS
- Monthly requests
- 50,000
- Concurrency
- Higher concurrency
- Monitoring conditions
- 50 conditions
- China coverage
- Includes data from 31 provinces
Enterprise
For platforms, data companies and large enterprises
- Monthly requests
- High-volume usage
- Data delivery
- Incremental data push
- Customisation
- Field / dataset
- Technical support
- Enterprise technical support
The questions worth confirming before integrating a global VIN data API
Straight answers on data sources, China coverage, response fields and commercial integration.
There are plenty of VIN decoders — why do I still need this API?
If you only need to decode a VIN occasionally to see specifications, a public tool is enough. GooFuture is built for teams that need bulk lookups, system integration, unified fields and continuous updates — aggregating data scattered across multi-region public vehicle records into a vehicle record you can get in one call (including history, valuation and China coverage).
Where does the data come from?
Data comes from multi-region public vehicle records, including North American vehicle history and accident databases, Japanese auction and export archives, Chinese motor vehicle registration and inspection, European MOT inspections and international stolen-vehicle databases. GooFuture collects, cleans, standardises, links and aggregates the raw records and delivers them via API.
Which fields are returned for a VIN?
The basic VIN lookup API returns brand, model, model year, engine, displacement, fuel, transmission, colour, vehicle category, risk rating, market price and used-car price range; the vehicle history API additionally returns accident, title, mileage and theft records; the China coverage API returns registration, inspection, manufacturing, export, accident and anti-fraud results.
What does your China coverage include?
China coverage spans motor vehicle registration, inspection, manufacturing and export data across all 31 provincial-level regions in China, covering 100+ Chinese manufacturers (including BYD, NIO, XPENG, Geely, Chery and GWM), with bilingual responses. It fills the China-manufactured vehicle data gap that international vehicle history databases generally have.
Are Chinese brand VINs identified correctly?
Yes. The API automatically decodes all Chinese WMI (World Manufacturer Identifier) prefixes — for example LSV/LVS for BYD, LNB for NIO, LSP for XPENG, LB1 for Geely, LVV for Chery and LGW for GWM — and matches manufacturing and registration data accordingly.
How is data security and compliance ensured?
All data comes from public vehicle records. The API uses bearer token authentication and encrypted transport, billed by call volume; enterprise plans can specify data delivery scope, retention and compliance requirements, governed by the service agreement.
Can I integrate the data into my own used-car / insurance / customs product?
Yes. The API can be used in internal systems and integrated into used-car platforms, auto insurance claims, import customs, model database apps and trade SaaS products; commercial usage is governed by the applicable plan and service agreement.
Do you support batch lookups?
Yes. The batch VIN lookup API accepts multiple VINs at once and returns specifications, history and valuation for each asynchronously — for large-scale processing of dealer stock, auction platforms and fleet management, with result export.
You no longer integrate data sources from a dozen countries yourself.
From collecting multi-region public records to field normalisation, China coverage modelling and bilingual responses — we handle it all. Your systems just call the API.