New Zealand Vehicle Register Data API
Plug New Zealand vehicle register data into used-car due diligence and auto-insurance risk control
Covers registered vehicles with make and model, body type and colour, engine capacity and power type, model year, first New Zealand registration, import status, country of origin and previous registration country, usage class, region and fuel consumption. Supports exact lookup, combined search, status verification and batch checks.
Turn GB-scale English registry files into auditable vehicle record data assets
Why You Need This Data Service
New Zealand is one of the world main markets for right-hand-drive and Japanese-imported used vehicles. Registry data is published as GB-scale English flat files with scattered fields and enums, so using it directly for used-car verification and risk screening requires heavy parsing, cleaning and translation.
GB-scale English files are hard to use
The raw registry data is an extremely large flat file with English enums for body, power, usage and import status, so every integration needs fresh parsing, translation and field mapping.
The first 11 VIN characters are not unique
Registry data publishes only the first 11 VIN characters, which several vehicles in the same model family may share, so pinpointing one vehicle needs the engine or chassis number as well.
Import background information is scattered
New, used and re-registered statuses, plus country of origin and previous registration country, sit in separate columns, making import background and compliance checks difficult.
No batch verification capability
Screening vehicle lists, rental fleets or insured vehicles in bulk cannot be done record by record — you need a standardized batch verification API.
From source-language registry data to a structured query API
GooFuture turns New Zealand public vehicle register data into a ready-to-call API through six processing steps.
You do not need to handle source parsing or enum mapping — query standardized vehicle records directly through the API.
API Capabilities
Four core endpoints for different verification scenarios. All return standardized JSON with unified, Chinese-mapped enums for make, body, power, usage and import status, supporting queries by VIN, engine number and chassis number.
Vehicle record detail lookup
Look up a full vehicle record by the first 11 VIN characters, with automatic truncation of a full 17-character VIN. Returns make and model, submodel, body type and colour, engine capacity, power type, model year, first registration, import status, country of origin and previous registration country, usage, seats and mass, transmission, region and fuel consumption.
curl "https://api.goofuture.com/v1/nz/vehicle/5YJ3F7EA3KF" \
-H "Authorization: Bearer {api_key}"{
"vin11": "5YJ3F7EA3KF",
"make": "Tesla",
"make_original": "TESLA",
"model": "Model 3",
"submodel": "Standard Range Plus",
"body_type": "Sedan",
"body_type_code": "SALOON",
"basic_colour": "White",
"cc_rating": "—",
"motive_power": "Battery electric",
"motive_power_code": "ELECTRIC",
"vehicle_year": 2019,
"first_nz_registration": "2019-09",
"import_status": "New vehicle",
"import_status_code": "NEW",
"original_country": "United States",
"previous_country": null,
"vehicle_type": "Passenger car/Van",
"vehicle_usage": "Private passenger",
"number_of_axles": 2,
"number_of_seats": 5,
"gross_vehicle_mass": 2060,
"power_rating": 195,
"transmission_type": "Other",
"tla": "Auckland",
"postcode": 600,
"fc_combined": null,
"fc_urban": null,
"fc_extra_urban": null,
"ac_refrigerant": "Refrigerant R134a",
"snapshot_date": "2026-07-31"
}Combined-condition vehicle search
Search vehicle records by a combination of make, model, engine number or chassis number. Vehicles in the same model family may share the first 11 VIN characters, while engine and chassis numbers pinpoint a single vehicle.
curl "https://api.goofuture.com/v1/nz/vehicle/lookup?make=Toyota&model=Corolla&page=1&page_size=20" \
-H "Authorization: Bearer {api_key}"{
"query": {
"make": "Toyota",
"model": "Corolla"
},
"total": 173138,
"page": 1,
"page_size": 20,
"results": [
{
"vin11": "JTDKR22E400",
"engine_number": "1ZZ-1731090",
"make": "Toyota",
"model": "Corolla",
"submodel": "1.8P GL Hatchback 5doors 4AT",
"body_type": "Hatchback sedan",
"basic_colour": "Red",
"motive_power": "Petrol",
"vehicle_year": 2004,
"first_nz_registration": "2004-09",
"import_status": "New vehicle",
"original_country": "Japan",
"tla": "Timaru District"
}
]
}Registration status and import background verification
Verify a vehicle import status and registration background, returning enums such as new, used or re-registered, together with country of origin, previous registration country, first New Zealand registration and assembly method for import sourcing checks.
curl "https://api.goofuture.com/v1/nz/vehicle/register?vin11=WVGZZZ7LZ9D" \
-H "Authorization: Bearer {api_key}"{
"vin11": "WVGZZZ7LZ9D",
"make": "Volkswagen",
"model": "Touareg",
"motive_power": "Diesel",
"import_status": "Used vehicle",
"import_status_code": "USED",
"nz_assembled": "Built-up import",
"original_country": "Germany",
"previous_country": "United Kingdom",
"first_nz_registration": "2012-03",
"vehicle_year": 2008,
"tla": "Auckland",
"postcode": 1062,
"fc_combined": 10.5,
"fc_urban": 14.2,
"fc_extra_urban": 8.4,
"ac_refrigerant": null
}Batch vehicle record verification
Pass a list of first-11 VIN characters or engine numbers to return record summaries and registration status in bulk — for used-car list screening, rental fleet audits and bulk verification of insured vehicles.
curl -X POST "https://api.goofuture.com/v1/nz/vehicle/batch" \
-H "Authorization: Bearer {api_key}" \
-H "Content-Type: application/json" \
-d '{"vin11s": ["5YJ3F7EA3KF", "JTDKR22E400", "5HD1FC4117Y"]}'{
"total": 3,
"found": 3,
"results": [
{
"vin11": "5YJ3F7EA3KF",
"make": "Tesla",
"model": "Model 3",
"vehicle_year": 2019,
"motive_power": "Battery electric",
"import_status": "New vehicle"
},
{
"vin11": "JTDKR22E400",
"make": "Toyota",
"model": "Corolla",
"vehicle_year": 2004,
"motive_power": "Petrol",
"import_status": "New vehicle"
},
{
"vin11": "5HD1FC4117Y",
"make": "Harley-Davidson",
"model": "Electra Glide",
"vehicle_year": 2007,
"motive_power": "Petrol",
"import_status": "New vehicle"
}
]
}Real-World Use Cases
How companies in different roles and stages use the New Zealand Vehicle Register Data API.
Used-vehicle import due diligence
Before importing right-hand-drive vehicles from Japan, the UK and other markets, verify country of origin, previous registration country, first New Zealand registration and model year to assess the source and build a complete vehicle record.
Auto insurance pricing and risk control
Insurers verify make and model, model year, power type and usage class in bulk at underwriting and renewal, automatically flagging high-risk vehicles to improve pricing and underwriting efficiency.
Rental and mobility risk control
Rental companies and mobility platforms verify fleet vehicle records and usage class, separating private passenger from commercial vehicles and identifying taxis and freight vehicles.
Fleet management platform integration
Logistics and enterprise platforms embed vehicle record verification into data entry, auto-filling make and model, mass and fuel consumption for standardized vehicle management.
New Zealand vehicle register data coverage
Covers registered vehicle records in the New Zealand register, including passenger cars, vans, trucks, utes, trailers, motorhomes and motorcycles, with fuel consumption and new energy power data.
Data Quality & Differentiators
GooFuture cleans English vehicle register data into directly queryable structured data, lowering integration and maintenance cost.
Chinese enum mapping
Map English enums for body, power, usage and import status into a unified, readable form while keeping the source text, so teams can use and audit it directly.
Multi-dimensional lookup index
Because the first 11 VIN characters are not unique, a three-dimensional index on VIN, engine number and chassis number supports vehicle-level verification.
Structured import background
Split new, used, re-registered and self-assembled statuses and unify country of origin and previous registration country enums, supporting import sourcing checks.
Fuel economy and new energy
Provides combined, urban and extra-urban fuel consumption fields, with power type split into battery electric, plug-in hybrid and petrol hybrid, supporting new energy penetration analysis.
Monthly snapshot sync
Registry data syncs as monthly snapshots, with new registrations, deregistrations and field changes applied at each snapshot so verified vehicle data does not go stale.
Three-Step Onboarding
From consultation to production queries in as little as a few hours.
Contact a consultant
Describe your used-car due diligence or auto-insurance needs and confirm the data scope required (VIN, engine number, batch size and more).
Confirm the plan
Both sides agree on endpoint scope, call volume, concurrency and update frequency. Webhook or CSV batch delivery is agreed at this stage.
Start Querying
Get an API key and docs, then query over standard REST. Technical support is provided during integration so results can be used directly in your systems.
Ongoing maintenance
Registry data syncs monthly, with field changes applied at each snapshot. Your consultant keeps tracking data quality and API stability.
# Query the vehicle record
curl "https://api.goofuture.com/v1/nz/vehicle/5YJ3F7EA3KF" \
-H "Authorization: Bearer {api_key}"
# Verify registration status and import background
curl "https://api.goofuture.com/v1/nz/vehicle/register?vin11=WVGZZZ7LZ9D" \
-H "Authorization: Bearer {api_key}"
# Batch-verify a vehicle list
curl -X POST "https://api.goofuture.com/v1/nz/vehicle/batch" \
-H "Authorization: Bearer {api_key}" \
-H "Content-Type: application/json" \
-d '{"vin11s": ["5YJ3F7EA3KF", "JTDKR22E400", "5HD1FC4117Y"]}'Choose the Right Plan
From single-record verification to batch due diligence, from low-frequency calls to high-concurrency integration — four plans.
Basic
- Monthly requests: 5,000
- API scope: exact VIN lookup
- Rate limit: 1 QPS
- Monitoring: —
- Delivery: REST API
- Support: email support
Standard
- Monthly requests: 25,000
- API scope: VIN lookup + combined search / status verification
- Rate limit: 2 QPS
- Monitoring: snapshot update push
- Delivery: REST API + Webhook
- Support: priority email support
Professional
- Monthly requests: 100,000
- API scope: all core endpoints + batch verification
- Rate limit: 5 QPS
- Monitoring: snapshot update push
- Delivery: REST API + Webhook + CSV
- Support: dedicated technical consultant
Enterprise
- Monthly requests: custom
- API scope: all + custom endpoints
- Rate limit: high concurrency
- Monitoring: custom
- Delivery: REST API + Webhook + CSV
- Support: enterprise-grade SLA
FAQ
Common questions about data scope, update frequency, API capabilities and pricing.
Which New Zealand vehicles are covered?
Covers registered vehicle records in the New Zealand motor vehicle register, including passenger cars, vans, trucks, utes, trailers, motorhomes and motorcycles. Each record includes make and model, body type and colour, engine capacity and power type, model year, first New Zealand registration, import status, country of origin and previous registration country, usage class, region, transmission and fuel consumption.
Why not query the public New Zealand vehicle register data directly?
Raw registry data is published as GB-scale flat files with English enums, and body, power, usage and import status descriptions scattered across columns, with no query interface by VIN or engine number. GooFuture cleans, structures and maps it so it plugs straight into verification and due diligence workflows.
Which query filters are supported?
Exact lookup by the first 11 VIN characters (with automatic truncation of a full 17-character VIN), combined search by make and model, engine number or chassis number, registration status verification and batch record checks. Make, body, power, import status, usage and colour all come with consistent readable mappings.
What is the difference between the first 11 VIN characters and a full 17-character VIN?
A full VIN has 17 characters; the first 11 identify the manufacturer, model and engine characteristics. Registry data is published by first-11 VIN characters, which several vehicles in a model family may share, so pinpointing one vehicle requires the engine or chassis number. The API exposes all three: first-11 VIN characters, engine number and chassis number.
How often is it updated?
Registry data updates as monthly snapshots. New registrations, deregistrations and field changes (such as a region change after an owner moves, or a colour correction) arrive with each snapshot. Exact frequency is agreed when confirming the plan.
Can it integrate with our existing systems?
Yes. The REST API returns standardized JSON with fixed fields and unified enums. It supports Webhook update pushes and batch delivery of detailed data in CSV or Excel on request.
Does the data include fuel consumption and new energy vehicle data?
Yes. The API provides combined, urban and extra-urban fuel consumption fields, and you can filter new energy vehicles — battery electric, plug-in hybrid and petrol hybrid — directly by power type enum, making it suitable for penetration analysis and fuel economy research.
How is pricing calculated?
Pricing is based on monthly request volume. Basic suits low-frequency single-record checks, Standard adds combined search and status verification, and Professional and Enterprise support higher concurrency, batch checks, Webhooks and custom integration. Contact a consultant for a specific plan.
Plug New Zealand vehicle register data into due diligence and risk control
From make and model to import background, from usage class to fuel consumption — a complete New Zealand vehicle record data foundation.
