DVLA Vehicle Enquiry API: A Complete Guide for UK Businesses

The DVLA Vehicle Enquiry Service (VES) API is a free official government API that returns vehicle data by registration number — make, model, colour, fuel type, engine size, tax status, MOT expiry date and CO2 emissions. It’s the same data source behind the government’s own vehicle enquiry tool, available programmatically for any UK business to integrate into their platform. This guide covers what the API returns, how authentication works, how it differs from the DVSA MOT API, and what you can realistically build with it.

What the DVLA Vehicle Enquiry API returns

A single API call to the DVLA VES endpoint returns the following data for any UK-registered vehicle:

Vehicle identification: make, model, colour, year of manufacture, date of first registration, engine capacity in cc, fuel type (petrol, diesel, electric, hybrid), and vehicle type approval category.

Tax and MOT status: current tax status (taxed, untaxed, SORN, not licensed), tax due date, MOT status (valid or expired), and MOT expiry date.

Environmental data: CO2 emissions in grams per kilometre, Eurostandard emissions category, and real driving emissions figures where available.

Additional fields: wheelplan, revenue weight for commercial vehicles, date of last V5C issued, and a marked-for-export flag.

What the API does not return: registered keeper name or address, number of previous owners, service history, accident history, or any personal data. The VES is a vehicle data API, not a keeper enquiry service. Keeper information requires a formal Section 19 application to DVLA and is not available through the API.

How DVLA VES API authentication works

The DVLA VES API uses simple API key authentication — significantly simpler than the OAuth 2.0 flow required by the DVSA MOT API. You register through the DVLA API portal, your application is reviewed, and you receive an API key included as a header on every request.

The API key must always be stored server-side. The correct pattern is a server-side proxy: your platform sends a request to your own server, the server calls the DVLA API with the key, and the parsed response is returned to your platform. This keeps credentials protected and means they can be rotated without touching any client-side code.

DVLA registration is free. The approval process is generally straightforward for legitimate business use cases — used car dealers, fleet managers, insurance platforms and similar. Approval typically takes a few days to a couple of weeks.

DVLA VES vs DVSA MOT API — what’s the difference?

This is the most common point of confusion for businesses integrating vehicle data. The two APIs come from different government agencies and return completely different data.

The DVLA VES API returns current vehicle registration data: what the vehicle is, its current tax and MOT status, fuel type, colour, engine size and emissions. Think of it as the vehicle’s current record. It’s the right API when you need to know what a vehicle is and whether it’s currently taxed and has a valid MOT.

The DVSA MOT API returns historical MOT test records: every MOT test conducted on the vehicle, with pass/fail results, mileage recorded at each test, failure reasons and advisory notices. Think of it as the vehicle’s test history. It’s the right API when you need to understand a vehicle’s maintenance history and track mileage consistency over time.

Many use cases need both. A used car dealer listing platform that wants to show buyers a complete picture needs VES data (what is this vehicle, is it currently taxed) and MOT data (what’s the full test history, are there recurring advisories). A fleet management system monitoring compliance needs VES data for current tax and MOT status and MOT history for maintenance tracking. A custom integration can call both APIs and combine the responses into a single data layer for your platform.

Rate limits and usage

The DVLA VES API has rate limits applied at the API key level. For most business use cases — lookups triggered by individual user actions or a daily fleet check — the default limits are generous. For high-volume applications making thousands of lookups per day, it’s worth confirming your expected volume with DVLA during the registration process.

A well-built integration caches responses where appropriate. Vehicle registration data doesn’t change hourly — tax status and MOT expiry date change at specific events, not continuously. Caching a vehicle’s response for 24 hours is reasonable for most use cases and reduces API calls significantly for repeat lookups on the same registration.

What you can build with the DVLA VES API

The most common integrations are vehicle data auto-population on forms and listings, tax and MOT status display on dealer websites, fleet compliance dashboards, insurance quote tools that verify vehicle details, and part-exchange valuation tools that retrieve vehicle specifications automatically when a customer enters their registration.

