The DVLA holds the definitive record for every registered vehicle in the UK, and developers regularly ask the same question: how do I get that data into my application by registration number? This guide covers the official DVLA Vehicle Enquiry Service (VES) API, what it does and doesn't give you, and when a commercial gateway is the better route.
What "DVLA API" usually means
There are two things people call the "DVLA API":
- The DVLA Vehicle Enquiry Service (VES) API — the official government API that returns registration data for a UK vehicle.
- A commercial vehicle data API that includes DVLA-sourced fields alongside MOT history, valuation, provenance and more, through a single integration.
Both are legitimate. Which you want depends on how much data you need and how much integration and compliance work you want to own yourself.
What the DVLA VES API returns
Given a valid registration, the VES API returns the core DVLA-held attributes, typically including:
- Make and (in some cases) model
- Colour
- Fuel type and engine capacity
- Year of manufacture / first registration
- CO₂ emissions
- Tax status and tax due date
- MOT status and MOT expiry date
It's a clean, official source for "what does the DVLA hold about this plate right now?" VehicleMatic's Vehicle Details product is built on this same DVLA data, returned in a normalized JSON envelope.
What the DVLA VES API does not give you
This is where teams get caught out. The VES API is deliberately narrow. It does not include:
- Full MOT history — individual test results, mileage readings over time, and advisories (that's the separate DVSA MOT History API).
- Valuation — trade/retail/private values.
- Provenance — outstanding finance, write-off category, stolen markers (the HPI-style check).
- Factory specification and options.
If your use case needs any of those, you'll be integrating additional providers anyway — which is the main reason teams reach for a marketplace that bundles them behind one key.
Access, keys and rate limits
The official VES API requires registering for access and managing your own API credentials, request signing and rate limits directly with the DVLA. That's fine for a single, high-volume, DVLA-only integration where you have the engineering time to own it.
A commercial gateway like VehicleMatic abstracts that: you get one API key that works across DVLA registration data and every other dataset, a single normalized schema, and pay-per-lookup billing with no contract. You call:
POST /products/vehicle-details/api/live/lookup
X-API-KEY: your_key_here
{ "registration": "AB12CDE" }
and receive the DVLA fields in the same envelope shape as every other product.
When to use official DVLA vs a marketplace
Use the official DVLA VES API directly if: you need only current registration/tax/MOT-status data, you have very high volume, and you're happy to own the access agreement, auth and compliance yourself.
Use a marketplace like VehicleMatic if: you need DVLA data plus MOT history, valuation, provenance, spec or imagery; you want one integration and one bill; you value being charged only on successful lookups; and you don't want to manage multiple provider relationships.
Everything VehicleMatic returns is sourced from an official register or a licensed data partner — see data & coverage for exactly where each field comes from and how to use it lawfully.
Try it without committing
You can see the exact shape of a DVLA-sourced response in the sandbox with no account, then sign up for 10 free live lookups to test against real registrations.
Frequently asked questions
Is DVLA vehicle data free? The DVLA's own VES API is available to registered users, but you own the integration and compliance. Commercial gateways charge a small per-lookup fee for the convenience of one normalized API and bundled datasets.
Can I get make and model from the DVLA? The DVLA record is strongest on make; precise model/trim often comes from combining registration data with specification data — which a marketplace can return in the same call.
Does DVLA data include MOT history? No — MOT status yes, full MOT history no. History comes from the DVSA dataset.
Explore the DVLA-backed product on the Vehicle Details page, or see how it fits with everything else on the API catalog.