Combined with the DVSA MOT API, the data layer becomes more comprehensive — full vehicle record plus complete test history in a single lookup. For used car platforms and fleet tools, this combination is the foundation of a complete vehicle history integration.

For the full service details and pricing, see the DVLA API integration service. For how DVLA compares to the DVSA MOT API, see DVLA API vs DVSA MOT API. For what the integration costs, see the DVLA API integration cost guide.

Related posts

• DVLA API vs DVSA MOT API: what’s the difference?
• DVLA API integration for used car dealer websites
• DVLA Vehicle Enquiry API integration cost
• How to automate vehicle tax and MOT checks

Error handling and edge cases

A production DVLA VES integration needs to handle several common failure scenarios gracefully. Not every registration number entered by a user will return a clean result, and the integration needs to distinguish between different failure types and respond appropriately.

Vehicle not found. The registration number doesn’t exist in the DVLA register. This happens most often with mistyped registrations. The response is a 404 from the API. The integration should return a clear message to the user — “No vehicle found for this registration” — and prompt them to re-enter.

SORN vehicle. The vehicle exists but is declared off-road. The API returns the vehicle data but with a SORN tax status. The integration should display this clearly — a vehicle that’s SORN is not legally road-usable, which is relevant for dealer listing tools and insurance platforms.

New vehicle — no MOT. Vehicles under three years old are exempt from MOT. The API returns vehicle data but no MOT expiry. The integration should show “MOT not required” rather than a blank field or an error.

API unavailability. DVLA’s API, like any external service, can be temporarily unavailable. The integration should implement retry logic with backoff for transient errors, and fallback messaging for extended outages. Caching previous responses means that repeat lookups on known registrations can still return data during an outage.

Invalid registration format. UK registration numbers follow a defined format. Client-side validation can catch obviously invalid inputs before they reach the API, reducing unnecessary API calls and giving users faster feedback on input errors.

Combining DVLA with other data sources

The DVLA VES API is most powerful when combined with other vehicle data sources. The most common combination is DVLA VES plus DVSA MOT history — the VES tells you what the vehicle is and its current status, the MOT history tells you the vehicle’s test record and mileage history. Together they provide a comprehensive picture without relying on commercial vehicle history services.

For businesses that need finance checks, write-off history, or keeper changes alongside vehicle data, a commercial provider like HPI or Cazana can be integrated alongside the free government APIs. The free APIs cover the factual vehicle record; commercial providers add the additional data categories that require their own data sources. A custom integration can combine all of these into a single lookup that hits multiple APIs and returns a unified response to your platform.

For the DVSA MOT API specifically and how it differs from DVLA, see DVLA API vs DVSA MOT API. For the DVSA MOT API in detail, see the DVSA MOT API integration service.

The difference between the DVLA API and commercial vehicle check services

Commercial vehicle data services like HPI, Cazana and cap hpi charge per lookup and provide a packaged report combining multiple data sources. The DVLA VES API is free and returns only DVLA data. The two serve different purposes and aren’t direct alternatives for all use cases.

If your use case is vehicle identification and current status — auto-populating a form with make, model and fuel type when a customer enters their registration, or checking tax and MOT status for a fleet — the DVLA VES API does this for free. You don’t need a commercial service for data the government provides openly.

If your use case requires finance checks, write-off markers, stolen vehicle alerts or keeper history — data that comes from commercial sources like insurance company databases and finance houses — you need a commercial provider. The DVLA doesn’t hold or share this data through the VES API.

For most platforms, the sensible approach is to use the DVLA VES API for vehicle identification and status, the DVSA MOT API for test history, and a commercial provider only for the data categories that genuinely require it. This minimises ongoing per-lookup costs while ensuring you have the data your use case actually needs.

If you need help with a custom API integration for your website or business application, I can help. I build bespoke API integrations for UK businesses. See API integration pricing or get in touch to discuss your project.